Skip to content
Issue trackingWeb + Desktop + iOS + Android

How much does it cost to build an app like Linear?

Estimated US development cost, the features and surfaces involved, the team and timeline it takes, the infrastructure it needs at scale, and what it costs to run once it is live.

An issue tracker for software teams built around responsiveness: issues, cycles, projects and roadmaps, with a keyboard-driven interface that updates instantly. It targets engineering teams specifically rather than general work management.

What this build involves

Issue tracking
Features listed
31
Sides served
3
Industry
Technology & SaaS
Sensitivity
3/5

The calculator returns

Cost rangeEngineering hoursTimelineTeam compositionRunning costs
Price a build like this

It is not one app — it is 3

The most common reason a budget for something like this comes in low is counting one application when the product needs several, plus the shared platform underneath that nobody sees.

Applications people use — 3

  1. Team client

    Web · Desktop · iOS · Android

    Engineers and product managers

    Issues, cycles, projects, roadmap, search — local-first and keyboard-driven.

  2. Workspace administration

    Web

    Team admins

    Teams, workflows, permissions, SSO and integrations.

  3. Developer integrations

    Web

    Engineering toolchains

    Source control, chat and CI integrations plus a public API. Table stakes for this audience.

Shared platform underneath — 8

  • Backend & API

    The shared data model, business rules and the API every side reads and writes through. Built once, and the single largest line in almost every estimate.

  • Identity & permissions

    Sign-in, sessions, second factors and a role model enforced on the server. Multi-sided products need one identity system that understands several kinds of user.

  • Payments & money movement

    Charging, refunding, paying out, reconciling and surviving audit. Never just an SDK call — the ledger and the failure paths are the work.

  • Notification system

    Templating, preferences, delivery across push, email and SMS, retries, and the suppression rules that stop a product becoming spam.

  • AI services & governance

    Model access, retrieval over your own content, evaluation and guardrails. The governance half is the part that gets cut and then rebuilt after an incident.

  • Admin & operations console

    Where your own staff fix what customers cannot: account issues, refunds, overrides, escalations. Consistently underbudgeted, and consistently the reason support costs balloon.

  • Analytics & reporting

    Event instrumentation, a warehouse and the dashboards the business actually runs on. Retrofitting instrumentation costs several times what building it in does.

  • Infrastructure & delivery

    Environments, pipelines, secrets, monitoring, alerting and on-call. The work that makes everything above deployable more than once a month.

What has to be built

Split by the phase each capability realistically lands in. The MVP column is priced as its own configuration above, so the split is a real costing decision rather than a diagram.

MVP features

11

The smallest set that is still this product.

  • Email & password sign-in
  • Google & Apple sign-in
  • User profiles
  • Organisations & team accounts
  • Roles & permissions
  • Search, filters & sorting
  • Comments & reactions
  • Documents & file handling
  • Transactional email
  • Notification centre
  • Push notifications

Advanced features

11

What a credible competitor is expected to have.

  • Offline-first operation
  • Dedicated search engine
  • Public API & webhooks
  • Dashboards & reporting
  • Subscriptions & recurring billing
  • Card payments
  • Guided onboarding
  • Accessibility (WCAG 2.2 AA)
  • Product analytics instrumentation
  • Text generation & summarisation
  • Feature flags & remote config

Enterprise features

9

Scale, governance and the work nobody demos.

  • Enterprise SSO (SAML / OIDC)
  • Audit logging
  • Admin console
  • Self-service report builder
  • Scheduled exports & feeds
  • Approval workflows
  • Retention & deletion policy
  • Support tooling
  • AI evaluation & guardrails

The same features, by who uses them

Customer experience

What the people you are building for actually touch.

  • Email & password sign-in
  • Google & Apple sign-in
  • User profiles
  • Organisations & team accounts
  • Roles & permissions
  • Comments & reactions
  • Documents & file handling
  • Subscriptions & recurring billing
  • Card payments
  • Guided onboarding
  • Enterprise SSO (SAML / OIDC)
  • Audit logging
  • Retention & deletion policy

Communication

How the product reaches people and how they reach each other.

  • Transactional email
  • Notification centre
  • Push notifications

