Pricing

Find your gaps for free. Pay only when you want them closed.

The Reliability Audit is free forever — MIT, on PyPI, no signup. Alarm Engineering and Incident Operations are pilot-priced during the first customer cohort. No credit card to start. The audit answers "do I have a problem?" — the paid products answer "how do I fix it?".

Reliability Audit

DiscoveryFabric · Open source

Free

MIT license · forever

  • Read-only AWS audit (describe / list only)
  • Five-strategy alarm matching
  • DEGRADED alarm detection
  • Executive PDF + JSON output
  • Cross-account audits via STS
  • --demo mode, no AWS credentials needed
pip install opsfabric-discovery
Most popular starting point

Alarm Engineering

AlarmFabric · Pilot pricing

Talk to us

2-week paid engagement to start

  • Everything in the Reliability Audit
  • Creates the missing alarms in your account
  • Copilot / Autonomous / HIL remediation modes
  • SNS / PagerDuty / Opsgenie wiring
  • Tagged + reversible alarm provenance
  • Scheduled re-audits with drift detection
Book a demo

Incident Operations

OpsFabric · Annual contract

Talk to us

Volume-priced by managed resource count

  • Everything in Alarm Engineering
  • Multi-cloud incident response (AWS + Azure)
  • Slack-native triage + automated RCA
  • Copilot / Autonomous / HIL remediation
  • Jira lifecycle + Confluence post-mortems
  • GitHub PR for app-side fixes
Book a demo

All paid plans include a dry-run mode so you can see exactly what would be created before any write touches your account.

FAQ

Questions other teams asked first.

If yours isn't here, email [email protected] — you'll get a real answer, not a sales call.

Why is the Reliability Audit free?
Because nobody should have to pay to learn that their AWS alarm coverage is broken. The audit is MIT-licensed (open source as DiscoveryFabric) so it's auditable, embeddable, and useful even if you never become a paying customer. We make money on the layers above — Alarm Engineering closes the gaps, Incident Operations handles the incidents.
What does Alarm Engineering actually cost?
Pilot pricing during the first customer cohort — concretely, a 2-week paid engagement to wire it into your account, define your alarm pack, and confirm the SNS / PagerDuty routes. Steady-state pricing is volume-tiered by the number of managed resources. Email us with your AWS account size and we'll quote.
Do we need to share AWS credentials?
No long-lived credentials, ever. Alarm Engineering and Incident Operations assume a role in your account via STS with an external ID you control. You can revoke the trust policy at any time. The OSS audit runs against your local AWS profile and never sends data anywhere.
Can we trial Alarm Engineering without committing?
Yes. We can run it in dry-run mode against your account — same scan, same proposed alarm set, but no PutMetricAlarm calls. You see exactly what would be created (with the tags and SNS targets) before any write happens.
Is OpsFabric SOC 2 / ISO 27001?
Not yet — we're a pre-revenue product and SOC 2 is on the roadmap once we have committed customers requiring it. We're happy to walk you through our security posture today (data flow, retention, role permissions, encryption) if that's the gating concern.
Can I self-host the paid products?
Not today. Alarm Engineering and Incident Operations are managed SaaS — we operate the control plane, you grant the cross-account role. If self-hosted is a hard requirement for your environment, email us and we'll have a real conversation about it.

Have a specific use case in mind?

Email us with your AWS footprint and what you're trying to fix. You'll get a real answer from the person building this.

Email us