Coder: Self-Hosted Developer Workspaces

"Self-hosted" is used loosely across this market, so it is worth being exact. With Coder, both halves are yours. You operate the control plane, and you operate the compute the workspaces run on. Coder Technologies does not run any part of the serving path.

That distinction is what separates Coder from most of the products it gets compared against. A vendor that hosts the control plane and schedules workspaces into your cloud account is offering something real, but it is not the same thing, and it has different failure and compliance properties. With Coder, if the vendor's website went dark tomorrow, your installation keeps running until you choose to change it.

As of July 2026, coder.com/pricing lists exactly two editions. The older three-tier arrangement of OSS, Enterprise, and Premium is gone, so comparison articles that still describe three Coder tiers are out of date.

Coder does not publish a Premium price. It is described only as billed annually per user, with a contact-sales motion. Any specific per-seat figure you find elsewhere is somebody's estimate, and this page will not repeat it.

Coder Technologies Inc. is a private, venture-backed company. Its about page names Ammar Bandukwala and Kyle Carberry as co-founders, Rob Whiteley as chief executive, and lists Uncork Capital, Founders Fund, IQT, Notable Capital, Redpoint, Capital Factory, and Georgian Partners as investors. The company also raised a 90 million dollar Series C led by KKR, announced 04-01-2026, with Qube Research and Technologies and Uncork Capital participating - a funding event worth weighing in any durability assessment, since it buys runway the smaller vendors in this category do not have. The customer logos and the "over 100,000 community users" figure on the about page are vendor claims, published by the company selling the product, and should be treated as marketing rather than independent measurement.

Maintenance activity is genuinely strong and easy to check for yourself. Coder cuts a release from main on the first Tuesday of each month and patches it continuously. As of September 2026 the published release calendar puts 2.37 on mainline, released 09-01-2026; 2.36 on stable, released 08-04-2026; 2.35 on security support; and 2.34 and 2.29 on Extended Support Release. Coder's own release notes advise enterprise customers without a staging environment to install the stable line rather than mainline, which is a useful signal about how to plan your upgrade policy. Patch numbers move within days, so plan against the release line rather than a specific tag.

The most important durability item has a date on it. Coder Tasks is deprecated and, in the shipped v2.37 line, hidden by default: the Tasks API at /api/v2/tasks is only registered when CODER_ENABLE_AI_TASKS is set, which is verifiable in v2.37.3's own source. The removal itself - the CLI verbs, the API and the RBAC resource - is merged on the main branch and ships in v2.38, scheduled for 10-06-2026, so a deployment that still calls the Tasks API has one release left rather than none. Coder's migration guide on main states that requests to the Tasks API fail and directs readers to a previous documentation version if they need to read about Tasks at all. Note what "removed" does and does not mean: it is removal from new releases, not from every deployment on the same day. Premium customers on the 2.34 Extended Support Release, which began 06-02-2026 and runs twelve months, keep Tasks until that line ends. Teams not on Premium have no such runway, and for them the migration is now overdue rather than upcoming. The documented replacement is Coder Agents, which entered beta on 05-06-2026 and reached general availability in that same v2.37 release. It runs entirely self-hosted with no SaaS component and works with any LLM provider you configure. The two are architecturally different rather than drop-in equivalents, and the difference is a security argument as much as an operational one: Tasks ran the agent inside the workspace with LLM credentials injected into the workspace environment, while Agents runs the agent loop in the control plane and, in Coder's words, never lets those credentials enter the workspace. The replacement API is Chats at /api/v2/chats, which keeps conversation state in the Coder database rather than in the workspace and supports multi-turn history and sub-agent delegation. If you are evaluating Coder for agent workloads, build on Agents.

Agent work is now separately metered, which is a cost line that did not exist when this category was only about workspaces. Coder's licensing documentation describes Community licenses as supporting up to five concurrently active agents deployment-wide, with no limit on how long they run and additional agents queued behind them, and Premium licenses as including a preset pool of Agent Hours shared across the deployment with unlimited concurrency. Agent Time is measured as the cumulative duration of model invocations that produce chat messages - it excludes time spent composing messages, waiting between turns, and failed or retried calls. Budget for it separately from seats, because it scales with how much autonomous work you run rather than with headcount.

Two AI features were also renamed: AI Bridge is now AI Gateway, and Agent Boundaries is now Agent Firewall. Coder describes the AI Gateway change as a cosmetic rebrand that nonetheless moves user-visible names, configuration options, the canonical HTTP API path, and the Prometheus metric names. Deprecated aliases still resolve for gateway and proxy controls - CODER_AIBRIDGE_*, --aibridge-*, the aibridge: YAML group, /api/v2/aibridge and the coder_aibridged_* metrics - with one exception that will bite an upgrade: provider configuration through environment variables, flags, and YAML has been removed under both the old and the new name, and is now managed in the database. New settings get only the ai_gateway name with no alias, so the old names are a migration window rather than a permanent equivalence. As of September 2026 the coder/aibridge and coder/boundary repositories both still exist under their original names and neither is archived. Agent Firewall's documentation carries the same warning that some configuration options and internal references still use the old name. Both features are part of AI Governance, which is included with a Premium license rather than sold as a separate add-on; Community deployments cannot access either.

On the exit question, Coder is in a better position than most of this category. Because the platform is AGPL-3.0 and you already operate every component, a change of vendor direction is a support and roadmap problem rather than a service shutdown. Your templates are Terraform, which you would keep regardless. That is a materially different risk profile from a hosted CDE, where a strategy change can take your environments with it.