For developers · Ample Computer

Infrastructure, finally boring.

Ample reads your repo, works out what it needs and runs it: its own VM, a managed database, HTTPS, logs your coding agent can read. One command, and a clear answer when it’s done.

The files you don’t have to write.

No Dockerfile to babysit, no pipeline YAML, no Terraform, no cron job renewing certificates. Ample reads the repo and works out the rest. You get one small file you can read in ten seconds.

−0/+0 lines

+ample.toml11

[app]
name = "ledger"

[services.web]
build = "auto"
port = 3000

[databases.main]
gine = "postgres"

[buckets.uploads]

Follow one request all the way down.

Every layer is there. You didn’t configure any of them.

  1. Your domain, with TLS

ledger.yourco.com. Certificates issued and renewed automatically.

  1. CDN

Static files and buckets served close to whoever asked.

  1. Your app, in its own microVM

Own kernel, isolated from everyone else. Sleeps when idle, wakes in a fraction of a second.

  1. Managed database

Postgres, MySQL, Redis or MongoDB, picked from what the code needs. Connection string handed to the app.

  1. Watched, every minute

Process, health endpoint, logs and database. Problems flagged with how to fix them.

One run. One answer.

Deploys are synchronous and content-addressed. Run it once, read the exit code. Run it again with nothing changed and nothing happens, which is exactly what should happen.

0 live The URL is in the output. Done.
1 failed Read why with ample logs --kind build. Fix, run again.
2 needs input Needs something from you, like an answer to a plan question.

Made by people like you.

Every app here is live at its own link. Want your own version? Copy the prompt and paste it to your assistant.

$ curl /api/entries

API Response

GET /api/entries 200
POST /api/entries 201
health ok
✓ live

API References

Go write the app.

We’ll be over here, keeping it running. Quietly.