Install and run
Tiny mode runs urgentry in one process on one machine.
Tiny mode uses one binary, one SQLite data directory, and one local runtime. Start here if you want to install urgentry, send a test event, and decide whether you need anything larger.
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.
Start here
Build it, start it, and verify it.
Keep the sequence short so you can see where the first failure happens.
make build URGENTRY_BASE_URL=http://localhost:8080 ./urgentry serve --role=all
make tiny-smoke
Deployment shape
Pick the smallest deployment that does the job.
Most first installs do not need more than a single binary. Use these links if you want the packaged install paths.
Docker install
Keep in mind
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_URLshould match the external URL- That keeps links in the UI and generated outputs stable
Next docs
Stay in Tiny mode if one machine is enough. Move to self-hosted mode when you need shared PostgreSQL-backed infrastructure, split roles, or operator workflows.