Aiolum Browse stories
All stories
Open-source AI coding assistant and coding agent for VS Code, JetBrains and the terminal, later AI checks on pull requests · United States

Continue: Revenue, sale and how it was built

Small teamFundedExitB2BDeveloper tools

Continue (Open-source AI coding assistant and coding agent for VS Code, JetBrains and the terminal, later AI checks on pull requests, United States): Acquired by Cursor, June 2026. Evidence grade E: no revenue figure was checked. Team: 2 co-founders, Ty Dunn and Nate Sesti, in 2023; 10 people on the YC company page in September 2025 and 5 in May 2026, a month before the sale. Launched 26 July 2023; sold 35 months after launch.Added 8 November 2026

Outcome
Acquired by Cursor, June 2026
Evidence
E no revenue figure was checked
Launch
26 July 2023
Status
Sold, 35 months after launch
Team
2 co-founders, Ty Dunn and Nate Sesti, in 2023; 10 people on the YC company page in September 2025 and 5 in May 2026, a month before the sale
Outside funding
US$5.1M from Heavybit, Y Combinator and angel investors, the company stated on its YC page in May 2026
Main channel
Open source
No revenue figure

What is not verified

No sale price, revenue figure or count of paying customers was found. We read Continue's live home page, Internet Archive copies of its home, pricing and about pages, its YC company page (live and two archived copies), its GitHub repository and a DEV Community post. The New Stack's report of 22 June 2026, which that post cites, was not read: thenewstack.io disallows ClaudeBot in its robots.txt. No announcement by Cursor was found. The team sizes are figures that the company enters on its YC page, and "hundreds of thousands of users" is the company's own claim. A reader could look for a statement by Cursor or by the investor Heavybit, or for a later interview with the founders. This story is grade E: the business is real and its product, price and customers are described from public pages, but no revenue figure was checked. Aiolum shows it as an idea worth studying, not as proof that it makes money.

Continue was an AI coding assistant, a program inside a code editor that sends the developer's code and question to a large language model (LLM, a model trained on large amounts of text and code that writes text) and shows the answer or applies the edit. It shipped as an extension (an add-on that runs inside another program) for VS Code and JetBrains editors, and later as a command-line tool, under the Apache 2.0 open-source license, which lets anyone read, change and reuse the code. A developer could connect it to any model, from OpenAI and Anthropic to models running on the developer's own machine.

Ty Dunn and Nate Sesti started it in 2023 in Y Combinator's Summer 2023 batch; their launch post of 26 July 2023 called it "the open-source autopilot for software development". The extension stayed free, and in June 2025 the pricing page listed a Team plan at US$10 per developer a month. The YC page listed 10 people in September 2025 and 5 in May 2026, when the company stated that it had raised US$5.1 million. By 15 June 2026 its home page said "Continue has been acquired by Cursor".

No sale price, revenue figure or count of paying customers was found, so this story is grade E: the evidence is the company's own pages, its YC page, its code repository and one news post. The product was shut down: a DEV Community post of 22 June 2026, citing The New Stack, reported that recurring billing was turned off and that user data would be deleted after 15 July 2026, and the code repository is now read-only.

Continue: Acquired by Cursor, June 2026. Open-source AI coding assistant and coding agent for VS Code, JetBrains and the terminal, later AI checks on pull requests, United States, team of 2 to 10, evidence grade E.
The story in one card. Share it with the address of this page.
01

How much did Continue make, and what was it sold for?

Each row shows the evidence grade and the source numbers from the list at the end of this page. The grades are explained in How Aiolum verifies.

