Getting Started
Build the binary, start the server, sign in, and send the first event.
Open guideurgentry has two kinds of docs: the core guides you use to get a real system running, and the smaller reference pages you reach for once you are already in motion. Start with the first kind.
If you are new to urgentry, start with one of these four guides before you read anything else.
Build the binary, start the server, sign in, and send the first event.
Open guideUse the SQLite-first path when you want the fastest route to a working DSN.
Open guideUse the split-role path when your team already needs PostgreSQL, queues, and runbooks.
Open guideRead the memory, throughput, and query-latency numbers before you pick the operator shape.
Open guideThese path cards group the docs by the job you are trying to get done, not by the file tree behind them.
Start with the DSN-swap path, compatibility proof, and same-host benchmark evidence.
Pick Tiny, verify the install, and get to a working DSN quickly.
Use the product and operator docs once traffic is live and your team needs supportable operations.
Once you are past the first install, use these grouped lists to find the smaller reference pages without losing the main thread.
Start the product, send the first event, and keep the evaluation loop short.
Use the DSN-swap path, compatibility boundary, and benchmark proof before cutover.
Validate the feature surfaces you already depend on before you trust a migration.
Follow the operator path once traffic is live and your team needs supportable runbooks.
Read the benchmark method alongside the headline numbers.
Start with Getting Started, then move to Tiny mode, SDK setup, or support depending on what you are trying to prove next.