| role | publish | delete | deploy | api-keys | read |
|---|---|---|---|---|---|
| admin | ✓ | ✓ | ✓ | ✓ | ✓ |
| editor | ✓ | ✓ | — | — | ✓ |
| author | — | — | — | — | ✓ |
| viewer | — | — | — | — | ✓ |
Self-hosted content infrastructure for teams who read the dependency tree before the feature list. No SaaS landlord. No vendor lock-in. Just raw publishing power running entirely under your control.
Platform risk is a line item your CFO hasn't budgeted for yet.
In the last 18 months, three major SaaS CMS vendors raised prices an average of 340%. One sunset its legacy API with 90 days notice. Another was acquired and immediately began migrating customers to an enterprise-only tier.
Agencies running 40+ client sites on hosted platforms aren't customers — they're hostages. Every renewal cycle is a negotiation you're losing because switching costs compound every year you wait.
The self-hosting resurgence isn't nostalgia. It's engineering teams doing the math on total cost of ownership and realizing that infrastructure you control doesn't have a pricing page.
Monthly infrastructure cost
Forge vs. leading SaaS CMS vendors. Mid-tier usage. All numbers sourced from public pricing pages.
* Excludes server hardware amortization. Self-managed VPS from $12/mo.
4ms API responses. Not a typo.
When your CMS runs on your hardware, there's no multi-tenant rate limiting, no shared CDN queue, no vendor throttle on content delivery. The p95 response time for Forge's content API is 4ms on a $12/mo Hetzner VPS.
SaaS vendors optimize for median performance across millions of tenants. You get the average. Forge is yours alone — optimized for your workload, your traffic patterns, your query shapes.
API latency & uptime comparison
Measured from AWS us-east-1. Forge on $24/mo Hetzner CX31. February 2026.
* All measurements from public status pages + independent monitoring. Methodology available on GitHub.
Your compliance officer already vetoed the hosted option.
HIPAA, GDPR, SOC 2 — every major compliance framework has the same clause: you are responsible for where your data lives. "But it's in their cloud" is not an acceptable answer to a regulator.
Enterprise teams aren't choosing self-hosted CMS because it's cheaper (though it is). They're choosing it because their legal team requires a signed BAA, a data processing agreement, and proof that content never transits a jurisdiction they haven't approved.
Framework coverage
Forge's architecture is designed to satisfy the most demanding compliance requirements out of the box.
One command. Zero downtime.
The migration playbook covers WordPress, Contentful, Sanity, and Strapi. The CLI handles schema mapping, media migration, redirect generation, and DNS cutover coordination — with a rollback checkpoint at every stage.
Agencies migrating 40-client portfolios use the batch migration mode: one config file, one run, 40 sites transferred with audit logs for each.
Request a Private Demo
A Forge engineer will walk through your specific infrastructure setup, migration path, and compliance requirements. No slides. No sales deck. Just a terminal and your questions.