Platform guides
Operate WordPress on managed.dev: branch environments, deploys, domains and TLS, caching, the security pipeline, and observability.
Branch environments & deploys →
Security → · Observability →
~/acme-store ❯ git push managed feature/checkout managed.dev ▸ provisioning environment for feature/checkout managed.dev ▸ cloning database + files from production managed.dev ✓ environment live https://acme-store-feature-checkout-a1b2c3.preview.managed.dev
managed.dev documentation
Managed WordPress with a real git workflow. Push a branch, get an isolated preview environment, promote to production — and automate every step through a scoped, capability-aware public API.
managed.dev is managed WordPress that behaves like a modern platform. Every plan gets git-style branch environments, a FrankenPHP runtime, a real SSH gateway + WP-CLI, built-in security and observability, and a scoped, async-native public API for automating all of it.
Start here
QuickstartFrom zero to a deployed WordPress site and a live preview environment in a few minutes.
Core conceptsSites, environments, projects, teams, and runtimes — the model everything else is built on.
Deploy from gitConnect a repository and ship with git push. A branch becomes a preview; main becomes production.
Migrate a siteMove in from WP Engine, Kinsta, Pantheon, or a raw VPS — reviewed on a branch before cutover.
Two ways in
Public API
The Forge /v1 API: scoped mfk_ keys, a resource:action scope model,
cursor pagination, idempotency, async jobs, capability discovery, and signed
webhooks.
Popular guides
Go-live checklistDomain → DNS → TLS → cache → search-replace, the whole launch in order.
A preview environment per pull requestWire branch environments into CI so every PR gets a live, reviewable URL.
Connect via SSH + WP-CLIRun WP-CLI against any environment through the ssh.managed.dev gateway.
Migrate from WP EngineA step-by-step move from WP Engine onto a branch, then a zero-downtime cutover.