Skip to main content
Henrik Albihn
Henrik Albihn
Creator of ticket-rs

​
It’s Time

A 9MB Rust binary that runs graph analytics on your backlog in under 25 milliseconds. No daemons, no databases, no SaaS. Today, ticket-rs enters public alpha. I’m ready to let other people break it.

​
What You’re Getting

A single Rust binary. ~9MB. Zero dependencies. No daemons, no databases, no SaaS subscription. Issues stored as markdown files in .tickets/, versioned alongside your code in git. Dependencies modeled as a directed acyclic graph. Graph algorithms (PageRank, betweenness centrality, critical path) running over that graph to tell you what matters. All of it completing in under 25 milliseconds on your local machine.

Graph-Powered Triage

tk triage runs PageRank, critical path analysis, and betweenness centrality to find what matters most. Not what’s oldest. Not what someone manually flagged P0. What the dependency structure says is important.

AI-Native

Context-aware output for Claude Code, Cursor, and Windsurf. SessionStart hooks, MCP server, structured JSON. Point your agent at the skill docs and go.

Zero Infrastructure

No background processes. No network calls. No accounts. curl | sh and you’re running. Works in Docker, CI/CD, air-gapped environments (direct binary download), Claude Code web. Anywhere you have a terminal.

Sync When You Want

Bidirectional sync with GitHub Issues and Linear. Use ticket-rs as your local layer and push upstream when you’re ready. Or don’t—it works fine standalone.

​
What “Alpha” Means

Let me be direct about what you’re signing up for:
  • The core is stable. I’ve been using ticket-rs daily for months across multiple projects. Create, list, triage, dependencies, graph analytics—these work.
  • The edges are rough. Error messages could be better. Some commands have sharp corners. The documentation has gaps.
  • Things will change. Command flags, output formats, config structure—I’ll try to minimize breakage, but this is alpha. Backwards compatibility is a goal, not a guarantee.
  • Your feedback shapes the roadmap. This is the phase where user input has the most leverage. Found a bug? Want a feature? Think something is designed wrong? I want to hear it.

​
Who This Is For

If any of these describe you, this is worth trying:
  • You use Claude Code, Cursor, or Windsurf and want your AI agent to have structured context about what to work on next
  • You’re tired of cloud-based issue trackers that add latency to every agent interaction
  • You want issue tracking that lives in your repo, branches with your code, and diffs like any other file
  • You’re building with multiple AI agents in parallel and need dependency-aware coordination
  • You just want a fast, local, no-nonsense issue tracker that respects your terminal workflow

​
Install

curl -fsSL https://ticket-rs.io/install.sh | sh

​
Request Access

The public alpha is invite-based. Send an email to get your invite code:

Request an Invite

Email alpha@ticket-rs.io with a brief note about your use case. We’ll send you an invite code and onboarding instructions.
Include whatever context is useful—what you’re building, what tools you’re using, what’s frustrating you about your current setup. Or just say “let me in.” Both work.

​
What’s Next

The alpha is about finding sharp edges before a wider release. Here’s what I’m focused on:
  • Stability — Fixing bugs reported by alpha users
  • Documentation — Filling gaps in the docs, adding more examples
  • Integrations — Improving Claude Code, Cursor, and Windsurf workflows
  • Performance — Already fast, always room to push further (see: our benchmarks)
If you’ve been following the project, now’s the time to jump in. If you’re just hearing about it, start with the intro post for the full story.

Quickstart

Install and create your first issue in 60 seconds

Why Graph Analytics?

Your backlog is a graph—here’s why that matters