A real database, in one command.

No connection-string archaeology. Create a managed Postgres, and Miso stores the credentials as a secret and wires them straight into your service.

today

Postgres is the easy part

› One managed Postgres per project
› Connection string stored as a secret, attached to your service
› Automated backups on a schedule
› Restore to a fresh instance, proven by an actual restore
› Storage usage visible in the console

terminal

$miso db create --attach web

db.run

provisioning pg-15 ...

credentials -> secret

attached to web

backup scheduled daily

> _

backup.cfg

backups

0/day

automated

restore.chk

restore

proven, not promised

db.health

engine✓Postgres 15

credentials✓stored as secret

backups✓daily, automated

restore✓tested, to new instance

One command, one databasewired in, backed up, attached

The whole backend, next

Once the deploy core is solid, your database grows a full backend, an API, auth for your app's users, and the rest, all from the same console. Shipped in order, never promised before it is ready.

› Auto REST API from your schema
› Built-in auth for your app's users
› Row-level security
› Realtime row changes
› Object storage + buckets
› Scheduled jobs + cron
› Edge functions