Install

NullTickets ships as one static binary with SQLite vendored in. There is no database server to run and no language runtime to install.

Release binary#

Each release attaches prebuilt binaries for seven targets:

Download, mark executable, run:

curl -LO https://github.com/nullclaw/nulltickets/releases/download/v2026.5.29/nulltickets-macos-aarch64.bin
chmod +x nulltickets-macos-aarch64.bin
./nulltickets-macos-aarch64.bin --port 7700 --db tracker.db

Releases use CalVer (v2026.x.y). There is no Homebrew formula or install script; the binary is the whole product.

Build from source#

You need Zig 0.16.0 — exactly that version, not "any recent Zig". SQLite is vendored as a static dependency, so there is nothing else to fetch.

git clone https://github.com/nullclaw/nulltickets
cd nulltickets
zig build

The binary lands at zig-out/bin/nulltickets. To build and start in one step:

zig build run -- --port 7700 --db tracker.db

Defaults are --port 7700 and --db nulltickets.db. See Configuration for the config file and environment variable.

Verify the build#

zig build test            # unit tests
bash tests/test_e2e.sh    # end-to-end API flow

The e2e script drives a full claim → events → transition cycle against a live server. If it passes, your build works.

Via NullHub#

If you run the wider Null stack, NullHub can install and supervise NullTickets for you — the repo exports a NullHub manifest (src/export_manifest.zig) and supports JSON config bootstrap (src/from_json.zig).

nullhub install nulltickets

Docker#

A Dockerfile ships at the repo root. No published container image is documented, so build your own if you want the tracker containerized.

Next: Quickstart — from an empty database to a completed task.