Cognition AI: the company behind Devin and the former Windsurf

The short answer

Cognition is the company behind Devin. Devin began as a managed autonomous software engineer: assign a task, let the service work in its own environment, and review the result later. Cognition subsequently acquired Windsurf, the company and editor descended from Codeium, then folded the desktop editor into the Devin product line under the name Devin Desktop.

The distinction between company and product matters because “Cognition AI” searches often land on outdated stories about the original Devin demo or the attempted Windsurf deal cycle. The current buyer does not encounter one agent in isolation. The buyer encounters an account, plan quota, cloud sessions, a desktop editor, a CLI, repository knowledge, review, integrations, and enterprise controls.

The timeline without the deal-cycle noise

The sequence matters because three different events are often compressed into “Cognition bought Windsurf.” The company rebrand from Codeium to Windsurf happened before Cognition owned it. The acquisition happened in July 2025. The consolidation under Devin happened in 2026.

Why Cognition bought an editor

The original Devin product began away from the developer's active editor. Its strength was asynchronous delegation in a managed environment: work arrives from a task system or chat integration, the agent operates, and a pull request returns. Windsurf began from the opposite end of the day, where the developer reads code, accepts completions, asks for an edit, and watches an agent in the current workspace.

Putting them together gives Cognition surfaces for both correction latencies. Short edits and code reading stay local in Desktop. Longer or independent tasks can move to cloud agents. A CLI covers developers who do not want the editor. DeepWiki supplies a codebase knowledge layer. Review provides a post-implementation surface. The acquisition therefore filled a product gap more directly than it added a new model.

The risks are the mirror image of the logic. An editor and a cloud engineer have different expectations for latency, trust, pricing, extensions, and reliability. Unifying the brand does not automatically unify the architecture. A desktop user may want predictable completions and no cloud complexity. An enterprise cloud customer may not care which editor developers use. Cognition has to make the product line coherent without forcing every customer to buy the same workflow.

What the 2026 consolidation changed

The June rename was not a shutdown or a request to migrate projects into a different editor. Cognition described Devin Desktop as the new name for Windsurf and delivered it as an over-the-air update. Existing plans, settings, extensions, and keybindings carried over. The desktop software remained, while its brand, homepage, product story, agent, and billing context changed.

The command center is the substantive product change behind the name. It organizes agents by running, waiting for review, and done states. Spaces give agents shared context and git-worktree structure. Agent Client Protocol support allows third-party agents inside the editor. The direction is not merely a relabeled VS Code fork; it is an editor acting as the local control surface for a fleet.

Billing also became part of the consolidation. Current Devin plans cover the desktop and cloud product line, with Free at $0, Pro at $20, Max at $200, Teams with an $80 floor and $40 full seats, and custom Enterprise terms. Existing Windsurf Pro and Teams subscribers documented at $15 and $30 per developer seat retain grandfathered prices.

The current Cognition product map

Cognition is easier to understand as a stack than a list of names. The layers share a brand and account but solve distinct parts of software work. A buyer should mark which layers are requirements, conveniences, or unused overlap.

The model layer is deliberately less central to this map. Cognition can package its own SWE models and frontier models from other vendors. Model quality changes quickly. The product advantage Cognition is attempting to build is continuity across intake, environment, knowledge, execution, and review. That workflow remains valuable even when the best model changes.

This also explains why comparing Cognition with one terminal agent is incomplete. Claude Code or Codex can replace the implementation loop for many tasks. They do not automatically replace managed environments, DeepWiki, ticket integrations, Review, or enterprise support. The inverse is true too: buying Cognition's suite is unnecessary when the real requirement is one agent on a local repository.

Pricing and business model

Cognition's self-serve ladder now resembles other AI development subscriptions at the entry and top individual tiers: Free, $20 Pro, and $200 Max. Teams uses an $80 monthly minimum, $40 full seats, and free flex seats that draw from shared credits. Enterprise is quoted and can include SAML or OIDC SSO, deployment choices, dedicated support, and ACU-denominated capacity in the order form.

The March 2026 change moved self-serve away from the old public ACU system. Plans now use model-weighted quota that refreshes on daily or weekly boundaries, with paid overage through on-demand credits. Enterprise contracts can still use Agent Compute Units. That mixed state is not contradictory; it is a difference between public product billing and negotiated capacity.

Cognition's business model is therefore integrated software and model access, not a neutral workbench over subscriptions a customer already owns. A Devin customer pays Cognition for the product line and its usage. A local multi-provider workflow may instead pay Anthropic, OpenAI, or another model provider directly. Neither rail is inherently cheaper. The answer depends on whether Cognition's managed environment, integrations, knowledge, review, and support remove enough work to justify another meter.

What happened to Windsurf users

For an installed Windsurf user, the immediate answer is that the editor did not disappear. The rename arrived as an update. Projects, extensions, settings, and keybindings carried over according to Cognition's announcement and FAQ. The home page and pricing moved, the default product framing changed, and the bundled agent changed after Cascade reached end of life.

JetBrains users occupy a special branch. Cognition's current Desktop FAQ says Windsurf for JetBrains continues to be available, so the Windsurf name remains meaningful there even though the desktop editor is Devin Desktop. That is why saying “Windsurf no longer exists” is too blunt. The standalone desktop brand was retired; plugin products still use the name.

What is known, and what remains uncertain

The factual core is unusually clear. Cognition owns the acquired Windsurf business. Devin Desktop is the new name for the editor. windsurf.com redirects into devin.ai. Plans and settings carried over. Cascade reached end of life and Devin Local became the bundled agent. Spaces, the command center, Supercomplete, Fast Context, and ACP support define the current desktop proposition.

The uncertainty is the product boundary over time. Cognition is plainly moving toward one account and one command center across local and cloud agents. It has not thereby promised that every plugin, model, workflow, and plan will converge into one indistinguishable runtime. ACP makes third-party agents more portable inside the editor, while integrated billing and Cognition models pull in the other direction. Both can be true.

A buyer should treat uncertainty as part of the evaluation rather than a reason for speculation. Test the current build, export important settings, keep repositories in ordinary git, and avoid coupling automation to a marketing name when a protocol or CLI contract is available. The strongest hedge against product consolidation is portable project state, not predicting the next brand.

How Cognition compares with the workbench model

Cognition is building an integrated software-engineering vendor: agent runtimes, editor, models, environment, knowledge, review, plans, and enterprise service. The alternative model is a control plane around native agents and subscriptions that remain separate. The former reduces integration ownership. The latter preserves provider and infrastructure choice.

The combination can also be rational. Keep Devin Desktop for completions, local code reading, and its agent board. Use a workbench for long sessions on provider subscriptions, multiple accounts, remote hosts, phone approvals, and cross-provider cost evidence. The overlap should be measured. Paying two products to run the same agent job creates complexity; using one as the editor and the other as operations can be clean.

Questions people ask

Keep reading