Start with one service. Scale to every AI workload.

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

$0

forever

For prototyping and instrumenting your first production service.

  • 3 projects
  • 50,000 traces / month
  • 7-day data retention
  • Community support

Team

$99

workspace / month + usage

For engineering teams operating AI systems across environments.

  • Unlimited projects
  • 1 million traces included
  • 90-day data retention
  • Budgets, alerts, and deployment history
  • Role-based workspace access

Enterprise

Custom

annual agreement

For high-volume and regulated AI workloads with advanced controls.

  • Custom event volume and retention
  • SAML SSO and SCIM
  • Private networking and deployment
  • Audit logs and support SLA
  • Dedicated solutions engineering
CapabilityDeveloperTeamEnterprise
Agent and model deployments3 projectsUnlimitedUnlimited
Tracing and logs50k / month1M includedCustom
Token and cost analyticsBasicAdvancedAdvanced
Deployment correlationNot includedIncludedIncluded
Reliability objectivesNot includedIncludedCustom
Workspace access controls1 userRBACSAML + SCIM
Data retention7 days90 daysCustom
SupportCommunityPriority emailSLA + dedicated

Hosted inference and third-party model-provider charges are billed separately by those providers.

Frequently asked

Technical answers, without the hand-waving.

Do we have to move our agents onto Metrune?

No. Instrument existing services with OpenTelemetry or the Metrune SDK, or deploy new workloads directly. Both paths appear in the same production view.

Which model providers are supported?

Metrune is provider-neutral and supports OpenAI, Anthropic, Google AI, Azure OpenAI, AWS Bedrock, and custom OpenAI-compatible endpoints.

How is token cost calculated?

Usage is captured per model call and attributed to agents, releases, environments, customers, and teams using current provider pricing or your negotiated rates.

Can we separate staging and production data?

Yes. Environments have separate credentials, retention policies, budgets, alert rules, and access controls while remaining comparable within one workspace.

Does Metrune store prompts and responses?

Payload capture is configurable. Teams can redact fields, disable body storage, set retention windows, or keep telemetry inside a private deployment.

What happens when a release regresses?

Metrune correlates reliability and cost changes with deployment history, alerts the owning team, and preserves the prior release for a fast rollback.