Deleting commit… Deleting commits…
kad.dev · docs

The docs. All of them.

The product is small on purpose, so the manual fits on one page. Paste a Git URL, it builds, it's live — you would have figured that out without us. This page covers the part people actually get wrong.

The part you already guessed

GitHub, GitLab, Bitbucket, Codeberg or any Git URL. The framework is detected, the build streams live, and a failed build comes back with a diagnosis instead of a shrug. There is no step two. Included here for completeness.

No account yet? A public repo or a folder on your machine deploys without one, for 72 hours.

Every commit keeps its URL. Exactly one is canonical.

Deploy a commit and it gets a URL of its own — your-app-a1b2c3.kad.run — which keeps working for as long as the deploy exists. Deploy ten commits, keep ten URLs.

One commit at a time is canonical: it also answers on the bare host, your-app.kad.run. Promote makes a commit canonical; demote takes that back. There is no separate rollback feature, because promoting an older commit is the rollback.

Static assets are cached at the CDN edge for a few hours. Promoting or changing a commit's visibility clears that cache automatically — and if your framework fingerprints asset filenames (Vite, Next.js and friends do by default), you were never going to notice anyway.

a commit's own URL, the canonical PROD host, and where Promote lives

New deploys are private. Yes, even the link you just sent.

A private URL answers 302 → /unauthorized to everyone who is not you. You are signed in, so to you it looks fine. Your client is not, so to them it looks broken. This is our most reported non-bug.

Every fresh deploy starts private. Before you share a link, expose that commit — select it in the graph, then Actions → Make public — or turn on the project's default-public setting and never think about it again.

select a private commit → Actions → Make public

Postgres and a bucket

One click each, from the project page. Postgres injects DATABASE_URL; storage injects S3_ENDPOINT, S3_BUCKET and credentials. Read them from the environment at runtime — nothing to copy anywhere. Both run in the EU, next to your app.

Settings → Storage — Provision Postgres, then Object Storage — env var names go live

Custom domains

Settings → Domains. Add www.your-client.com, create the CNAME the UI shows you, and TLS issues itself. The .kad.dev host keeps working alongside. That is the entire feature.

Settings → Domains — a custom domain verified, TLS issued

Or let an agent read this instead

kad.dev speaks MCP. Point Claude — or any MCP client — at kad.dev/mcp and it can create projects, deploy, expose, promote and read build logs, on your account, within your limits. It gets the same rules you just read, as tool descriptions.

One token may make about 30 tool calls a second, and read one app's status about once a second. Past that, a call answers "Rate limit hit" with the number of seconds to wait, and runs nothing. Your app is not affected. Builds are shared fairly: one account runs two builds at once, and the next ones wait in the queue as PENDING.

Connect an assistant

  1. In Claude, open the kad.dev listing in the connectors directory and press Connect. In any other MCP client, add a remote server with the URL https://kad.dev/mcp.
  2. Sign in with your kad.dev account when the client asks. The consent screen lists the two scopes: mcp:read (status, logs, files) and mcp:deploy (create, deploy, promote, settings).
  3. Ask for something concrete: "deploy this folder to kad.dev", "what is the status of my app", "show me the last build log". Read tools run without a prompt; tools that change production ask you first.

To disconnect, remove the connector in your client, or revoke its grant from the key icon in the dashboard header, under Chat connectors. Nothing in a conversation is stored on kad.dev: a tool call carries only its arguments, and the answer carries only the project data it names.

Still comparing hosts?

What 12 hosts give you for free, in one table, with a source for every number. The short version:

HostCommercial useDatabase
kad.devYes; best effort, no SLAPostgres, 1 per project, with an app, not on its own; 5 GB of storage in all per account
FirebaseYesFirestore, 1 GiB; Postgres as a 3-month trial
NetlifyYesPostgres: up to 3, 5 GB each
RailwayYesany open-source database, on a 500 MB volume
RenderDocs: not for production applicationsPostgres: 1 GB, expires after 30 days
SupabaseYesPostgres: 500 MB, 2 active projects
VercelNo: personal, non-commercial onlyno relational database of its own; Marketplace providers
BUILT SLOWLY · SOLO · EU-HOSTED | BUILD d44087f