A two-founder open-source coding assistant from Y Combinator's Summer 2023 batch that sold team plans, raised US$5.1 million by its own account, and was acquired by Cursor in June 2026; no price, revenue or paying-customer count is public
FactValueGradeHow we knowSources
Outcome, June 2026acquired by Cursor; price not disclosedCContinue's home page, Internet Archive copy of 15 June 2026: "Continue has been acquired by Cursor." The copy of 14 June 2026 still sold the product. The YC company page now reads "Acquired by Cursor". The DEV Community post: "Terms of the deal were not disclosed, per the report." No announcement by Cursor itself was found.[1, 2, 3, 6, 10]
What happened to the producthosted service shut down; billing turned off; repository read-onlyCDEV Community post, 22 June 2026, citing The New Stack: "Recurring billing has been disabled, and the FAQ on the homepage sets July 15 as the data-deletion deadline." GitHub README, read 8 November 2026: "no longer actively maintained and is read-only for all users", after a "Final 2.0.0 Release".[9, 10]
Founders and startTy Dunn and Nate Sesti, 2023; Y Combinator Summer 2023CYC company page: year founded 2023, batch Summer 2023, two founders. Launch post: "We're Nate and Ty, co-founders of Continue." Their YC profiles say Ty Dunn was founding product manager at Rasa and Nate Sesti built mission control software at NASA's Jet Propulsion Laboratory.[6]
Launch26 July 2023, Launch YC postC"Continue: the easiest way to code with any LLM", an open-source extension for VS Code and JetBrains. The post said the company planned to make money from "a paid development data engine" for organizations.[6]
Team size10 people in September 2025; 5 in May 2026; 0 todayCTeam size field of the YC company page in Internet Archive copies of 17 September 2025 and 19 May 2026, and on the live page read 8 November 2026. The company enters these figures itself.[6, 7, 8]
FundingUS$5.1 million from Heavybit, Y Combinator and angel investorsCCompany text on the YC page, Internet Archive copy of 19 May 2026. The DEV Community post gives "roughly $5 million raised, per The New Stack". The about page of January 2026 showed Heavybit and Y Combinator under "Backed by".[8, 10, 11]
PricesTeam US$10 per developer a month in June 2025; US$20 per seat a month in June 2026CArchived pricing pages. A Models add-on cost US$20 per developer a month in 2025; in 2026 the Starter plan charged US$3 per million tokens.[4, 5]
Users"hundreds of thousands", company statementCYC page text, May 2026: "With hundreds of thousands of users, Continue is loved by developers worldwide". No count of paying customers was given. Not verified.[8]
GitHub repository36,400 stars and 5,600 forks, read 8 November 2026CGitHub shows "36.4k stars" and "5.6k forks". The DEV Community post gave about 34,300 stars and 4,800 forks at the time of the deal, per The New Stack. Apache 2.0 license, "© 2023-2026 Continue Dev, Inc."[9, 10]
Product before the saleAI checks on every pull request, written as markdown files in the repositoryCHome page of 14 June 2026: "Source-controlled AI checks on every pull request" that Continue runs "as native GitHub status checks with suggested fixes".[3]
Time from launch to the sale35 monthscalcCalculated: 26 July 2023 to 15 June 2026.[2, 6]

How to read this table: a grade C value is a statement by Continue on its own pages or on its YC company page, a count shown by GitHub, or a report in a DEV Community post. A "calc" value was computed on this page. No money amount for the sale or for revenue exists in the sources, and no statement by Cursor was found.

Continue prices before the sale, read from Internet Archive copies of hub.continue.dev/pricing (9 June 2025) and www.continue.dev/pricing (14 June 2026), grade C. The product no longer sells.
PlanPer month, billed yearly (US$)Per month, billed monthly (US$)Limit
Solo (June 2025)0open-source extensions; bring your own models or API keys
Team (June 2025)10 per developerprivate assistants managed for the team; allow and block lists; managed proxy for API keys
Models add-on (June 2025)20 per developera set of frontier models for a flat monthly fee
Enterprise (June 2025)customsingle sign-on with SAML or OIDC; on-premise proxy
Starter (June 2026)3 per million tokenspay as you go; create and run agents
Team (June 2026)20 per seatincludes US$10 in credits per seat; shared private agents; Gmail or GitHub sign-in
Company (June 2026)customcustom single sign-on; bring your own API keys; invoicing and SLA

The open-source extension was free throughout. In 2025 the company charged per developer for team management and sold model access as an add-on; by June 2026 it charged per seat with included credits and sold model use by the token. No yearly prices were published, so the yearly column is empty. After the sale, recurring billing was turned off, a DEV Community post reported.

02

When did Continue launch, and how did it grow?

From a 2023 launch as an open-source coding assistant to a sale to Cursor 35 months later, and the shutdown of the hosted product. Each entry carries its grade.

  1. 2021 to 2022CTy Dunn uses GPT-3 and Codex in research at Rasa; Nate Sesti writes code at NASA, where privacy rules keep him from using LLMs. The founders wrote that GitHub Copilot and ChatGPT changed how they built side projects in 2022. [6]
  2. 26 July 2023CLaunch YC post in Y Combinator's Summer 2023 batch: an open-source extension for VS Code and JetBrains that works with any LLM, including local models. [6]
  3. June 2025CThe pricing page lists a free Solo plan, a Team plan at US$10 per developer a month, a Models add-on at US$20 and custom Enterprise prices. [5]
  4. September 2025CThe YC page lists 10 people and the line "Build and run custom agents across your IDE, terminal, and CI". [7]
  5. May 2026CThe YC page lists 5 people, a new product (AI checks on pull requests) and US$5.1 million raised, as the company stated. [8]
  6. 15 June 2026CThe home page announces "Continue has been acquired by Cursor"; the copy of the day before still sold the product. [2, 3]
  7. 22 June 2026CA DEV Community post, citing The New Stack, reports undisclosed terms, billing turned off and a 15 July deadline to export data. The GitHub repository becomes read-only after a final 2.0.0 release. [9, 10]
