← sources

What it actually costs to run a Linear-style issue tracker for a small team (I built one to find out)

source: reddit (reddit:SaaS)published 2026-09-25 05:36ingested 2026-09-26 02:36

retained text

Disclosure: I built the tool mentioned at the end.

Our five-person team was paying per seat for an issue tracker, and I wanted to know what the same thing costs to run when you strip out sales and marketing. So I built one with the same shape: issues, projects, cycles, triage, saved views, documents, inbox, board and timeline, GitHub PR linking, Slack notifications, keyboard-first.

Numbers so far, hosting a few workspaces on one small server: about $20 a month for compute and database, email delivery on a free tier, sending under a cent per login code. At a thousand workspaces the same setup is maybe $300 to $800 a month. Per-seat pricing at $8 to $14 would be charging that thousand-workspace base over a million a year for the same infrastructure.

What I got wrong: the software was the easy part. Deliverability rules, security headers, abuse controls and support are where the real work went, and none of it scales with seats. Seat pricing is a sales model, not a cost model.

So I've made it free with no seat limits and no tiers; if it ever charges, it'll be a flat fee per workspace. It's early (no CSV import yet, no mobile). It's called Nonlinear, at usenonlinear dot com.

Curious what others here pay per seat for trackers and whether flat per-workspace pricing would change your choice.

document fetched 2026-09-26 00:29 · canonical https://reddit.com/r/SaaS/comments/1wpo4m9/what_it_actually_costs_to_run_a_linearstyle_issue