Tiny mode is the short path to a working DSN.

Tiny mode runs the full product in one process with one SQLite data directory. It is the fastest way to evaluate urgentry on your own hardware before you decide whether you need anything larger.

Maintained by Wraxle LLC
Last updated
1 process Run the whole product without Postgres, NATS, object storage, or cache.
52.3 MB Peak memory on the current Tiny benchmark reference lane.
400 eps Same-host stable throughput for the Tiny line.
SQLite The data lives in one local directory until you decide you need a bigger operator shape.

Build it. Boot it. Verify it.

Keep the sequence simple so you know where something went wrong if it fails.

boot Tiny mode
make build
URGENTRY_BASE_URL=http://localhost:8080 ./urgentry serve --role=all
verify
make tiny-smoke

Pick the smallest deployment that does the job.

Most first installs do not need much more than a single binary. If you want packaging help, use one of these paths.

Tiny stays simple if you keep the data path simple.

Storage and backup

  • Tiny mode stores data under URGENTRY_DATA_DIR
  • Backup is a copy of that data directory or mounted volume

Base URL

  • URGENTRY_BASE_URL should match the external URL
  • That keeps links in the UI and generated outputs stable

Next docs

Stay in Tiny mode if the first loop is enough. Move to self-hosted when you need shared PostgreSQL-backed infrastructure, split roles, or operator workflows.