ProductComing soon
Why We're Building an OpsGenie Replacement
The story behind OpsPing — why a drop-in compatible API matters, and how we're approaching the build from a monorepo with plain HTML and OpenTofu.
EngineeringUpdated 2026-10-01
Why we rewrote our paging backend in Go — and how one process handled 1,000 alerts/s
Same API, one Go process, PostgreSQL 17, and a mixed two-minute 1,000 alerts/s burst: 222,021 creates accepted across the run, zero drops or HTTP failures, and 83 ms ingest p95. Full numbers, failure discoveries, and methodology.
On-Call CultureComing soon
Your On-Call Tool Should Be Boring (And That's a Good Thing)
Why familiarity beats novelty in incident response tools, and how we're designing OpsPing to feel like second nature from the first minute.
Blog posts coming soon.