Pantheon Launches P1, an AI-Native CMS and Web Operations Platform

MIAMI — Pantheon launched P1, its agentic content and web operations platform, at the company's GoLive conference in Miami at the Loews Hotel on Oct. 6. According to Pantheon's SVP of Product, Chris Yates, P1 is an AI-native web composition and management layer that both is, and is not, what one would traditionally call a content management system.

P1 differs from a CMS in that it was designed from the start to empower high velocity human and AI agent collaboration on both content and code within a shared set of operational and brand guardrails.

Pantheon ... Beyond Drupal, Beyond Wordpress

According to Pantheon leadership, P1 aims to help organizations use AI to improve web ops velocity, collaboration and transparency without introducing fragmentation, security risks, brand inconsistency or accountability gaps.

The P1 platform is a new CMS in that it can serve as the primary content repository, but it can also happily play more of an experience composition role, pulling content from any API source, including existing WordPress or Drupal instances, PIMs, Google Docs or any platform that has an appropriate API. P1 includes its own front-end authoring and content management environment and renders front-end experiences built as Next.js applications.

Pantheon said it developed the P1 roadmap over two years, concluding that legacy PHP-based CMS architectures were unsuitable for the asynchronous, long-running and human/agent collaborative work streams that modern teams now require.

Related Article: Pantheon Publishes Google Docs Content Publisher Tool

P1's Agent-Human Collaboration

At the heart of the platform is an agentic orientation and agents as first class citizens. Agents take two forms in the platform: the native interactive tasking agent, named Zappy, or remote agents that access the platform via MCP.

Zappy is an out of the box collaborator that can be accessed via 1:1 or group chat interface at a number of different surfaces and elevations in the back office experience. Zappy can carry out in-page tasks such as editing, performing localization and modifying elements of the end user experience.

Remote agents, such as Claude desktop, utilize the P1 MCP interface and tools, and either authenticate by impersonating a platform user, or authenticate via access key and operate under their own identity with their own set of unique permissions.

Built on the Shoulders of Primatives

It's true that P1 is one of the many new products who's rapid evolution and surfacing in the market can be, at least in part, credited to the rise of vibe coding. The company has had code-level participation from a range of company execs, product leadership and professional developers.

P1 comprises a significant body of new code, but also benefits from and ties together elements of the company's existing products and Pantheon's nearly 16 years serving enterprise-grade clients. Pantheon leadership told CMSWire that they are serving an estimated 20,000 clients, 10,000 professional web teams, hosting around 100,000 websites and serving roughly one billion unique visitors per month.

Co-founder, Josh Keonig, described P1 as built on top of a core set of Pantheon Primatives — currently active products and service components that the company has been investing in, in some cases, since its inception.

This set of primatives include:

• Multidev: Multidev, a long standing differentiator for Pantheon's core services, gives each code branch its own environment for development, testing and previewing. P1 builds on that foundation to bring a concept called workstreams to the product. Workstreams are a business-friendly way to let teams work together on many different parallel initiatives, keeping code, design, structure and content changes together until they’re ready to be merged and released.
  
  
• Upstreams: An upstream is a parent blueprint from which an organization can create sites and push subsequent changes across its fleet. Upstreams can be thought of like code repositories that modify the base Pantheon code base, but go beyond this in ways that can support the needs of sophisticated site fleet operators that need to broadcast out code, config, design and eventually content changes across their fleets.
  
  
• Autopilot: Autopilot combines patch and update management with visual regression testing. It can report on changes from patches or upgrades and help IT teams control whether updates are applied. P1 intends to draw on those capabilities for its pre-flight checks before a workstream is released, covering accessibility, performance and Core Web Vitals, among other pre-release concerns and governance. Parts of the Autopilot functionality are present in the current P1 beta, but much of that P1 experience remains to be implemented.
  
  
• Content Publisher: Content Publisher, released in September 2025, lets authors work in the comfort of Google Docs or Microsoft Word to create and publish longer form content directly into Wordpress, Drupal, Next.js sites or P1. The new P1 platform natively integrates the Content Publisher functionality, supporting ingestion of this content into the local repository as a first class data source. Authors can contribute content without controlling, or breaking, the site's visual design.
  
  
• Next.js hosting & CDN: The company released Next.js hosting support in April of this year and is continuing to evolved that offering. P1's reliance on Next.js hosting for digital experience delivery will additionally put pressure on that product, helping to mature and expand the offering. Pantheon's Next.js hosting capability is essential to P1's font end web experience delivery and is tightly coupled with the company's CloudFlare-backed NextGen CDN.

Inside P1's First Customer Build

Chris Teitzel, founder of digital agency Cellar Door, a Pantheon partner, onboarded the first customer on P1: A company working at the intersection of sports and technology. It pulls data from multiple sources to help teams track what players eat, when they sleep and how ready they are for game day.

Teitzel said P1 fills a gap his team has worked around for years while decoupling Drupal and WordPress sites. A native, in-browser visual editor for Next.js that uses a team's own components used to be something developers had to piece together.

"And P1 just works," he told CMSWire during an interview at the Loews Hotel in Miami.

From WordPress and Elementor to P1 in 11 Weeks

The business had a strong in-house design and marketing team, an internal design system and designers already building components with Claude Code. The friction came from its WordPress site and Elementor page builder, which gave the team wide creative freedom without guardrails. Small inconsistencies built up page by page until the brand drifted across the site.

"It wasn't intentional. It wasn't that they didn't have the skill or the capabilities," Teitzel said. Without guardrails, he added, "the site can go off the rails very quickly."

Cellar Door first built a code-based design system in Next.js for the company's staff and its AI agents to use beyond the website, with output into tools such as Figma. The team then mapped and migrated more than 600 pages into P1, with Claude handling much of that work.

