Pricing That Scales With Decisions, Not Data Volume
An OpsTrails event is a deliberate change — a deploy, rollback, release, or data load. Not a log line, metric, or trace. Even a 200-service organization shipping 50 changes a day records about 1,500 events a month, so plans stay predictable at any infrastructure size.
Start free. Scale when you're ready.
Free
Starter
Pro
Running a Bigger Fleet?
Hundreds of services, multiple teams, governance requirements — tell us about your architecture and we'll walk you through a setup that fits: pipelines per team, deployment policies, change-freeze windows, and retention that satisfies your audit needs.
Frequently asked questions
Isn't OpsTrails another logging tool?
No. OpsTrails doesn't collect logs, traces, or metrics. It tracks operational events — deployments, rollbacks, data loads, and releases — on a single timeline. Think of it as a changelog for your infrastructure that your AI assistant can query.
How is OpsTrails different from Datadog?
Datadog monitors application performance. OpsTrails tracks what changed and when. They're complementary — connect Datadog as an analytics provider and OpsTrails automatically shows before/after metrics for every deployment.
Does OpsTrails replace monitoring tools?
No. OpsTrails sits alongside your monitoring stack. It answers 'what changed?' while your monitoring answers 'what's broken?' Connect them together for automatic impact analysis.
How long does setup take?
Under 5 minutes. Add one step to your CI/CD pipeline to start recording events. Connect an analytics provider for impact metrics. Set up the MCP server for AI queries. Each step is independent.
What happens when I exceed my event limit?
New events are rejected with a 429 response until the quota resets on the 1st of the month. You'll receive a notification at 80% usage so you can upgrade proactively. Events already recorded stay accessible for the full retention period.