Companies that use Sanity.io

Source: Analysis of job postings that mention Sanity.io (using the Bloomberry Jobs API)

I analyzed 63 job postings and found that Sanity.io purchasing decisions are driven by engineering and product leadership. Frontend Engineers make up 38% of hiring, followed by Backend Engineers at 11%, Solutions Architects at 5%, and Content Marketing Specialists at 6%. The remaining 40% spans diverse roles from Web Developers to Quality Engineers. Leadership positions like Technical Directors and VPs of Digital Engineering are making the strategic call to adopt Sanity.io as part of broader platform modernization efforts, particularly moving away from legacy systems like WordPress and monolithic architectures.

Day-to-day users are primarily developers building headless CMS implementations. I noticed extensive mention of React, Next.js, and TypeScript stacks, with Sanity.io serving as the content layer. Teams are building marketing websites, e-commerce platforms, and enterprise web applications where content editors need intuitive workflows while developers maintain clean, performant code. The combination of frontend and backend engineers suggests Sanity.io enables true separation of concerns between content management and application logic.

Companies are solving specific pain points around content operations at scale. One posting emphasized the need to "replace complexity and manual paperwork" while another sought to build "fast, accessible, and elegant experiences." Multiple roles mentioned "modern JAMstack and composable architectures" and the goal of creating "scalable, secure, and future-ready web architectures." The recurring theme is organizations modernizing their tech stack to enable faster iteration, better performance, and improved collaboration between technical and non-technical teams.

Source: Analysis of Linkedin bios of 3,346 companies that use Sanity.io

I noticed Sanity.io attracts an incredibly diverse range of companies, but they share a common thread: they're all building or managing significant digital presences. These aren't just companies with websites. They're organizations where content is central to their business model, whether that's media publishers like British Vogue and Rough Draft Atlanta, e-commerce platforms, SaaS companies building complex product experiences, or service businesses that need to communicate expertise and build trust online. Many are in sectors experiencing digital transformation: healthcare facilities, real estate agencies, financial services, manufacturing firms with direct-to-consumer channels, and education providers.

The funding and employee data reveals a sweet spot: primarily growth-stage companies with 11-200 employees. While there are some larger enterprises (FDM with 428 employees, Home Instead) and early-stage startups (seed and pre-seed funded), the majority are past the initial startup phase but not yet corporate giants. Many show no recent funding rounds, suggesting they're profitable and scaling sustainably rather than venture-backed hypergrowth plays.

Source: Analysis of tech stacks from 3,346 companies that use Sanity.io

I noticed that Sanity.io users are overwhelmingly modern web development shops building fast, content-driven experiences. The dominant presence of Next.js (95x more likely) and Vercel (91x more likely) tells me these are companies that have fully embraced the Jamstack architecture and React ecosystem. They're likely digital agencies, e-commerce brands, or media companies that prioritize performance and developer experience over traditional CMS solutions.

The pairing patterns reveal a clear workflow. Next.js and Vercel together suggest teams shipping production apps quickly with minimal DevOps overhead. The strong correlation with Shopify Oxygen (455x more likely) is particularly telling. It shows many Sanity users are building headless commerce experiences, using Sanity to manage product content and marketing pages while Shopify handles transactions. The Netlify correlation (78x more likely) reinforces this deployment pattern, showing these teams want git-based workflows and instant previews. Claude for Work appearing 33x more frequently suggests these are forward-thinking technical teams already integrating AI into their content operations.

The full stack screams product-led growth and developer-first decision making. These aren't enterprise buyers going through lengthy RFP processes. They're technical teams that discovered Sanity through developer communities, tried it on a side project, and brought it into production. The Vercel Pro adoption indicates they're past the hobby stage and running real businesses, but they still value tools that scale incrementally. I'd guess many are Series A to Series C startups or established companies with modern engineering cultures.