# keel.run documentation

keel.run is an EU developer cloud. It builds and runs container apps from Git or a local directory – web services, workers and cron jobs, with preview environments per pull request – and offers managed Postgres and serverless Valkey, on Hetzner servers in Germany and Finland. Everything you can do in the dashboard also works through the [REST API](/docs/api), the [`keel` CLI](/docs/cli) and a [remote MCP server](/docs/agents) for coding agents.

> keel.run is in beta: there is no SLA yet. Current availability and incidents: [status.keel.run](https://status.keel.run).

## Start here

- [Getting started](/docs/getting-started): sign up, deploy your first app from GitHub, GitLab or Codeberg, and use the CLI.
- [Services](/docs/services): sources, builds, runtime settings, variables and domains.
- [Databases](/docs/databases): managed Postgres, linking it to an app, connecting from your machine, backups and restores.
- [Mail](/docs/mail): mailboxes for your domains, webmail, aliases and forwarding; [App mail](/docs/mail-sending) for transactional mail and inbound webhooks.
- [Agents](/docs/agents): connect Claude Code or another MCP client, scopes and confirmations.
- [Billing and limits](/docs/billing): plans, usage, spend limits and what happens when you reach them.
- [Security](/docs/security): how tenants are isolated and where your data lives.

## Concepts

```text
Workspace            billing, plan, spend limit, API tokens
 └─ Project          a group of things that belong together, e.g. "shop"
     └─ Environment  production, staging, …: one isolated network each
         ├─ Service      a container app built from Git or a container image
         │   └─ Deployment   an immutable release: commit, image and configuration
         ├─ Database     managed Postgres
         └─ Variables    environment variables and secrets
```

- **Workspace** (`ws_…`): the billing unit. It has a plan, an optional spend limit, API tokens and an audit log.
- **Project** (`prj_…`): groups environments. Every project starts with a `production` environment.
- **Environment** (`env_…`): an isolated network. Services in the same environment reach each other by name (`http://api:8080`); nothing outside it can.
- **Service** (`svc_…`): an app built from a Git repository or deployed from a container image. It gets an HTTPS hostname such as `https://web-shop.keelrun.app`.
- **Deployment** (`dpl_…`): every deploy creates one. Its status goes `queued → building → built → releasing → deploying → active`, or ends as `failed` or `cancelled`. When a new deployment becomes active, the previous one becomes `superseded` and you can roll back to it.
- **Database** (`db_…`): a managed Postgres cluster in an environment.

IDs are stable; names can change. The API, CLI and MCP tools accept IDs everywhere and names where they are unique.

## For agents

Every page of these docs is also available as Markdown: add `.md` to its URL, for example [/docs/getting-started.md](/docs/getting-started.md). [/llms.txt](/llms.txt) lists all pages, and [/llms-full.txt](/llms-full.txt) is the whole documentation in one file.

## Status and support

- Platform status and incidents: [status.keel.run](https://status.keel.run).
- Every API error carries an `X-Request-Id` header. Include it when you contact support.
- Abuse reports: `abuse@keel.run`.
