
A San Francisco platform company that runs Drupal, WordPress and Next.js for organizations who can't afford a 2 a.m. outage - and would rather you didn't notice they exist.
Which is, more or less, the point. Pantheon sells the absence of drama. The company runs a WebOps platform - hosting, workflow, automation - for more than 12,000 organizations whose homepages, campaign pages, intranets and product docs all share the same unglamorous requirement: be up, be fast, be safe to deploy on a Thursday afternoon.
You can run a tiny nonprofit site on it. You can also run a Fortune 100 marketing portfolio on it. The platform does not particularly care, which is unusual in enterprise software, where caring is usually the product.
Drupal and WordPress run an enormous share of the internet. By most counts, WordPress alone powers more than 40% of the web. That is a remarkable achievement for an open-source CMS - and a slightly miserable one to operate at scale. The plugins drift. The PHP versions drift. The marketing team wants a landing page by Friday. Somebody, somewhere, needs to keep all of it talking to itself without falling over.
For most of the 2000s, the answer to that was a sysadmin and a lot of caffeine. The early cloud era replaced the sysadmin with a checklist of AWS services and, often, the same sysadmin. Marketing teams started using the word "DevOps" in budget meetings, which is usually how you know something has gone wrong.
The founders - Zack Rosen, David Strauss, Josh Koenig, Matt Cheney - all came out of that community. They had seen, repeatedly, how the same problems repeated themselves: a slow site for a non-profit, a security patch the agency forgot to apply, a viral moment that took down a state government's homepage. The fix was not better servers. The fix was a different shape of platform.
In 2010, the founders bet that the right primitive for the open web was not a virtual machine, and not a shared host. It was a container - a lightweight, multi-tenant unit that could run Drupal or WordPress on demand and be cloned, replicated, and torn down in seconds. Years before Kubernetes was a t-shirt, Pantheon was operating multi-tenant Linux containers in production.
On top of that primitive, they built the second bet: a Dev/Test/Live workflow that marketing and engineering could share. The same site, three environments, Git-tracked changes, one-click promotion. Familiar to any software engineer. Foreign to most marketing teams in 2011.
The bet's modest superpower was branding: Pantheon insisted on calling itself WebOps, not hosting. The distinction matters. Hosting is a line item. WebOps is a way of running. One gets you a server. The other gets you a deployment culture.
Founded in San Francisco by four veterans of the Drupal community.
Raises $5M Series A led by Foundry Group.
$21.5M Series B led by Scale Venture Partners.
$40M Series D led by Sageview Capital; total funding crosses $100M.
$100M Series E from SoftBank Vision Fund 2. Valuation tops $1B.
Sameer Kazi appointed CEO; Bill Ingram moves to CFO.
Named WebOps Platform of the Year by CIO Review.
The platform itself is a managed surface for running open-source CMS workloads on Google Cloud. The pieces customers tend to name first:
Dev/Test/Live environments, Git-based deploys, multi-developer workflow for WordPress, Drupal, and Next.js front-ends.
Built-in CDN, image optimization, and edge caching for sites that spike unpredictably.
Automated, visual-regression-tested updates for CMS core, plugins, and themes. The boring work, automated.
Front-end hosting for Next.js paired with Drupal or WordPress back-ends, for teams going the Jamstack route.
Multi-site management, white-labeling, and billing tools for digital agencies running dozens (or hundreds) of client sites.
SOC 2, HIPAA-eligible plans, and the kind of audit paperwork enterprise procurement asks for at minute 35 of an evaluation call.
The Pantheon roster reads like a list of organizations that would prefer not to call IT. DocuSign. Patagonia. MGM Resorts. Clorox. MIT. The United Nations Foundation. Each one has a different reason for being there: a global compliance need, a campaign team that ships daily, an academic department that wants its site to look like a department's site and not a startup's. The platform absorbs all of them.
Mission statements, as a genre, are mostly bad. Pantheon's is, mercifully, narrow: make Drupal and WordPress - and now Next.js - viable at enterprise scale without making them feel enterprise. That has implications. It means investing in the Drupal and WordPress projects directly, not just hosting them. It means hiring engineers who know the difference between a CMS user and a developer. It means keeping the product opinionated when "opinionated" would be easier to abandon.
Under Sameer Kazi, who took over as CEO in November 2024, the company has signaled a tighter focus on customer outcomes - hence Michelle Curless's arrival as Chief Customer Officer in early 2025, and the announcement of WebOps Platform of the Year a few months later. None of which is shouted from the rooftops. Pantheon is not really a rooftop company.
There is an argument going around that AI agents will browse the web instead of humans. Setting aside whether that's true, both species - the human and the bot - prefer pages that load and don't lie. Pantheon's bet for the next decade is that the underlying CMS gets more complicated, the front-ends get more decoupled, and the team operating it gets smaller. The platform has to absorb the slack.
The other bet is older and steadier: open source is not finished. Drupal and WordPress have outlived two waves of "the CMS is dead" think pieces. The infrastructure that runs them, if it is built well, will outlive a third.
Their sites are still working. They are still not thinking about Pantheon. They are thinking about jackets, syllabi, agreements - the actual things their organizations are for. Somewhere, a deploy ran. Somewhere, a patch got applied. Somewhere, a piece of plumbing did its job and went unnoticed.
Pantheon, fifteen years in, is still building the platform that earns that silence. It is harder than it sounds and quieter than it deserves.
All four founders met through the Drupal community. The Dev/Test/Live model is named, deliberately, after how newspaper production teams moved stories through a stack. Some habits stay.