Introduction

managed.dev is managed WordPress hosting with a real git workflow. You connect a repository, push a branch, and get a fully isolated environment with a live preview URL — then promote that branch to production when it is ready. The platform that runs all of this is the Managed.dev Forge Platform — Forge for short — and as a customer you only ever see managed.dev.

If you have used a modern application platform — branch deploys, scoped tokens, an API for everything — and wished your WordPress host worked the same way, this is that host. Nothing here asks you to touch Docker, a registry, or a deploy key.

The core loop

Day-to-day work on managed.dev is a short, repeatable loop:

1. Migrate or create a site. Existing sites move in free, white-glove, and are reviewed on a branch before any cutover. New sites are created from a repository or a starter.
2. Push a branch. Run git push managed <branch> and managed.dev provisions an environment with its own database and files, seeded from production, and hands you a preview URL. The default branch deploys to production; other branches map to staging or preview through branch routes.
3. Review and promote. Share the preview, run QA against real data, then promote the branch to production. If something regresses, roll back instantly from a snapshot.

The thing that makes this practical is that branch environments are available on every plan, not gated behind an enterprise tier. Branch environments shouldn’t be a $500/mo enterprise feature — so on managed.dev they aren’t.

Who it’s for

Agencies

Group client sites into projects, give each client a preview URL to sign off on, and keep staging and production cleanly separated. Free migration moves existing portfolios in.

In-house teams

Wire branch environments into CI so every pull request gets a reviewable URL, enforce access with teams and roles, and automate the rest through the public API.

Solo developers

Get the same git deploy, SSH + WP-CLI, caching, TLS, and observability that larger teams use — on the Starter plan, with a 14-day free trial.

How these docs are organized

The documentation has two halves, and the home page sends you into either one:

• Platform guides cover operating WordPress on managed.dev from the dashboard and the command line — environments and deploys, domains and TLS, the build pipeline, caching, the security pipeline, and observability.
• The public API is the Forge /v1 API: scoped mfk_ keys, a resource:action scope model, cursor pagination, idempotency, async jobs, capability discovery, and signed webhooks. Everything you can do in the dashboard is something you can automate.

Developer preview

The public API is in active development. The platform itself — branch environments, git deploy, SSH, security, observability — is shipped and in production. Endpoints, scopes, and payloads in the API section reflect the current design and may change before general availability.

Next steps

QuickstartFrom an account to a deployed site and a live preview environment in a few minutes.

Core conceptsAccounts, teams, projects, sites, environments, and runtimes — the model everything builds on.

Connect gitAdd the managed remote and ship with git push. A branch becomes a preview; main becomes production.

API overviewAuthenticate, page, and run async jobs against the Forge public API.