Windsurf builds SWE model family

Diving deeper into

Codeium

Company Report
Windsurf also develops its own in-house model family—SWE-1, SWE-1-lite, and SWE-1-mini—designed specifically for software engineering workflows;
Analyzed 5 sources

Building an in house model family turns Windsurf from a thin wrapper around outside labs into a vertically integrated coding product with more control over speed, cost, and workflow fit. SWE-1, SWE-1-lite, and SWE-1-mini are split by job, with the full model handling harder reasoning and tool use, the lite version serving broad Cascade usage, and the mini model powering instant tab suggestions, which lets Windsurf tune each layer of the editor for the exact task instead of paying one expensive general model to do everything.

  • The important design choice is that these models are built for software engineering, not just code generation. Windsurf describes SWE-1 as covering the full engineering lifecycle, including long running tasks, incomplete work, and multiple surfaces like the editor and tools, which matches how Cascade operates across files, terminal actions, and broader codebase context.
  • This is also a unit economics move. Windsurf’s margins have been pressured because frontier model inference costs can exceed what it charges users. Proprietary models give it a path to replace some third party usage with cheaper first party inference, while keeping premium performance for tasks where speed and low latency matter most.
  • The broader pattern is that top AI IDEs are moving toward their own task specific models. Cursor has built specialized completion and editing models, then expanded into a first party frontier coding model. In this market, owning the model is becoming part of owning the product, because the best coding experience depends on tight coupling between the model, the editor, and the agent harness around it.

Going forward, the winners in AI coding will look less like plugin companies and more like full stack labs for developer workflow. Windsurf’s SWE family points toward a product where autocomplete, retrieval, agent steps, and enterprise deployment are all tuned together, which should improve both gross margins and product lock in as coding shifts from single prompts to continuous agent driven work.