No investors. No exit to force.
OpsPing has taken zero outside funding. There are no VCs expecting a 10x return, no board pushing for an acquisition, and no growth-at-all-costs roadmap that ends with the product being absorbed or abandoned. Opsgenie didn't die because it failed — it died because it was acquired. That failure mode does not exist here.
Profitable at a scale most tools consider worthless.
Our entire overhead is infrastructure: one backend service, a database, and push delivery that costs fractions of a cent per notification. We don't need a hundred thousand users to survive — a small, steady customer base covers costs indefinitely. The bottom of this market is chronically abandoned because it's unprofitable for companies with payroll. It's profitable for us. That's not a vulnerability; it's the whole design.
Your data is yours — leaving is as easy as arriving.
Full data export on request: schedules, rotations, escalations, users, alert history. Our API is deliberately OpsGenie-shaped, which means the same compatibility that makes migrating in a one-line change makes migrating out one too. Lock-in is a strategy for products that are afraid of comparison. We'd rather win the comparison.
Source-code escrow, once profitable.
We commit to establishing source-code escrow — with release terms that trigger if the service is ever discontinued without a successor — once OpsPing is profitable (subscription revenue covering operating costs). We'll publish the escrow status on this page when it's in place. Until then, your continuity protection is pledges 3 (full data export) and 5 (private deployments): a customer whose continuity requirement is absolute should run a private deployment, where our company's survival is irrelevant to their pager working.
Private deployments: your paging can outlive us.
The backend is a single Node.js service backed by DynamoDB — small enough to run as your own private, single-tenant deployment, on your infrastructure or operated for you. Teams that need maximum independence from any vendor (including us) can hold the whole system themselves. Migration guide has the details.
If we ever did shut down, here's the protocol.
Pledges about why it won't happen are cheap. Here's what happens if it somehow does: 90 days minimum notice to every customer, export tooling and migration assistance during the window, and release of escrowed source (per pledge 4, once in place). No abrupt lights-out. You will never read about our shutdown in a changelog you found by accident.
Built in the open, verified in public.
Public changelog, public security practices, honest SOC 2 status (where we are, not where we wish we were), and a live status page. We publish our reliability instead of asking you to take it on faith.
One honest caveat: this page is a pledge — a public commitment we'll be held to — not a contractual guarantee. If you need contractual teeth (SLA terms, escrow clauses in an MSA), that's a Business plan conversation, and we're happy to have it.
— The OpsPing team