One command · your infrastructure

From approved model to a live API. One command.

nuzur-cli deploy provisions a server, self-hosts your database, builds and runs your generated Go API behind automatic HTTPS, and pairs it all back to nuzur — on infrastructure you own, with credentials that never leave your machine.

$ nuzur-cli deploy --provider digitalocean --domain api.myapp.com
→ generating app · go-code-gen
→ provisioning droplet · nyc3
→ installing docker · database (localhost only)
→ building image · starting api
→ caddy · https via let's encrypt
→ applying schema · pairing agent
✓ live at https://api.myapp.com  ·  200 OK
How a deploy works

Four steps, one command.

Every deploy is idempotent — run it again to ship changes, and your hand-written code is preserved.

1

Generate

nuzur generates your Go backend from the approved model into a directory you own — git-friendly, and preserved across re-deploys.

2

Provision

Deploy to your own Linux server over SSH, or let nuzur create a VM through your own provider CLI. nuzur never sees a cloud token.

3

Bootstrap

Docker, your database (MySQL or PostgreSQL) locked to localhost, a least-privilege DB user, and the image built on the box.

4

Go live & tracked

Caddy fronts the API with automatic HTTPS, the schema is applied, and the deployment shows up in nuzur with live health — tear it down anytime with nuzur-cli destroy.

Supported providers

Your server, or a VM on your own cloud

For managed providers, nuzur shells out to that provider's own already-authenticated CLI to create the server — so your cloud credentials never pass through nuzur.

Your own server
DigitalOcean
Hetzner
Linode
Google Cloud
Microsoft Azure
Vultr
Scaleway

AWS support is on the way. Databases self-host on the box by default, or bring your own with an existing connection.

Why it's different

Production-ready, and yours to keep

One command, or one prompt

Run nuzur-cli deploy yourself, or let Claude drive the whole thing through the nuzur MCP server.

Your infrastructure, your credentials

Servers are created through your own provider CLI, and SSH keys and database passwords never leave your machine.

Your database is never exposed

The database binds to localhost only. nuzur reaches it through an outbound-only agent — no inbound database ports.

Automatic HTTPS

Pass a domain and Caddy provisions a Let's Encrypt certificate automatically. No certificate wrangling.

Code you own

The generated source lives in your own directory. Edit it, commit it, and re-deploys preserve your custom code.

Tear down anytime

nuzur-cli destroy cleans up the server, revokes its agent, and removes local state. Keep or purge the database as you like.

Flexible by design

Deploy exactly what you need

The default ships the full app and database, but you can mix and match.

Full app

API plus a self-hosted database on the box — the default.

Database only

Host and manage just a database, with no app, using --db-only.

Existing database

Deploy the API against a database you already run with --db-dsn or a stored connection.

Custom endpoints

Add your own REST or gRPC layer with --custom — preserved on every re-deploy.

Deploy with an agent

Or just ask Claude to ship it

The nuzur MCP server includes a deploy prompt that walks your agent through the entire deploy — provider, API surface, and the live URL — with you approving every gate.

Ship your backend to production today

Free for personal use. Install the CLI, connect your project, and deploy.

Start free

brew install nuzur/tap/nuzur · MySQL & PostgreSQL

nuzur mascot