Deploys.
Rolling and health-checked; one action rolls back. Push to deploy, median build 41 seconds.
Databases.
Postgres and Redis with nightly backups, point-in-time recovery, and restores rehearsed weekly on a throwaway node.
One file.
duploy.toml is the source of truth. No dashboard state to drift; every change from panel or CLI becomes a pull request.
Domains & TLS.
DNS checked automatically; certificates issue and renew themselves. Nothing to click through.
One log stream.
Builds, deploys, cron runs, backups and node events in one place — panel and CLI show the same stream.
Your agent already knows the CLI
duploy skill writes a skill file that teaches coding agents the whole command set. Every command takes --json, and plans are dry-run by default — an agent stages the change, you approve the pull request.
AI writes the change. You stay the reviewer.
Everything, at a glance
The full set. Defaults, not add-ons.
Pricing
Questions we actually get
▸Do I need a Dockerfile?
No. Builds detect the stack from the repository; a Dockerfile wins if present.
▸Where does my app run?
On machines we own in Frankfurt (fra1) and Ashburn (iad1) — not resold cloud. Databases stay in-region.
▸What can an agent actually break?
Nothing directly. Agents work through the same staged changes as humans — dry-run plans, then a pull request you approve. Production only moves on merge.
▸Can I take my data and leave?
duploy export hands you the file, volume archives and pg dumps any time. No egress fee on the way out.