03

Why did Continue work?

Four causes, in the order they mattered. Each one is a reusable lesson.

01

Open source that works with any model

The extension was free under the Apache 2.0 license and worked with OpenAI and Anthropic models, open-source models on a company's own cloud, and local models. A developer at a company that does not allow code to leave its network could still use it. The launch post asked readers to star the repository and download the extension, and GitHub counted 36,400 stars by November 2026.

02

Free extension, paid control for teams

Individuals paid nothing. Companies paid per developer for central management: private assistants shared across the team, allow and block lists for the parts developers could use, and a proxy that let members use the company's API keys without seeing them. Model access was a separate add-on, and later credits sold by the token.

03

From the editor to pull requests

In 2026 the company sold a narrower product: checks written as markdown files in the repository, each run by an AI agent on every pull request and reported as a GitHub status check. The YC page called it "Quality control for your software factory" in May 2026, a month before the sale.

How it was built

These points are the company's own statements on its pages, in its launch post and in its code repository, grade C. [3, 5, 6, 9]

  • Extensions for VS Code and JetBrains editors, and later a command-line tool; the final release recommended the command-line tool over the JetBrains plugin.
  • Model-agnostic from the start: OpenAI and Anthropic models, open-source models on the customer's own cloud, and local models through ggml, the launch post said.
  • Customization through slash commands, context sources such as GitHub issues, Jira and documentation pages, templated system messages, and tools such as running unit tests.
  • Development data saved by default to .continue/dev_data on the developer's machine, which the founders wanted companies to use to improve their models.
  • A hosted hub for teams with an authentication layer and a managed proxy for API keys, and for enterprises an on-premise proxy that kept code in the customer's own environment.
  • The final 2.0.0 release removed anonymous telemetry and authentication, so the code can run without the company's servers.

Tools named in the sources

Each one opens its page in the Tools tab, with every story that uses it.

04

Who tried this before Continue, and why did they fail?

Three companies in our database of failed startups sold developer tools that lived inside the editor or the terminal and failed, one of them after a sale to a large buyer. The values below are from that database and are not independently verified.

Died 2014 to 2024Burned US$21M

Kite DevTool

The promise

AI code completion inside the editor, years before GitHub Copilot.

Why it died

Its free product did not turn into paying users, and GitHub Copilot, built on OpenAI's Codex model, gave better suggestions with GitHub's reach.

Competition
Died 2020 to 2024Burned US$2.4M

Fig DevTool

The promise

Autocomplete and visual command builders for the terminal.

Why it died

Developers used it daily, but few paid for a terminal tool; AWS acquired it in 2024.

Unit Economics
Died 2012 to 2016Burned US$8M

Nitrous.io

The promise

A code editor in the cloud, so developers need no setup on their own machine.

Why it died

Amazon bought the competitor Cloud9 and offered it free or cheap to sell AWS computing; Nitrous could not compete on price.

Competition

The failed startups come from our database of 1,749 dead startups, retold here in our own words. Its entries are AI-assisted summaries of public sources, so these cards carry no evidence grade.

What changed

Kite built AI code completion before large language models were good enough and could not get developers to pay; Fig made a tool that developers used every day and few paid for; Nitrous lost when a large company gave a similar product away. Continue had the newer models that Kite lacked, and it kept the extension free while it charged companies for team control and model access.

The end resembles Fig's: a larger company bought the team and the product stopped. Continue's open-source license changed one part of that end. The code stays public under Apache 2.0, so users can keep running it or fork it, which means copying the code into a new project of their own, after the hosted service closed.

05

Can one person copy Continue now?

The product, no. The open-source route, yes.

Continue had two founders, a Y Combinator place and, by its own statement, US$5.1 million of outside money, and it competed with Cursor and GitHub Copilot. One person cannot copy that. The route is still open on a smaller scale: an open-source tool that works with any model, free for individuals, with a paid plan for the controls that companies need.

