Introduction #
Most teams stitch together five tools that don't talk to each other: a tracker, a ticket queue, a planning calendar, a docs app, and a spreadsheet for who-can-do-what. Trackr collapses all of that into one workspace where the data stays connected and the command palette reaches everything.
This guide walks you from a fresh instance to a running project: checking your organization, inviting your team, setting up roles, and shipping your first task. If you'd rather just explore, hit ⌘K anywhere in the app to jump to anything.
What you can build #
Project tracking
List or board views, grouped by project, status, assignee, or priority. Always in sync.
Capacity planning
Plan tasks onto days, set a weekly limit, and see over-commitment before it happens.
Support inbox
A shared ticket queue with a client portal. Convert a ticket into a task in one keystroke.
Team wiki & notes
Long-lived docs and runbooks with real-time collaborative editing.
CLI & TUI
Create tasks, triage tickets and read your inbox from the terminal.
iOS app
The reactive slice of Trackr on your phone: tick off, quick-add, reply, log time.
How the pieces fit #
Trackr is one repository with four deployable parts that evolve together:
| Part | What it does |
|---|---|
| Web app | The product core. Owns the database schema, the HTTP API and the collaboration server. |
| Worker | Drains the job queue: emails, webhooks, push notifications, digests, cleanup. |
| Scheduler | Enqueues recurring jobs on a schedule. Never does work itself. |
| Clients | The trackr CLI and the native iOS app, both talking to the same /api/v1. |
The whole system runs on Postgres, one Bun-based web app and two Go binaries. There is no message broker and no separate real-time service: the queue is a table, and collaborative editing runs inside the web process. See Self-hosting for the full picture.