"We did it in about 11 weeks and a good four or five of that was just building the design system and then the other piece was just migrating it into P1," Teitzel said. Two years ago, he estimated, a decoupled Next.js site of that scope would have taken about six months. "The bots moved everything over super fast."

'Rough Around the Edges' But Worthy in the Long Run

Teitzel pitched the company on being first through the door and was upfront about the tradeoff. "It's going to be a little rough around the edges," he recalled telling the company.

"And it wasn't hard to convince," he said. He credited their appetite for AI.

Where P1 Fits Alongside an Existing CMS

For simpler sites, Teitzel said P1 can take over the whole job. "So P1 could act as the CMS. It does act as the CMS for a simple site." That includes marketing sites and small businesses that want to update pages directly or by prompting ChatGPT or Claude.

Organizations with heavy structured content, such as university course catalogs or retail product catalogs, should keep that data in a structured system and pipe it into P1 for display, he said. Content stored in P1 is "very dedicated to P1," which limits reuse in other systems. Cellar Door has one site in progress that will likely combine three data sources in P1.

"It definitely doesn't replace a CMS. It just augments whatever you have already," Teitzel said. "We're big proponents of just use the tech that's the best for the job."

For teams without that infrastructure, his advice was direct: "But if you don't have all the infrastructure behind it and you're starting that new and you already have a component library, just use P1. It's great."

What Changes for Agencies: Time to Market Normally Out of Reach

Teitzel said the timeline would have been out of reach for Cellar Door before. "We would have never done that before," he said. "P1 is showing how an agency with AI with the right tooling can just fly."

Pantheon's Web Operations Evolution

Though somewhat dwarfed by the P1 unveil, Pantheon has moved to expand its historic, core WebOps platform beyond WordPress and Drupal, with managed Next.js hosting reaching general availability in April and a host of core platform improvements announced at GoLive Miami, oriented around streamlining larger scale site fleet management.

The April Next.js release delivered a managed container runtime on Google Cloud Run with global CDN, persistent caching, HTTP Streaming and Git-based Dev/Test/Live workflows — unifying modern frontends with legacy CMS stacks under a single pipeline.

The company's AI integrations extend through its Content Publisher tooling, which launched in public preview in September 2025 and enables teams to publish from Google Docs to Drupal, WordPress or Next.js sites in near real time. By February, Pantheon placed a Content Publisher MCP Server into public beta, allowing AI agents such as Claude and ChatGPT to orchestrate content workflows directly. The company also joined the Drupal AI initiative as a Gold member in October 2025.

Pantheon's strategic arc culminated in September with the unveiling of Agentic Fleet Management, introducing fleet-level traffic insights, a Site Administrator role and a next-generation CDN with bot protection. Supporting State of the Web 2026 research found roughly 80% of marketing, engineering and IT leaders cite manual validation as the primary barrier to scaling AI.

The Web Ops & CMS Platform Market

Pantheon joins a host of vendors in the digital experience space who are investing frantically to evolve their platforms for emerging operating models.

Webflow launched Source in September, giving marketing teams and AI agents simultaneous, governed access to site code within an agentic workspace. The approach aligns with what Forrester has described as agentic digital experience platforms. These are goal-seeking environments that actively coordinate composable components rather than serving as passive toolkits.

Several vendors have moved governance to the architecture layer:

• Sitecore rebranded its offering as SitecoreAI and deployed 20 AI agents via Agentic Studio across campaign planning and content migration

• Kontent.ai released an agentic CMS targeting governance, compliance and translation automation

• WordPress.com expanded Model Context Protocol integration so agents can draft, edit and publish with user approval

The model context protocol (MCP) standard is central to this shift, enabling agents to interact in real-time data with these systems, performing tasks at a depth, speed and scale not previously possible, and in some cases, enabling a new kind of agentic marketing and personalization.

Pantheon P1 Feature Breakdown

Pantheon says P1 addresses limitations of legacy headless CMS platforms for AI-driven web operations by bringing together a mature set of what co-founder Josh Koenig described today as Pantheon Primitives combined with a layer of new operating and agentic choreography and emerging capabilities like Next.js hosting and Content Publisher integration with diverse authoring enironments.

Capability	Description
Component-based architecture	Page-building interface using React components governed by a central design system, organized in a collaborative library and surfaced in the experience designer backoffice UI.
Multiplayer mode	Real-time collaboration between humans and AI agents with identity management, role based permissions and chat-based human-to-human and human-to-agent collaboration.
Work stream-based workflows	Work streams form the basis of operational work and support versioning, branching, granular release packaging and minimal clicks to live flow. Notably work stream comprise both content and code, a capability that scant few platforms offer today.
Native Next.js front-end	P1 front end experiences are packaged as Next.js apps and deployed natively to Pantheon's Next.js infrastructure.
Agent first, agentic orchestration	AI and humans work in parallel with transparency and accountability. Agentic work can happen interactively in the backoffice UI via the Zappy agent, or via MCP and remote agentic tooling / platforms. Agents can be assigned unique identities in the platform with their own roles and permissions. MCP connections can impersonate a platform user or be assigned a key-based identity with its own permissions.

Pantheon Background

Pantheon is a WebOps platform serving cross-functional web teams at enterprises, universities and nonprofits. Founded in 2010 in San Francisco, it has raised several rounds of funding over the years, including $100 million in Series E funding led by SoftBank Vision Fund 2 in July 2021. The company offers managed cloud infrastructure, automated deployment workflows and multi-site management for WordPress, Drupal and Next.js.

The company's new P1 platform marks a significant new chapter for Pantheon as it moves further into the operational stack to compete directly with traditional CMS platforms.

Have a tip to share with our editorial team? Drop us a line: