Instatus: $48K MRR with Every Metric Public, After Dropping "Sup" and Repricing Upmarket

“When something breaks, how do you tell your customers?” A SaaS that solves exactly that one problem, a status page, has grown to $48,017 MRR and 1,248 paying customers. Instatus publishes its business metrics on an open page anyone can check (as viewed in August 2026, showing a May 29 update: $576,208 ARR and 62,261 total users).

Knowing the product’s predecessor changes what those numbers mean. The first version founder Ali Salah built was called “Sup,” and it did not attract a single paying customer. Today’s Instatus is a “second lap” over the same problem space with the name, brand, pricing, and target customer all replaced. It took off not from rebuilding the product, but from rebuilding how it was sold — that ordering is the heart of this case.

The numbers

The failure wasn’t the product — it was the choice of customer

What stays consistent in Salah’s retrospectives is that he does not blame Sup’s failure on features. Sup was built for startups, but early-stage companies simply did not need a status page. With few customers, there is nobody to notify about an outage, and polishing that page ranks near the bottom of any priority list. He was selling, with a likable brand, to a segment where the problem did not exist.

The pivot to Instatus is a prescription written against that diagnosis. The companies that genuinely need a status page are the ones with many customers, where outage-time support tickets are a real cost and SLA accountability is real. So he shifted the target customer upmarket, rebuilt the brand into something that reads as trustworthy to that segment, and raised prices. Not cheaper-and-broader, but pricier-and-narrower, filtering for the segment whose problem is acute. Directionally, like the Deep Research pricing pivot, this is the pattern of moving the pricing before moving the feature set.

A B2B tool has to survive being explained inside the buyer’s company. In that setting, a cutesy brand gets in the way of the explanation, while a serious name and a substantial price actually ease the approval. What Sup’s failure demonstrates is a quiet but decisive variable: for identical functionality, brand and price determine whose internal approval process you can pass.

Acquisition, and openness as a strategy

The relaunch happened on Twitter and Product Hunt, and Salah says his “Twitter friends really helped me spread the word.” The growth work he lists afterward: improving the product and adding features, introducing higher-priced plans, blog content produced with Embarque.io, and small side projects like a /now page and a GitHub repository. None of it is flashy; all of it consistently places exposure where developers and technical decision-makers already are.

Publishing the company’s metrics works as an exposure engine in the same vein. An “open page” disclosing everything from MRR to paying-customer and non-profit-account counts becomes something people talk about, link to, and, as this article shows, verify. As with Plausible’s $1M ARR, which led with open metrics, in developer-facing products, not hiding doubles as both trust and marketing.

The pace of growth is worth recording too: from $5K in February 2022 to $48K most recently, roughly 10x in about four years. Averaged monthly, it is the compounding curve typical of B2B subscriptions, with no dramatic spikes. The plans visible at the $5K milestone (Instatus Now for outage detection, monitoring, incident management) show a staged expansion from a single feature toward adjacent ones.

The open page also makes the revenue structure legible. Of 62,261 total users, 1,248 pay, about 2%. Most usage is free. That $48K MRR still works because the paying side averages about $38/month per customer (MRR divided by paying customers), clearly above free-tool price norms. “Widen the base for free, charge the acute segment properly”. The post-pivot design shows up directly in the numbers. That the page even discloses 93 free non-profit accounts is a detail showing how far the openness policy goes.

Risks and weaknesses

The structural position of this business is “one feature of a bigger suite.” Status pages are a space where majors like Atlassian (Statuspage) sell the same product, and monitoring SaaS sometimes bundles it as a feature. A single-feature specialist’s defense rests on polish at that single point and pricing flexibility. Salah founded solo and only hired his first part-time engineer once MRR grew. Supporting an infrastructure-adjacent product, one tied to outages and reliability, with effectively one or two people is a cost-structure strength but also a permanently taut rope where availability expectations are concerned. Healthchecks.io’s one-person SaaS is the precedent for operating that same tension over a decade.

One more note: the open metrics are a self-operated page, not audited figures. Verifiability is high, but their nature is continuous self-reporting.

What transfers, and what doesn’t

None of these moves is specific to status pages. When a product isn’t selling, the question to ask before rebuilding it is who you are selling to, at what price, with what face. A B2B price can be designed as a filter that keeps only the segment whose problem is acute. And in developer-facing products, publishing your metrics is itself marketing.

The limits: the Sup-to-Instatus pivot worked because demand for status pages genuinely existed upmarket, the rename and price raise merely discovered it. Running the same operation in a demand-less space changes nothing. And open metrics have become a cheap-to-copy tactic, as differentiation it is now weak, and the original novelty is gone. The pivot pattern travels. The verification that demand exists on the other side starts from zero every time.