| What it does | AI coding spend and usage analytics for teams
| See, trace, stop, and prove what your AI agents do
|
|---|
| Stage | Not given
| Startup
|
|---|
| Founded | Not given
| 2026
|
|---|
| Based in | Not given
| AU
|
|---|
| Pricing model | Freemium
| Freemium
|
|---|
| Pricing | Community (self-hosted): free for up to 5 seats under Community License. Managed (hosted): free for 5 seats, then $1 per active developer per month.
| Free: Community edition (1,000 runs/month, 1 workspace, 7-day retention, self-hosted). Starter: A$49/month (20,000 runs/month, 5 seats, 30-day retention). Growth: A$600/month (50,000 runs/month, 10 seats, 60-day retention). Scale: A$1,800/month (75,000 runs/month, 20 seats, 60-day retention). Pro: A
|
|---|
| Key features | - AI spend attribution per pull request and issue, showing whether work merged
- Cost forecasting showing where month's bill will land at current pace
- Alerts for developers near Claude session or weekly limits
- Seat utilization visibility showing barely-used seats
- Cost breakdown by person, tool, and model with token and latency estimates
- Device and agent configuration health reporting
- Support for local runtimes like Ollama and LM Studio
- GitHub integration to match AI usage to work and pull requests
- No keystroke surveillance, browser capture or network interception
| - Record every model call, tool use and agent step
- Replay decisions from original context
- Policy enforcement before tool execution
- Turn failures into regression tests
- Tamper-evident audit records
- MCP gateway integration
- Incident tracking from failed runs
- Prompt registry and playground
- Fleet control room and policy simulation
- Signed audit records with integrity verification
|
|---|
| What makes it different | - Unified dashboard across Claude, Cursor, Codex, and GitHub Copilot instead of separate tool dashboards
- Open-source and self-hosted option under Community License for data privacy
- Cost attribution to actual work via GitHub integration, not just tool-level bills
- Individual developer control over what data is collected and shared
- Designed for privacy-conscious teams with no keystroke or browser monitoring
| - Replay over retell: hold context fixed, run the model fresh to verify behavior actually changed
- Block before it ships: enforce policy at release time, not after a failure in production
- Self-hosted by default: full control with deployment in customer's own network
- Tamper-evident records checkable without Runback
- Turn production failures into future test cases
|
| Community votes | 0 | 0 |
| DR (Domain Rating by Ahrefs) | Not checked yet ● no change since last check | Not checked yet ● no change since last check |
| Trust Flow (Majestic) | 2 | 0 |
| Citation Flow (Majestic) | 20 | 9 |
| Referring domains (Majestic) | 12 | 1 |