Self-hosted Cloud Agents
read at source ↗ cursor.com
Self-hosted Cloud Agents
Source: Cursor Date: 2026-03-25 URL: https://cursor.com/changelog/03-25-26
Summary
Cursor ships self-hosted cloud agents: organizations run agent infrastructure inside their own machines and networks, with codebase, build outputs, and secrets staying on internal infrastructure while agent tool calls execute locally. Identical functionality to Cursor-hosted agents — isolated VMs, full dev environments, multi-model support, plugins. Activated via Cursor Dashboard.
Implications
Agent-IDE feature race. Self-hosted agents remove the primary enterprise objection to Cursor: data residency and IP leakage. This makes Cursor competitive in regulated industries (finance, healthcare, defense) that Windsurf and GitHub Copilot Enterprise have targeted. Aider and Claude Code are already local-first by default — Cursor’s self-hosted option catches up on that axis while retaining the cloud-coordination layer.
Pricing model evolution. Self-hosted removes Cursor-managed compute as a cost layer, which changes the pricing math. If enterprise customers host their own agents, Cursor’s value becomes the model routing, the IDE, and the protocol — similar to how HashiCorp sells Terraform Enterprise (tooling + support, not compute). Watch for a dedicated enterprise pricing tier that separates IDE licensing from compute costs.