Developer
$0
forever
For prototyping and instrumenting your first production service.
- 3 projects
- 50,000 traces / month
- 7-day data retention
- Community support
Platform access is predictable. Usage grows with the traces you retain and the workloads you deploy, never with the number of engineers investigating them.
Developer
forever
For prototyping and instrumenting your first production service.
Team
workspace / month + usage
For engineering teams operating AI systems across environments.
Enterprise
annual agreement
For high-volume and regulated AI workloads with advanced controls.
| Capability | Developer | Team | Enterprise |
|---|---|---|---|
| Agent and model deployments | 3 projects | Unlimited | Unlimited |
| Tracing and logs | 50k / month | 1M included | Custom |
| Token and cost analytics | Basic | Advanced | Advanced |
| Deployment correlation | Not included | Included | Included |
| Reliability objectives | Not included | Included | Custom |
| Workspace access controls | 1 user | RBAC | SAML + SCIM |
| Data retention | 7 days | 90 days | Custom |
| Support | Community | Priority email | SLA + dedicated |
Hosted inference and third-party model-provider charges are billed separately by those providers.
Frequently asked
No. Instrument existing services with OpenTelemetry or the Metrune SDK, or deploy new workloads directly. Both paths appear in the same production view.
Metrune is provider-neutral and supports OpenAI, Anthropic, Google AI, Azure OpenAI, AWS Bedrock, and custom OpenAI-compatible endpoints.
Usage is captured per model call and attributed to agents, releases, environments, customers, and teams using current provider pricing or your negotiated rates.
Yes. Environments have separate credentials, retention policies, budgets, alert rules, and access controls while remaining comparable within one workspace.
Payload capture is configurable. Teams can redact fields, disable body storage, set retention windows, or keep telemetry inside a private deployment.
Metrune correlates reliability and cost changes with deployment history, alerts the owning team, and preserves the prior release for a fast rollback.