Built by people who carried the pager
Gravityloop is on-call infrastructure built by engineers who got tired of paying enterprise prices for a glorified phone tree.
Why we started Gravityloop
After years of carrying the pager ourselves — Datadog alerts at 3am, escalation policies that never quite escalated on time — we kept running into the same thing: on-call tooling is expensive, sales-gated, and built for whoever's signing the check, not whoever's getting paged.
Then Atlassian put Opsgenie on a path to end-of-life, and a lot of teams found themselves migrating whether they'd planned to or not. That's the opening we built Gravityloop for.
There's a better way
On-call shouldn't require a security review to sign up for or a sales call to see pricing. It should be a tool: point your monitoring at it, and it pages the right person over SMS, voice, or Slack — every time, and provably so.
That's what we built. Nothing more, nothing gated behind "contact sales."
How we work
We don't sell engagements or bill by the hour — Gravityloop is software you sign up for. And we don't sell seats: you pay for the services you're protecting, and everyone who needs an account gets one free. Each service picks the hours it's covered for, so the internal dashboard that can wait until Wednesday morning doesn't cost what the payments API does. Every integration, SSO and the audit log are there from day one. No enterprise tier holding back the features every team actually needs, and no line item that goes up because you made your on-call safer.
Migrating in is a command, not a project. gravityloop migrate --from pagerduty (or
--from opsgenie) reads your existing schedules, escalation policies, and integrations, and has
you routing real alerts in minutes. The migration client is open-source, so you can read
exactly what it's doing before you hand over an API token.
Experience that matters
Our team has spent the last decade running production systems at scale — the kind where a bad deploy means someone's phone starts ringing at 2am. We've been the ones holding the pager, writing the escalation policies, and maintaining the runbooks other people relied on mid-incident.
That's the experience behind every decision in Gravityloop: what actually helps when a system is down, and what's just enterprise theater.
Our mission today
Gravityloop exists to fix on-call — the thing every engineering team pays too much for and likes the least. We believe the tool you page out to at 3am should be transparent about what it costs, honest about what it delivers, and built by people who've actually carried it.
We believe in transparent pricing, honest reliability numbers, and a product that never punishes you for growing. When you migrate off PagerDuty or Opsgenie, we want it to be the last on-call migration your team ever has to do.
What drives us
The principles that guide everything we do.
Price tracks cost, not leverage
If the price ever moves, it's because our costs did — never because we found a new way to charge you.
No feature gating
SSO, SCIM, and the audit log ship in the base plan. We don't hold basics hostage to force an upgrade.
Built for whoever's holding the pager
Keyboard-first, no seats to count, no sales call required to start. We build for engineers, not procurement.
The boring part, done right
An on-call tool that's down during your incident is the worst kind of irony. We measure ourselves in the open.