You can put an app online on kad.dev without signing up: a server process, a Postgres database and a file bucket included. Run curl https://kad.dev/ and then the command it prints. The app is a temporary project: it is removed 72 hours after it is created, data included, unless you keep it.
From a folder, with one command
There is no CLI to install and no repository host: you need curl and tar.
curl https://kad.dev/
The answer is a link, https://kad.dev/<key>, and one command that sends the app in the current directory to that link as a tar archive. The link works for 1 hour. Run the command in the app's root directory. The reply is plain text, with the app's URL and a command that follows the build. Each run of that command waits for the next step, then prints it (step: 2/4 build) and the time usually left.
Options go in the URL, inside the quotes:
| Option | Effect |
|---|---|
name=my-app |
The name, which becomes part of the URL. |
&postgres=1 |
A Postgres database; the app reads DATABASE_URL. |
&storage=1 |
An S3-compatible bucket: S3_ENDPOINT, S3_BUCKET and the keys. |
&api=<name> |
Serves /api/* of this app from another app of the link: see A full-stack app. |
&framework=<preset> |
The preset, when detection picks the wrong one. |
From a coding agent
Paste one line into Claude Code, Codex, Cursor, OpenCode or another agent that has a shell. The home page shows the line with your link in it.
deploy this app with https://kad.dev/<key>
The agent reads the link, which holds the same upload command and its rules. It sends the files, follows the build and gives you the URL. It needs no MCP server and no sign-in. The same key also works on the MCP server, for logs, environment variables and rollback.
A full-stack app
There are two ways to deploy a front end and an API.
One app. Upload once: the server serves the pages and the API on the same host, next to its database and its bucket. Next.js, Django, or a FastAPI or Go server that also serves the front end's files all fit. The front end calls /api/... with no second URL and no CORS setup. If the front end is a separate React, Vue or Svelte project, build it and let the server serve the build output.
Two apps on one link. A link holds at most 2 apps, picked by name=. Upload the API first, with its own name. Its routes must be under /api. Then upload the front end with &api= and the API's name:
curl -T - "https://kad.dev/<key>?name=shop-api&postgres=1"
curl -T - "https://kad.dev/<key>?name=shop&api=shop-api"
https://shop.kad.run/api/* is then served by shop-api. The front end calls /api/... with a relative URL, so there is no CORS and no second URL in the code. The path is not stripped: the API sees /api/.... The mount is on the front end's main URL, not on a version URL. A new upload of the front end keeps the mount; &api=none removes it.
From a public Git URL
Paste the URL of a public repository on the home page, pick a branch or tag, deploy. A private repository needs a GitHub App, so an account.
Rules of the upload
- The file list comes from git: tracked files, and new files that
.gitignoredoes not exclude. The answer has a second command for a directory that is not a repository. - At most 2000 files and 25 MiB. Leave out dependencies and build output: the build installs and builds.
.envfiles are never accepted: they are dropped and the reply says so. Do not put secrets in other files.static,viteandastrorun no server process, so they cannot use the database or the bucket.- The same command again sends a new version; a file that is no longer in the archive is removed.
curl -sS -X DELETE "https://kad.dev/<key>"removes the app for good.
Keep the app
The app is private at first. The reply has an open link: in your browser it shows the app and its dashboard after one confirmation, and it is where you sign in with GitHub or Google to keep the app.
If you already have an account, sign in first and copy the link from the home page. Then the app lands in your account, as a temporary app that you can keep. The platform limits apply to it like to any other app.