Field & location

Everything that happens away from a desk.

  • Offline-first operation

Operations & staff

The consoles your own team lives in. Rarely demoed, always needed.

  • Admin console
  • Approval workflows
  • Support tooling

Data & intelligence

Reporting, analysis and anything model-driven.

  • Search, filters & sorting
  • Dedicated search engine
  • Dashboards & reporting
  • Product analytics instrumentation
  • Text generation & summarisation
  • Self-service report builder
  • Scheduled exports & feeds
  • AI evaluation & guardrails

Platform

The cross-cutting obligations — access, languages, configuration.

  • Public API & webhooks
  • Accessibility (WCAG 2.2 AA)
  • Feature flags & remote config

Technology a build like this would use

Derived from the platforms and capabilities above.

These are typical choices for building a product of this shape today. They are derived from the platforms and capabilities described above — not a claim about what Linear actually runs on. We do not publish other companies’ internal technology, and you should be sceptical of anyone who does.

Mobile

  • React Native or Flutter (one codebase)
  • Swift / SwiftUI (native iOS)
  • Kotlin / Jetpack Compose (native Android)

Two native codebases buy platform fidelity and cost roughly 66–70% more on the client than one shared codebase. Cross-platform is the default unless a specific capability forces native.

Web

  • TypeScript
  • React with Next.js
  • Tailwind CSS or a component library

Server rendering matters here if the pages need to be indexed; if the web surface is an authenticated console only, it does not.

Desktop

  • Electron or Tauri (shared with web)
  • Native Swift / WinUI where OS integration matters

A shared shell is cheaper; native is worth it only for deep OS integration, offline scale or performance-critical rendering.

Backend

  • Node.js / TypeScript
  • Python (Django or FastAPI)
  • Go or Java for throughput-critical services

Language choice matters far less than team familiarity. A modular monolith is the right default until traffic or team size forces separation.

Data

  • PostgreSQL (primary transactional store)
  • Redis (cache, sessions, queues)
  • Elasticsearch or Algolia (search)

One relational database plus a cache covers more products than teams expect. Add a specialist store when a real query pattern demands it, not in anticipation.

Cloud & delivery

  • AWS, Google Cloud or Azure
  • Containers on a managed orchestrator
  • Terraform or equivalent for infrastructure as code
  • GitHub Actions or similar for CI/CD

The architecture tier this product needs is driven by traffic, not preference — see the scale section below.

Payments

  • Stripe, Adyen or Braintree
  • Apple Pay and Google Pay via the platform SDKs
  • Reconciliation against processor settlement reports

Using a processor keeps card data out of your systems and shrinks PCI scope dramatically. It does not remove the need for your own reconciliation.

Messaging & notifications

  • APNs and FCM for push, usually via a delivery service
  • Twilio for SMS and voice
  • SES, SendGrid or Resend for email

Deliverability is an operational discipline: warm-up, domain authentication, bounce handling and suppression lists. It is not solved by picking a vendor.

AI

  • A hosted model provider (Anthropic, OpenAI) or Bedrock
  • Prompt and context management
  • Evaluation harness and output guardrails

Token cost scales with usage, so unit economics need modelling before launch. The evaluation and guardrail layer is what separates a demo from a product.

Observability

  • Sentry for errors
  • Datadog, Grafana or an equivalent for metrics and traces
  • Structured logging with retention matched to your compliance regime

Instrumentation is cheapest when added during the build. Retrofitting it after the first production incident costs several times more.

How an app like Linear works

The defining decision is that the client holds a synchronised local copy of the data it needs, so interactions complete against local state and reconcile with the server in the background. That local-first architecture is what produces the perceived speed, and it is also the single largest source of engineering complexity — offline mutation queues, conflict resolution, schema migration on client caches and partial sync scoped by permission all follow from it.

In costing terms that shape matters more than the feature count. A workflow / operations in technology & saas inherits obligations before anyone designs a screen — this sector rates 3 out of 5 for regulatory and procurement difficulty on this site, and that rating is what drives the security posture, the audit work and the integration surface any estimate has to carry.

MVP versus the full product

