FeaturedLinear
Screenshots
1 / 2The Story
Linear is a project and issue tracking tool for software teams. It replaces the spreadsheet-and-ticket sprawl of older trackers with an opinionated workflow: issues move through a fixed set of states, cycles bound a team's work to a timebox, and projects roll many issues into a single outcome the team can see.
The product is built around speed. Every action has a keyboard shortcut, the interface renders as a native-feeling desktop app, and the command menu reaches any record without navigating a hierarchy. Teams that adopt it typically keep a written convention for how issues are titled and how cycles are scoped, because the tool does not impose a methodology beyond the state machine.
Linear's roadmap features have expanded beyond engineering: project documents, customer requests, and initiative rollups now sit alongside the issue list. The company ships on a weekly cadence and publishes a public changelog, which is unusual for a tool of this size and is the main reason this entry stays verifiable.
Overview
Linear's core bet is that a software team's tracker should feel instant and require almost no administration.
The unit of work is the issue. Issues belong to a team, move through a fixed set of states (backlog, todo, in progress, done, canceled), and can be grouped into cycles - timeboxed sprints that reset on a schedule the team chooses.
Above the issue sits the project: a container for a defined outcome, with its own lead, target date, and progress rollup. Projects can be grouped into initiatives, which is how larger organizations map a quarter of work to a strategy.
Linear does not ship a configurable workflow builder. Teams that need custom state machines, per-department approval chains, or a service-desk intake form generally keep a second tool for that and use Linear for engineering execution.
What you get free, and what changes when you pay
| Feature | Free | Basic | Business | Enterprise |
|---|---|---|---|---|
| Members | Unlimited | Unlimited | Unlimited | Unlimited |
| File upload | 10MB | Unlimited | Unlimited | Unlimited |
| Issues | 250 issues | Unlimited | Unlimited | Unlimited |
| Teams | 2 teams | 5 teams | Unlimited | Unlimited |
| Releases | — | — | 15 pipelines | Unlimited |
| Microsoft Teams integration | — | — | — | Multiple tenants |
| Sub-teams | — | — | 1 level | 5 levels |
| SSO | Google + SAML |
Read from the vendor's pricing page · checked 2026-09-21 · Prices change; confirm before you buy.
Key Features
- Keyboard-first navigation
Almost every surface is reachable from the command menu, and the shortcut set is consistent across web, desktop, and mobile. Teams that learn it stop reaching for the mouse.
- Cycles that bound the work
A cycle is a repeating timebox with a scope the team sets at the start. Unfinished issues carry over automatically, so the backlog does not silently grow.
- Projects and initiatives
Projects collect issues into a single outcome with a lead and a target date. Initiatives group projects into a strategic theme.
- Public changelog
The company publishes releases on a dated changelog, so a reader can check what shipped and when without an account.
Where Linear is a strong choice, and where it is not
Choose Linear if you run a software team that already agrees on a workflow and wants the tool to stay out of the way. The speed advantage compounds with team size up to a point, and the cycle model works well for teams shipping on a regular cadence.
Look elsewhere if you need a heavily configurable workflow engine, a customer-facing service desk with SLAs, or a tracker that a non-technical department will administer. Linear's opinionated design is the feature and the limitation at the same time.
Getting started
A solo developer can be tracking issues in minutes; the cost is deciding on a workflow first.
- ~5 minTime to first issue
Create a workspace, invite nobody, and file an issue. No setup wizard or workflow builder stands in the way.
- FreeCost to start
The free tier covers unlimited members with limited issue history. Paid seats add full history and admin controls.
- NothingPrerequisites
A browser or the desktop app. No credit card and no self-hosting step.
Known limitations
These are the constraints we could confirm from the public documentation, not guesses.
- Paid seats are required for full history. The free tier limits how far back issues remain visible, which matters if your team treats the tracker as an archive.
- No configurable workflow engine. Issue states are fixed. Teams needing custom state machines or approval chains keep a second tool.
- Not a customer-facing service desk. There are no SLAs, no intake forms, and no external requester portal.
- Self-hosting is not offered. It is a hosted product, so the data lives with the vendor.
Pick Linear if your team already agrees on how it works
Linear is the strongest choice when speed matters more than configurability, and the wrong one when a non-engineering department has to administer the tool.
The product's bet is that a tracker should require almost no administration. That is a real advantage for a software team with a settled process, and a real limitation for anyone who needs the tracker to model a bespoke workflow.
If you need custom states, SLA-driven intake, or a tool a non-technical team will configure, look at a configurable platform instead. If you want the tool to disappear behind your process, this is the one to pick.
FAQ
What is Linear?
Linear is an issue tracker and project planning tool for software teams, built around a fast interface and a fixed issue workflow.
Is Linear free?
Linear lists a free tier for small teams alongside per-seat paid plans. Check the pricing page for the current limits and seat price.
What is a cycle in Linear?
A cycle is a repeating timebox, usually one or two weeks, that scopes a team's work. Unfinished issues carry into the next cycle automatically.
Does Linear have a public changelog?
Yes. Linear publishes dated releases on a public changelog page that does not require an account.
What stack is Linear built with?
CompassPad records Linear as a React and TypeScript application with a Node.js service layer and PostgreSQL storage, based on public engineering writing and job listings.
What we checked
- LIVESite and primary link
The marketing site resolved and the primary product link reached the application sign-in page.
- PRICINGPricing page
The pricing page resolved and lists a free tier alongside per-seat paid plans.
- DOCSDocumentation
Product documentation is public and covers issues, cycles, projects, and initiatives.
- FRESHNESSChangelog
A dated public changelog is published and reachable without an account.
Discussion
No comments yet. Be the first.
Join the conversation. Sign up to comment.
Sign up free