Glossary
The terms you’ll meet across these docs, defined once. Each links to the page that covers it in full. Unlike the rest of the reference section, this page spans the whole product — not just the API.
organization
Section titled “organization”Account : Your individual login identity on managed.dev. An account can belong to many teams and owns its own API keys.
Team : The unit of ownership and billing. Sites, projects, and members live under a team, and roles — owner, admin, site_manager, observer, billing — are granted per team.
Project : A grouping of sites within a team, used to organize a fleet and scope access. See projects.
sites & environments
Section titled “sites & environments”Site : A single hosted application — your WordPress install, static site, or other runtime. A site belongs to a project and has one or more environments.
Environment : An isolated copy of a site — its own database and files — that a branch deploys to. Each is a production, staging, or preview environment. See the environments overview.
Production
: The live environment your default branch (e.g. main) deploys to, serving real
visitors. See branch routes.
Staging : A long-lived clone of production for pre-release QA, fed by a designated branch. See the staging workflow.
Preview : An ephemeral, fully isolated environment provisioned for a branch — seeded from production with its own preview URL. See preview environments.
Branch route : The rule mapping a git branch to a target — production, staging, preview, or ignore. See branch routes.
runtime & capabilities
Section titled “runtime & capabilities”Runtime
: What a site is — wordpress, static, and on the roadmap drupal/node. The
runtime determines which capabilities a site advertises. See
runtimes & capabilities.
Site profile : How a repo is detected and built — bedrock (the git-deploy WordPress profile), vanilla, or static. See build runtimes.
Capability : A machine-readable statement of what a site can do — install plugins, run cron, query the database, exec a shell. Clients discover capabilities instead of assuming a runtime.
build & release
Section titled “build & release”Build : The step that takes your repo, compiles/assembles it in an isolated sandbox, and produces an artifact. See the build pipeline.
Artifact : The content-addressed, signed output of a build — the immutable thing that gets deployed. See the pipeline.
Deployment : The act of rolling an artifact onto an environment. See promote & rollback.
Release : A deployed artifact running on an environment — what’s live right now, and what you roll back from. See promote & rollback.
Snapshot : A point-in-time capture of an environment’s database and files, used to roll back or restore in a click.
delivery
Section titled “delivery”Preview URL
: The live, shareable address of a preview environment, e.g.
https://<site>-<branch>-<hash>.preview.managed.dev. See
preview environments.
Magic link : One-click, password-free SSO into wp-admin from the dashboard — no shared credentials. See magic link.
security
Section titled “security”WAF : The web application firewall (Coraza engine) in front of every site, blocking injection, XSS, and traversal attempts. See WAF & rate limiting.
Patchstack : Virtual patching that shields known plugin/theme CVEs at the edge before a fix is applied. See Patchstack.
observability
Section titled “observability”RUM : Real-user monitoring — performance data collected from actual visitor sessions, not synthetic tests. See web vitals.
p95 : The 95th-percentile latency — the response time 95% of requests beat. A truer health signal than an average. See web vitals.
Job : An asynchronous operation. A non-instant mutation returns a job you poll or stream to completion. See async jobs.
Scope
: A permission on an API key, in the form
product.resource:action, gating exactly what the key can do. See
scopes and the scope catalog.
Idempotency key : A client-supplied header on a write that makes a retry replay the original job instead of running it twice. See idempotency.
Cursor
: The opaque token that drives pagination — pass the
next_cursor from one page to fetch the next. No offsets.