Bring your portfolio, requirements, and questions about the operating model to review responsibilities, platform fit, and possible next steps with Pantheon.
Self-hosting vs. Pantheon
Is self-hosting still the right approach for your web portfolio?
If your team self-hosts today, the question isn’t whether the model works. It’s whether the engineering time spent to maintain the web estate remains justified as the portfolio grows.
Infrastructure requirements and in-house expertise may shape the decision to continue self-hosting, but they don’t remove the ongoing operational overhead.
Pantheon is a managed platform for WordPress, Drupal, and supported Next.js sites, built for teams that want their engineering time back. Its WebOps layer takes on much of that work, while your team retains ownership of the application and how it is governed.
Discover the difference between self-hosting and Pantheon across infrastructure, security, development, governance, and support.
Image
Image
What could your team accomplish with less operational overhead?
Pantheon manages the platform and infrastructure layer, while your team keeps ownership of the website and remains responsible for application code, governance, and business continuity.
Compare the models against the engineering capacity it demands, the architectural and control requirements it must satisfy, and its ability to sustain a growing portfolio.
The table below shows how responsibilities shift to your team and makes the tradeoffs clear, while keeping site scope and requirements consistent across models.
Area | Self-hosted infrastructure | Managed on Pantheon |
| Infrastructure and operations | Your team selects and operates the infrastructure and services, including setup, scaling, maintenance, and troubleshooting. | Pantheon provides a managed environment and WebOps layer for supported sites. Your team continues to own application code, integrations, and architecture decisions. |
| Security and updates | Your team coordinates controls, patching, testing, and the path from a change to production across the stack. | Pantheon provides platform capabilities and workflows for supported sites. Your team remains responsible for application-level security, access, and governance. |
| Development and releases | Your team owns the development, testing, and deployment across the tools and teams supporting the portfolio. | Teams can use Pantheon's Dev, Test, Live environments and deployment workflows to move changes through development and testing toward production. |
| Governance and visibility | Your team coordinates site ownership, access, updates, monitoring, and controls across providers and teams. | Pantheon provides shared visibility and workflows for sites managed on the platform, including Workspace Traffic Insights and Upstreams for standard codebases. Your team retains policy and business-level governance decisions. |
| Support and recovery | Your team defines how infrastructure and application issues are monitored, escalated, and recovered, including which providers and partners are involved. | Pantheon adds platform monitoring and support for supported sites. Your team still owns application response and business continuity decisions. |
Make the decision against your operating reality.
Compare the models against the requirements specific to your team:
- Site count, CMS mix, and how quickly the portfolio is changing.
- Ownership of patching, releases, monitoring, incident response, and recovery.
- Publishing delays, engineering capacity, and the work that gets pushed back.
- Reliance on a small number of engineers for operational knowledge and on-call responsibility.
- Cloud commitments, controls, integrations, and architecture that must remain in place.
A review can clarify tradeoffs and platform fit without assuming migration is the answer.
Image
Explore Customer Stories
These stories show how the demands of each web estate shaped two teams’ decisions. They are examples, not a verdict on every self-hosted environment.
Choose the model that leaves room to move your web estate forward.
Frequently Asked Questions
What is the difference between self-hosted and managed hosting?
The difference is who is responsible for running the infrastructure. With self-hosted, your organization owns the work behind platform operations, security, updates, monitoring, releases, and recovery. On a managed platform such as Pantheon, the provider runs the infrastructure layer, while your team remains responsible for application code, integrations, access, and governance decisions. Learn out more about the difference between self-hosting and managed hosting here.
How should organizations evaluate self-hosting?
The decision depends on the requirements and expertise behind the current setup. Self-hosting still leaves the organization responsible for maintaining security, reliability, and scalability. Assess whether your team can sustain those responsibilities as your web estate grows.
What should we include when comparing self-hosting costs?
Look beyond infrastructure and tooling bills. Account for the engineering and operations capacity required to build and run securely and reliably. Compare the same site scope and requirements on both sides; actual costs vary by organization and architecture.
Which CMSs and frameworks does Pantheon support?
Pantheon supports WordPress and Drupal. Next.js sites are available to customers with Gold, Platinum, or Diamond Workspaces, and the product capabilities differ by framework. For other CMSs or architectures, confirm compatibility and product fit with Pantheon.
Can we move an existing web estate to Pantheon?
Yes. For teams running websites on self-managed infrastructure, whether in the cloud, on-premises, or across a hybrid environment, Pantheon provides a managed WebOps layer that reduces operational burden while preserving framework and application choices.