MCP Gateway
The local capability router that exposes CHAOS tools to compatible AI clients.
Loading...
Loading...
Loading...
Individual evaluation
For individual developers who want the local CHAOS loop around their own AI provider.
Collaborative operation
For teams coordinating shared workflows, runtime visibility, and repository activity.
Advanced deployment
For advanced control, customization, compliance, and operational requirements.
Technical comparison
Tiers differ by runtime scope, coordination depth, tool routing, audit visibility, and deployment control.
Scroll to see all tiers
| Capability | Developer | Team | Enterprise |
|---|---|---|---|
| Free trial | 10 days, first checkout only | No introductory trial | Sales-led |
| Pricing | $29/mo | $60/mo | Custom |
| Best for | Individual local evaluation | Team coordination | Advanced deployment and compliance |
| Runtime | Local runtime | Local + cloud server support | Custom deployment |
| MCP Gateway | Included | Included | Included + custom routing |
| MCP tools | Core tool surface | Team tool surface | Full + custom tools |
| Agent types | 15 | 15 | All + custom |
| PM orchestration | Individual workflows | Team-visible workflows | Custom orchestration workflows |
| Context DB | Local project context | Shared/team context planned | Custom retention and policy |
| CHAOS Engine DB | Local operational state | Team operational state | Dedicated/custom operational state |
| Praxis Store | Local reusable knowledge | Team reusable knowledge planned | Admin-controlled knowledge policy |
| Ingestor | Repo/docs ingest | Shared ingest workflows | Custom adapters |
| Multi-clone sync | Clone discovery + sync | Clone discovery + sync | Federation/custom sync |
| Audit trail | Tool calls, runs, decisions | Team audit visibility | Compliance exports and review |
| Dashboard | Dash log | Full dashboard planned | Custom dashboards |
| AI models | BYOK | BYOK | BYOK + private model routing |
| Custom MCP integrations | Not included | Not included | Included by agreement |
| Support | Priority/SLA by agreement |
What MCP tools include
CHAOS exposes capabilities through an MCP Gateway so compatible AI clients can work through explicit local tools instead of vague hidden access.
Scroll to see all tool areas
| Tool Area | What It Means | Developer | Team | Enterprise |
|---|---|---|---|---|
| Context tools | Search, hydrate, inspect, and reuse project context. | Included | Shared/team context planned | Custom retention and policy |
| Agent tools | List, start, stop, inspect, and route agent runs. | Included | Team-visible activity | Custom agents and routing |
| PM tools | Turn work into intake, planning, execution, verification, and handoff state. | Individual workflows | Team-visible workflows | Custom orchestration |
| Runtime tools | Inspect local runtime health, logs, process state, and service status. | Local runtime | Local + cloud runtime visibility | Custom deployment controls |
| Git and sync tools | Track repo activity, branch movement, clone discovery, and integration state. | Local repo/run visibility | Multi-clone sync | Federated/custom sync |
| Audit tools | Record tool calls, decisions, prompts, run history, and file-change evidence. | Audit trail + dash log | Team audit visibility | Compliance exports |
| Provider tools | Connect and inspect BYOK provider configuration. | BYOK | BYOK with team policy planned | Private/self-hosted provider routing by agreement |
What runs locally
CHAOS runs near your repository. The local runtime coordinates the services agents need while keeping project context, run history, and audit evidence close to the code.
What BYOK means
CHAOS does not sell model credits or meter token usage. You connect your own provider keys, choose your model, and pay that provider directly. CHAOS supplies the local operating layer around the model: context hydration, tool routing, task state, audit records, and workflow coordination.
Subscription boundary
An active subscription gates CHAOS infrastructure processes, not ownership of your data. Active runtime services require an active projected subscription. Local project records, context entries, Praxis entries, metrics, audit logs, traces, and historical run data should remain available through read-only and export paths.
Access boundary
Scroll to see access states
| Area | Active access | Expired or inactive access |
|---|---|---|
| Runtime supervisor | Full mode | Read-only/account/export mode |
| MCP Gateway | Full tool routing | Account/status/export routes |
| Agents and PM orchestration | Enabled | Disabled |
| Provider calls through CHAOS | Enabled | Disabled |
| Local data | Read/write where supported | Read/export |
| Audit history | Live records + export | Historical view/export |
| License/account path | Available | Available |
Definitions
The local capability router that exposes CHAOS tools to compatible AI clients.
The set of explicit local capabilities CHAOS exposes, such as context search, agent lifecycle, PM routing, runtime status, audit export, and provider configuration.
The workflow layer that turns prompts into intake, planning, execution, verification, handoff, and trace-linked results.
The local project memory used for ranked context hydration.
The operational state store for tasks, events, assignments, approvals, audit records, and runtime state.
Reusable engineering knowledge that can compound across runs.
Records of tool calls, prompts, decisions, file changes, run history, and workflow movement.
Bring Your Own Key. Users connect their own AI provider keys and pay model costs directly to that provider.
Pricing FAQ
No. CHAOS is BYOK. Your AI provider bills model usage separately.
The first Developer checkout can include one 10-day introductory trial. Eligibility is enforced server-side from both local billing history and Stripe history.
Developer includes the local CHAOS runtime, MCP Gateway, core tool surface, 15 agent types, PM orchestration, context memory, audit visibility, and BYOK provider support for individual workflows.
Developer is for individual local evaluation: local runtime, MCP-connected tools, 15 agent types, PM orchestration, Context DB, audit trail, dash log, and BYOK provider support.
Team adds team-oriented coordination: multi-clone sync, clone discovery, local and cloud server support, team-visible runtime activity, and planned full dashboard visibility.
Enterprise adds all agent types, custom agents, custom MCP tools, custom integrations, advanced deployment requirements, procurement support, and custom operational terms.
An agent type is a specialized workflow role, such as debug, docs, test, review, security, migration, or language-specific development support.
PM orchestration turns work into structured state: intake, planning, assignment, dependency tracking, execution, verification, handoff, and audit-linked results.
No. CHAOS does not meter model usage. Model spend stays between you and your provider.
Local project records, context entries, Praxis entries, metrics, audit logs, traces, and historical run data should remain accessible through read-only/export paths.
Contact sales for Enterprise evaluation, custom agents, custom MCP integrations, self-hosted or controlled deployment requirements, compliance review, procurement, or SLA-backed support.
Next step
Start checkout, let Stripe confirm the subscription, and wait for the local billing projection to unlock access across the gated account surfaces.