A first version of this is a materially smaller build than the mature product, and the calculator will show you by how much. It gets there by shipping fewer features, on fewer surfaces, at a launch-sized audience rather than the traffic the mature product carries.

What it does not cut is compliance. A regulated product is regulated from its first user, so the primary regime stays in the MVP even though almost everything else is deferred. Teams that defer it discover that retrofitting audit logging, access control and data retention costs several times what building them in would have.

Monetisation

How products of this shape make money

  • Per-seat subscription with a free tier
  • Business and enterprise tiers
  • Usage-based add-ons

Generic to the category, not a description of Linear’s commercial arrangements.

What these numbers are, and are not

This page carries no figures deliberately. What it sets out is the shape of the build — the sides, the tiers, the stack, the compliance — because that is what an estimate is derived from and what you can check. The calculator turns your own version of that shape into a planning estimate with a stated confidence band; use it to decide the order of magnitude, then spend two to four weeks on a technical specification and get a real quote against that document.

Nothing here is a statement about Linear as a company. We do not know and do not publish what any business spent building its product, what it earns, how many people it employs, or what technology it runs on. What we describe is the product shape any user can observe — the surfaces it presents, the roles it serves, the capabilities it evidently has — and what building that shape would cost in the United States today.

Building an app like Linear, answered

How much does it cost to build an app like Linear?

There is no one figure, because "an app like Linear" covers three very different builds: a first version with only the essential features, a complete and credible competitor, and a rebuild of everything the mature product does at the traffic it carries. Those are several-fold apart. What this page gives you is the shape of each — the sides, the feature tiers, the stack and the compliance — and the calculator turns whichever one you actually mean into a cost range, hours and a timeline.

Why is an app like Linear more expensive than a typical app?

Because it is not one app. It is 3 separate applications — team client, workspace administration, developer integrations — sharing one backend, each with its own design, release cycle and test matrix. Most quotes that come in low have counted one of them. Local-first sync is the architecture: Holding a synchronised client-side dataset buys instant interaction and costs you offline mutation queues, conflict resolution, cache schema migrations and permission-scoped partial sync. It is a deliberate, expensive trade.

Could I build a cheaper version first?

Yes, and you should. A first version ships the essential feature tier rather than all three, on fewer surfaces, at a launch-sized audience — materially less than the full product, and the calculator will show you by how much. What it does not cut is compliance: technology & saas obligations apply from the first user, so those stay in whatever else is deferred.

How long would it take to build?

It depends on the same three things the cost does — which tier of the product you mean, how many surfaces you ship, and how settled the scope is. The calculator returns a timeline alongside the cost, derived the same way: hours divided across a realistic team shape, never a target date worked backwards from.

What does it cost to run once it is live?

Cloud infrastructure, third-party services and annual maintenance, and the calculator reports all three separately from the build. They are kept out of the build figure deliberately: they are operating expenditure rather than capital, and adding the two together produces a number that means nothing. Maintenance in particular is not optional — an app that receives none stops working within about a year as OS releases and SDK deprecations accumulate.

Are these real figures for Linear?

This page carries no figures at all, and nobody outside the company has real ones. What it describes is the product SHAPE, observed from what any user can see — the sides, the feature tiers, the stack, the compliance. Nothing here describes what Linear actually spent, earns, employs or runs on. The calculator prices building something of that shape today, for the United States market, at our own blended delivery rate.

What does multi-tenancy actually add?

Typically $30,000–$70,000 over the equivalent single-tenant product, and considerably more if you retrofit it. The cost is not a tenant column on your tables — it is that every query, cache key, background job, export and test must be tenant-aware, and that a single missed filter is a data breach rather than a bug. That raises your security and QA bar permanently. Design for it from the start even if you launch with one customer.

When should we build SSO and SOC 2?

When a deal depends on it, not before — but design so you can. SAML SSO, SCIM provisioning, audit logs and role granularity total $80,000–$180,000 of engineering, and SOC 2 Type II adds $20,000–$45,000 in auditor fees on top of the evidence work. Building it speculatively is premature. Building your auth layer and data model so it can be added without a rewrite costs almost nothing and saves a painful quarter later.

Price your own build, not Linear's

Every control on one page, a live spec sheet beside it, and nothing behind a form.