Codus for enterprise, and v2 ships in June

Two things on the runway today, and they're connected.

Codus is opening for enterprise teams — direct contracts, SSO, audit log, dedicated support — and version two ships in June with the team-scale features that make Codus work for an engineering organization instead of just a single developer.

The single-developer build — the one going public this week at $20/dev/month — is the foundation. v2 is what stacks on top of it for teams. Enterprise is how we package the whole thing under one contract for organizations that need it that way.

Codus for enterprise

What an enterprise contract gets you that the per-seat plan doesn't:

Single sign-on. Okta, Entra ID, Google Workspace — provision and de-provision the way the rest of your stack already works.
Audit log. Every quadrant action, every agent diff, every outbound PR — recorded, exportable, queryable. Compliance teams stop asking and security teams stop worrying.
Centralized billing. One invoice across the org, consolidated usage reporting, NET-30 terms. No more fifty individual cards filed under "engineering miscellaneous."
Role-based access. Scope who can touch which repos and which projects, with the granularity an engineering director actually needs.
Self-hosted cloud planner (optional). For orgs that need the planner inside their own perimeter — same product, your infrastructure, our deploy guide.
Procurement-ready paperwork. MSA, DPA, security questionnaire, SOC 2 letter — already drafted. We can move at your legal team's pace, not yours.
Dedicated support. Named contact, response SLA, a shared Slack channel. When something blocks the team, it gets a human within hours, not a ticket queue.

If you've been wanting to roll Codus across a 50-person engineering team without writing fifty individual seat-license memos, this is the door.

What lands in v2

June 2026. Five things, all aimed at teams:

Shared cloud planner. Task routing across the whole team, skill profiles per engineer, a dependency graph that spans engineers, and a real-time cross-engineer status view. The planner stops being a single-machine convenience and starts being a team operating system.
Background agents. Agents that survive app restart and a closed laptop — pick up exactly where they were on the next launch, with full quadrant state intact.
Windows and Linux builds. Same engine, same agent runtime, native installers. Heterogeneous teams stop being blocked by the Mac-only floor.
Public planner API. Linear, Jira, your in-house ticket system — drop tickets straight into a quadrant. No more copy-paste from your tracker into the planner.
Quadrant scale-out. Past the current four-per-machine cap, into "as many agents as the hardware can run." Bigger machines unlock more parallel agents without code changes.

Why both at once

The $20/dev plan is the floor — anyone who codes alone or in a small squad should be on it from day one. v2 is what the floor builds toward. Enterprise is how we deliver both, under one MSA, for organizations that don't want their CIO to read a self-serve checkout flow.

We've been holding back on the enterprise conversation deliberately. We wanted the single-developer build to be rock solid before opening the door to procurement teams. It is. So the door is open.

How to get on the list

If you want enterprise pricing or early access to v2, reach out via the contact form. Mention "enterprise" or "v2" in the message and we'll route it to the right pile.

v2 ships in June. Enterprise contracts can start as soon as your legal team can move.

More to come.