Mesh documentation
Deploy services from GitHub or Docker images, connect them on a private
network, and automate it all through the API or an AI agent.
Build and deploy
- Services A service is one workload in an environment: a web app, an API, a worker, or
a database. You describe what it should run, and Mesh keeps that many healthy
replicas running.
- Builds Mesh builds an immutable image from each commit of a repository service. A
build starts when you release a staged source change, when you push to the
tracked branch with auto-deploy on, or when you redeploy.
- Deployments and releases Changes to an environment are staged, then released together. Each release
starts one deployment per changed service, and every deployment is kept as
history you can inspect, redeploy, or roll back to.
- Environments An environment is an isolated copy of your application: its own services,
variables, volumes, domains, and private network. Use them for production,
staging, previews, or experiments.
- Variables Variables are environment variables for a service's process: database URLs,
API keys, feature switches. Each service has its own set in each
environment.
- Templates and databases Templates add ready-made services to an environment in one step: a database
with a volume and generated credentials, or a complete app with its database.
- Serverless A serverless service stops when nobody uses it and starts again on the next
request. While it sleeps it uses no CPU or memory, so you pay nothing for
compute.
Observability
- Logs Mesh collects build, deploy, and runtime logs for every service, plus HTTP
request logs from the edge. Read them in the console, through the API, or ask
an AI agent to read them for you.
- Metrics and usage Mesh measures what each service actually consumes: CPU, memory, volume space,
and public egress. The same measurements drive the service charts, the usage
reports, and your bill.
API and agents
- API overview The Mesh API is a versioned REST/JSON API for CI pipelines, scripts, and AI
agents. Everything the console does with projects, services, deployments,
domains, volumes, logs, usage, and billing, the API does too.
- API tokens An API token lets a script or CI job call the API as you. Each
token has a scope, an access level, and a 24-hour lifetime. AI agents do not
need one: they sign in through the MCP server and appear in the
token list as connected agents.
- API reference Every endpoint of the public API, generated from the route table that also
serves requests and the OpenAPI document. Request and response bodies are the
JSON mapping of the named platform.v1 messages; fetch
GET /v1/openapi.json for their full schemas. See
API overview for authentication, errors, and rate limits.
- MCP server Mesh is MCP-native. Your coding agent deploys, debugs, and manages your
services through the Mesh MCP server; the console shows the same state.