Install urgentry. Send one event. See it land.

This is the shortest honest path to a working Tiny-mode node. Build the binary, start the server, sign in with the bootstrap account, and push one real event through the ingest path.

Maintained by Wraxle LLC
Last updated
1 binary The first loop is one process on one host. No extra services required.
52.3 MB Tiny-mode peak memory on the current reference benchmark lane.
400 eps Same-host stable throughput once the first loop is running.
1 event The goal here is not a rollout. It is one event you can see with your own eyes.

Keep the first loop small.

You only need a local build toolchain, a free port, and enough patience to read one startup log.

Prerequisites

  • Go 1.26+
  • A free local port, usually 8080

First boot creates

  • a default organization
  • a default project
  • a bootstrap owner account
  • a bootstrap PAT
  • a default public ingest key

Build first. Then boot it.

Use the build command, then start the server with a base URL that matches where you plan to open it.

build
make build
start
URGENTRY_BASE_URL=http://localhost:8080 ./urgentry serve --role=all

Sign in

Open http://localhost:8080/login/ and use the bootstrap credentials printed in the startup log.

What to check

  • The server starts without errors
  • You can open the login page
  • The bootstrap credentials work on the first try

Push one event through the ingest path.

The first proof is simple: send an event, then make sure it shows up where you expect.

store event
curl -X POST http://localhost:8080/api/default-project/store/ \
  -H "Content-Type: application/json" \
  -H "X-Sentry-Auth: Sentry sentry_key=<public_key>,sentry_version=7" \
  -d '{
    "event_id": "abcdef01234567890abcdef012345678",
    "message": "Something went wrong",
    "level": "error",
    "platform": "python"
  }'

What you should see

  • The request returns cleanly
  • The issue shows up in the UI
  • The project, event, and message look sane

Next docs

Once the first loop works, pick the next page based on the job: stay in Tiny mode, move to self-hosted, or grab language-specific SDK snippets.