We do not price the work before we can see what it is worth.
Two plans you can start alone, and two engagements scoped after the observability has something to say. Understand the product locally for nothing; observe how work actually moves through it for $19 a developer; act on what that shows.
What each one proves.
Open source
- The whole model, locally
- Audit of your own changes
- Proves the technology
- No buyer risk — run it yourself
Connect
- One model and one queue across machines
- Team-wide audit baseline
- Shows where your time goes
- Monthly, self-service
Team
- Implementation around your workflow
- Continuous audit, published in CI
- Proves the second clock fell
- Named engineer
Enterprise
- Several products on one map
- Role-based access and ownership
- On-prem or your cloud, with SSO
- SLA / dedicated support
What you actually get.
The free engine is the whole model on your own machine. Connect shares it across the team and starts the measurement. Team and Enterprise are implementations — the rows below are what gets built, not what gets unlocked.
| What | Open source | Connect | Team | Enterprise |
|---|---|---|---|---|
| Built from your own code, in ten linked dimensions | ✓ | ✓ | ✓ | ✓ |
| Written to .gitmir/model, beside the code, in your repository | ✓ | ✓ | ✓ | ✓ |
| Product map, business logic, data flows, lifecycles, ownership | ✓ | ✓ | ✓ | ✓ |
| Products and repositories | Unlimited | Unlimited | Unlimited | All on one map |
| What a change breaks, in both directions | ✓ | ✓ | ✓ | ✓ |
| Every place the code and the written rules disagree | ✓ | ✓ | ✓ | ✓ |
| Works before the code exists — the model first, the code against it | ✓ | ✓ | ✓ | ✓ |
| Rebuilt on merge, as part of CI | — | — | ✓ | ✓ |
| What | Open source | Connect | Team | Enterprise |
|---|---|---|---|---|
| Local MCP for Claude Code, Codex and Cursor | ✓ | ✓ | ✓ | ✓ |
| Sixteen tools and twelve written procedures | ✓ | ✓ | ✓ | ✓ |
| A key per developer, per machine | — | ✓ | ✓ | ✓ |
| Wired into the agents your team runs, by us | — | — | ✓ | ✓ |
| Done means verified — a task closes when its own checks pass | ✓ | ✓ | ✓ | ✓ |
| What | Open source | Connect | Team | Enterprise |
|---|---|---|---|---|
| Developer seats | Your own machine | $19 each, monthly | In the engagement | In the engagement |
| Viewer seats | — | Free, unlimited | Free, unlimited | Free, unlimited |
| One task queue and one model across machines | — | ✓ | ✓ | ✓ |
| What is being built and what is running, visible to everyone | — | ✓ | ✓ | ✓ |
| What | Open source | Connect | Team | Enterprise |
|---|---|---|---|---|
| Two clocks on every change — computed, not logged | — | ✓ | ✓ | ✓ |
| Rework by area of the product, never by person | — | ✓ | ✓ | ✓ |
| The engineering audit | Your own changes, locally | Included, team-wide | Continuous | Rolled up by product and quarter |
| Published as a check on the repository | — | — | ✓ | ✓ |
| What | Open source | Connect | Team | Enterprise |
|---|---|---|---|---|
| GitHub Actions or GitLab CI | — | — | ✓ | ✓ |
| Linear, Jira or Asana | — | — | ✓ | ✓ |
| Impact and rules, posted on the pull request | — | — | ✓ | ✓ |
| Slack or Teams | — | — | ✓ | ✓ |
| Installed on the machines and handed over working | — | — | ✓ | ✓ |
| What | Open source | Connect | Team | Enterprise |
|---|---|---|---|---|
| An interface per role, not per repository | — | — | — | ✓ |
| Access by role and by area | — | — | — | ✓ |
| Ownership on the map — including the areas nobody owns | — | — | — | ✓ |
| What changed this month, as a report a non-engineer reads | — | — | — | ✓ |
| Review before execution, recorded against the object | — | — | — | ✓ |
| On-prem or your own cloud, with SSO | — | — | — | ✓ |
| What | Open source | Connect | Team | Enterprise |
|---|---|---|---|---|
| Licence | AGPL-3.0 | Commercial | Commercial | Commercial |
| Telemetry | None | None | None | None |
| Source code leaving your machine | Never | Never | Never | Never |
Do not sign anything before the audit has something to say.
There is nothing to buy in between. Run the open source, connect the developers who work on the same product, and let real changes accumulate. When the audit shows where the second clock concentrates, we look at it together — and if the recoverable part is too small to be worth an engagement, we will say so.