Source: https://www.thetechstack.com/teardowns/linear Author: Kyle Brierley Author profile: https://www.thetechstack.com/authors/kyle-brierley Editor: Not specified Editor profile: Not specified Publisher: TheTechStack (https://www.thetechstack.com) Published: 2026-07-10 Updated: Not specified Suggested citation: [Kyle Brierley](https://www.thetechstack.com/authors/kyle-brierley). [What Linear actually runs](https://www.thetechstack.com/teardowns/linear). TheTechStack. Retain the source qualifications. Cite the original article and link the credited author profile where available. An editor is not necessarily the author. **Research record**LinearPublished 2026-07-10 # What Linear actually runs The most opinionated product in project management runs a deliberately boring stack — TypeScript, Postgres, GCP — except for the one thing they built before almost anything else: the sync engine. By [Kyle Brierley](https://www.thetechstack.com/authors/kyle-brierley) Record Company Linear Published 2026-07-10 Structured record [View stack record ↗](https://www.thetechstack.com/stacks/linear) Topics devtools · typescript · sync-engine · gcp · Public-source research with documented limits. Product behavior and terms can change. Linear’s stack has a reputation for being exotic. It isn’t — and the company says so itself. CTO Tuomas Artman, [describing the architecture](https://newsletter.pragmaticengineer.com/p/linear): “We chose a ‘very normal’ tech stack, based on TypeScript. We have React on the frontend and Node on the backend… We use Postgres as a database, and Redis for queuing… and GraphQL as our API layer. And all of it runs on GCP with Kubernetes.” The exotic part is a single deliberate exception: a homegrown real-time sync engine, built in the company’s earliest days, that everything else is arranged around. Sourcing note: our baseline is Artman’s 2022 deep-dive with [The Pragmatic Engineer](https://newsletter.pragmaticengineer.com/p/linear); current state comes from the “Our tech” section [Linear publishes on its own careers page](https://linear.app/careers/cd5ae036-0223-427a-b038-ba16ef9dcb32) (accessed July 2026). Where the two lists disagree, that’s a migration signal — labeled inferred, not confirmed. Full record in [the stack database](https://www.thetechstack.com/stacks/linear). ## Stack at a glance | Category | Tool | Since | Confidence | | --- | --- | --- | --- | | language | TypeScript | 2019 | confirmed | | frontend | React, MobX, styled-components | 2019 | confirmed | | backend | Node.js, GraphQL API | 2019 | confirmed | | database | PostgreSQL | 2019 | confirmed | | queue | Redis; Temporal (agentic workloads) | 2019; ~2023–24 | confirmed | | database | MongoDB (caching) | — | **previous** — inferred | | hosting | GCP + Kubernetes | 2019 | confirmed | | ci-cd | GitHub Actions | — | inferred | | internal-tools | GitHub, Slack, Notion | — | confirmed | Context: ~30 employees at the 2022 interview (15 engineers) serving what the careers page now describes as [25,000+ companies including OpenAI, Coinbase, and Ramp](https://linear.app/careers/cd5ae036-0223-427a-b038-ba16ef9dcb32) (confirmed). Third-party aggregators report ~178 employees ([Latka](https://getlatka.com/companies/linear.app)) and an $82M Series C at a $1.25B valuation in June 2025 ([Sacra](https://sacra.com/c/linear/)) — both reported, not company-confirmed. ## The one exotic thing, built first Most startups bolt real-time sync on later. Linear inverted that. Artman: “In the very early days of Linear, we built a complex engine which took care of synchronizing the frontend and the backend, with offline support… Because we did this so early on, it meant that as we grew, engineers could focus on building features… as they would not have to think about networking, error management, race conditions or data synchronization between clients.” ([Pragmatic Engineer](https://newsletter.pragmaticengineer.com/p/linear), confirmed) The mechanics, per [third-party reverse-engineering](https://marknotfound.com/posts/reverse-engineering-linears-sync-magic/) of the client (inferred, 2022-vintage — details may have evolved): the app keeps a near-full local copy of workspace data in IndexedDB, bootstraps via a sync endpoint, then streams live changes over WebSockets as ordered sync actions, replaying anything missed after a reconnect. Postgres sits behind it as the system of record. Notably, [analysis of the engine](https://github.com/wzhudev/reverse-linear-sync-engine) suggests Linear’s collaboration model relies on a centralized server establishing canonical ordering rather than the CRDT approach favored by much of the local-first movement (inferred). MobX provides the reactive object graph on the client — the piece that makes a locally-synced database feel like an instant UI. Artman’s own 2023 talk, [“Scaling the Linear Sync Engine”](https://linear.app/now/scaling-the-linear-sync-engine), covers how it held up (confirmed it exists; the details live in the video). ## Infrastructure decisions made like migrations are expensive Two founding-era choices show the same philosophy: pay upfront to never migrate. Kubernetes arrived when the entire product team was two engineers and a designer — “sounds like bad prioritization,” Artman concedes, but “sooner or later, we’d need to move over to Kubernetes, so we might as well bite the bullet now… it means we won’t have to migrate” ([confirmed](https://newsletter.pragmaticengineer.com/p/linear)). It’s the mirror image of [Cursor’s Yugabyte retreat](https://www.thetechstack.com/teardowns/cursor) — where Cursor bought scale-readiness it didn’t need and walked it back, Linear pre-paid for infrastructure it grew into. The cloud choice was less philosophical. On GCP versus AWS: “in my view GCP is moving ahead on cost-for-performance. In the end, we went with GCP because the user interface is much better than AWS” (confirmed). Sometimes the deciding factor for a billion-dollar company’s cloud is that the console is nicer. ## What changed between 2022 and now Comparing Artman’s 2022 list against Linear’s current careers page yields two deltas, both unannounced: **MongoDB is gone.** “In place for caching scenarios” in 2022; absent from the company’s own current stack list (inferred — could be careers-page shorthand rather than a true retirement; we’ve [asked for verification](https://www.thetechstack.com/about)). **Temporal arrived**, appearing twice in the current list — once in the core backend line-up and once powering an “agentic workload system… at production scale” ([confirmed](https://linear.app/careers/cd5ae036-0223-427a-b038-ba16ef9dcb32)). The timing lines up with Linear’s 2025 push into AI agents, and their public GitHub org now includes Cursor and Claude agent integrations (confirmed). Durable workflow orchestration showing up exactly when a fast-moving product adds long-running AI tasks is the most 2026 stack move there is. ## What we couldn’t confirm In keeping with our method: we found no reliable public evidence for Linear’s auth provider, billing stack, or observability tooling, so they’re not in the record — rather than guessed at. If you work at Linear, [the record is one pull request away](https://github.com/KyleBrierley/thetechstack-data/blob/main/records/linear.json) from a ✓ verified badge. ## What we’d watch Whether the sync engine’s centralized-ordering model holds as Linear pushes deeper into multiplayer AI-agent territory, what actually replaced MongoDB’s caching role, and whether “very normal” survives the agentic era — Temporal is the first crack in the boring-on-purpose doctrine, and we mean that as a compliment. * * * _Sources: [The Pragmatic Engineer deep-dive with CTO Tuomas Artman](https://newsletter.pragmaticengineer.com/p/linear) (baseline), [Linear’s careers page “Our tech”](https://linear.app/careers/cd5ae036-0223-427a-b038-ba16ef9dcb32) (current state), [marknotfound](https://marknotfound.com/posts/reverse-engineering-linears-sync-magic/), [wzhudev](https://github.com/wzhudev/reverse-linear-sync-engine), [Sacra](https://sacra.com/c/linear/). Research assisted by AI agents, verified and edited by a human. Confidence labels: confirmed / inferred / reported. Spot an error? We correct publicly._ [Kyle Brierley](https://www.thetechstack.com/authors/kyle-brierley) · Founder, TheTechStack Research and drafting use AI assistance. Kyle is responsible for editorial direction and corrections. Source-backed observations, recommendations, and proposed tests are identified separately. [About Kyle and more of his research →](https://www.thetechstack.com/authors/kyle-brierley) ## Put the research to work Use the documented patterns as questions for your own team. Your systems, permissions, and acceptance criteria still need to be checked. - [Compare build, buy, and extend](https://www.thetechstack.com/guides/build-buy-or-extend)Work through capability fit, integration effort, cost, and ownership. - [Find a workflow like yours](https://www.thetechstack.com/use-cases)Explore knowledge search, support drafting, and sales RFP responses. - [Create a pilot review](https://www.thetechstack.com/workbench)Leave with a shareable brief and a list of open decisions. - [Evaluate a pilot](https://www.thetechstack.com/guides/evaluate-an-ai-pilot)Compare actual results with the current process, including review and rework. ## Follow the research Get new research briefs and company teardowns by email, in your feed reader, or on X. [Subscribe by email →](https://buttondown.com/thetechstack)[Subscribe via RSS →](https://www.thetechstack.com/rss.xml)[Follow on X →](https://x.com/thetechstackHQ) Email signup is hosted by Buttondown. RSS and X are available without an email subscription.