Start with the guide that matches the job.

urgentry 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.

Maintained by Wraxle LLC
Last updated
16 public docs routes on urgentry.com
4 core guides that should carry most first-time users
2 operator shapes: Tiny first, self-hosted when shared services are required
1 path install, verify, then widen the rollout only when the boring checks pass

These are the pages most people actually need.

If you are new to urgentry, start with one of these four guides before you read anything else.

Install

Getting Started

Build the binary, start the server, sign in, and send the first event.

Open guide
One binary

Tiny Mode

Use the SQLite-first path when you want the fastest route to a working DSN.

Open guide
Shared services

Self-Hosted Mode

Use the split-role path when your team already needs PostgreSQL, queues, and runbooks.

Open guide
Tradeoffs

Benchmarks

Read the memory, throughput, and query-latency numbers before you pick the operator shape.

Open guide

Pick the lane, then stay in it.

These path cards group the docs by the job you are trying to get done, not by the file tree behind them.

Every public docs page, grouped by intent.

Once you are past the first install, use these grouped lists to find the smaller reference pages without losing the main thread.

1 pages

Evaluate urgentry

Read the benchmark method alongside the headline numbers.

Need the shortest route?

Start with Getting Started, then move to Tiny mode, SDK setup, or support depending on what you are trying to prove next.