Where it is still open: Narrow open-source agents for one job in software development: checks on pull requests for one framework, reviews of database migrations, or test writing for one language.

  1. 1Publish a narrow AI tool for developers as open source, and let users bring their own model or API key.
  2. 2Make local and self-hosted models work, for companies that cannot send code to an outside service.
  3. 3Charge teams for central management: shared configurations, allow lists, and API keys that members use but cannot see.
  4. 4Sell model access as an optional add-on, not as the core price.

What could go wrong for Continue?

The risks are the mirror image of the causes above.

What is not verified

No sale price, revenue figure or count of paying customers was found. We read Continue's live home page, Internet Archive copies of its home, pricing and about pages, its YC company page (live and two archived copies), its GitHub repository and a DEV Community post. The New Stack's report of 22 June 2026, which that post cites, was not read: thenewstack.io disallows ClaudeBot in its robots.txt. No announcement by Cursor was found. The team sizes are figures that the company enters on its YC page, and "hundreds of thousands of users" is the company's own claim. A reader could look for a statement by Cursor or by the investor Heavybit, or for a later interview with the founders.

The product was shut down after the sale

The DEV Community post reported on 22 June 2026 that recurring billing was disabled and that data would be deleted after 15 July 2026. The GitHub repository is read-only, and the home page now says only that "Continue has joined Cursor". Users can still run the Apache 2.0 code themselves, but nobody maintains it.

Dependence on model providers

The extension had no model of its own: every answer came from a model that the user or the company chose. The founders wrote in July 2023 that "OpenAI and Anthropic perform best today", and the paid plans resold access to frontier models (a US$20 Models add-on in 2025, credits and a price per million tokens in 2026). Support for local and self-hosted models reduced that dependence for users, not for the company's paid model access.

Competition

In the DEV Community post's words, Continue was "the headline open-source alternative to GitHub Copilot", and it competed with the AI editor of its buyer, Cursor; on this site Firetiger is another small developer-tools team that Cursor bought in 2026 and whose product was then shut down.

Sources

The grade next to each source is the best grade that the source can support. "Read in full" means that the text of the page was downloaded and the numbers were checked in it.

  1. C Continue home page, read 8 November 2026: Continue has joined Cursor
    Read in full. The company's notice after the sale; the FAQ answers load by script and could not be read. continue.dev has no robots.txt (HTTP 404).
  2. C Continue home page, Internet Archive copy of 15 June 2026
    Read in full. The first archived copy with the text "Continue has been acquired by Cursor". Source for the date of the announcement.
  3. C Continue home page, Internet Archive copy of 14 June 2026
    Read in full. The last archived copy that still sold the product. Source for the AI checks on pull requests.
  4. C Continue pricing page, Internet Archive copy of 14 June 2026
    Read in full. Source for the Starter, Team and Company plans of 2026.
  5. C Continue Hub pricing page, Internet Archive copy of 9 June 2025
    Read in full. Source for the Solo, Team, Models add-on and Enterprise prices of 2025 and the features of the paid plans.
  6. C Y Combinator company page: Continue, with the Launch YC post of 26 July 2023
    Read in full on 8 November 2026 (ycombinator.com allows /companies/<slug> in robots.txt). Source for the founders, their background, the batch, the year founded, the status "Acquired by Cursor" and the launch post.
  7. C Y Combinator company page: Continue, Internet Archive copy of 17 September 2025
    Read the company data. Source for the team size of 10 and the product line of 2025.
  8. C Y Combinator company page: Continue, Internet Archive copy of 19 May 2026
    Read the company data. Source for the team size of 5, the US$5.1 million of funding, the investors and the users claim, all as the company stated them.
  9. C GitHub: continuedev/continue, read 8 November 2026
    Read the repository page and README in full. Source for the read-only notice, the final 2.0.0 release, the license and the star and fork counts.
  10. C DEV Community, 22 June 2026: Cursor acquires Continue and gives its users a July 15 export deadline
    Read in full. A post by the user leobaniak that summarises The New Stack's report of 22 June 2026, which we could not read. Source for the undisclosed terms, the billing stop, the export deadline and the earlier star count.
  11. C Continue about page, Internet Archive copy of 28 January 2026
    Read in full. Source for the investors shown under "Backed by" and the open engineering jobs.
  12. C Database of failed startups, local export
    Local export. AI-written summaries, not independently verified. Source for the failed predecessors.

Run this company? Send corrections or a verified figure to aiolum@livyden.com

Back to all stories