# kad.dev

> Managed PaaS hosted in the EU. A git repository URL becomes a live HTTPS
> app; every commit gets its own running deployment, URL and data timeline.
> Flat pricing (no usage metering). Managed Postgres and S3-compatible
> object storage included. MCP-native: agents can deploy, read logs and
> request approvals through the Model Context Protocol.
>
> The service is in public alpha. Keep your own backups.

## Docs

- [Documentation](https://kad.dev/docs): how deploys, previews, promote and managed backends work
- [Status](https://kad.dev/status): live platform status and incident history
- [Legal](https://kad.dev/legal): terms, privacy, subprocessors

## Agents

- [Agent setup prompt](https://kad.dev/agent-setup/prompt.md): fetch this to configure an MCP client for kad.dev
- MCP endpoint: https://kad.dev/mcp (OAuth 2.1 discovery at /.well-known/oauth-authorization-server)

## Docs pages

- [Deploy from a Git URL](https://kad.dev/docs/deploy): What the build runs for each preset, the port and health check, versions, the 72-hour project without an account, and the platform limits.
- [Commit URLs, promote and visibility](https://kad.dev/docs/preview-deployments): Every deployed commit keeps its own URL and one is canonical. Promote, demote, expose, stop and delete, and what each one does to the data.
- [Managed Postgres and object storage](https://kad.dev/docs/postgres-and-object-storage): The variables Postgres and the bucket inject, the SQL console and agent tools, the optional disk, restore points, and what is not offered.
- [Custom domains and TLS](https://kad.dev/docs/custom-domains): The DNS rows the Domains tab asks for, why the apex and wildcards are refused, the status badges, and which commit a custom domain serves.
- [MCP server and agent tools](https://kad.dev/docs/mcp): Connect a chat assistant or a coding agent to https://kad.dev/mcp, what the tools can do, the per-tool approval switch, and what the server keeps.