Saasmetry reads the providers you already pay — Stripe, Sentry, Vercel, your host, your database — and puts revenue, cost, uptime and deploys for each product in one place. Built for people shipping faster than they can keep an eye on what they shipped.
Free for one product and three integrations. No card.
Last 30 days · 4 products · $36,580 MRR
One control panel per SaaS — status, revenue, reliability and connected providers
Reads from 35 providers, including
Four decisions the product is built on. Each one is the reason a number on the screen above is worth trusting.
Stripe knows revenue, Sentry knows errors, Vercel knows deploys — and none of them knows which of your products it is talking about. Saasmetry asks that question once, at setup, then every figure afterwards belongs to a product.
Not estimated from usage and not typed in by hand. What a product earns, what it costs to run, and the difference — which is how a product that has been quietly losing money for three months stops being a surprise.
A dashboard that sorts by newest teaches you to read the top and stop. This one puts the loss-making product above the noisy one, so the first thing you see is the thing worth doing.
Every provider is asked for the narrowest credential it offers. Keys are encrypted with a key of your workspace’s own and never returned to the browser in full — not even to you, not even once.
The longest part is finding the API keys. Everything after that is a schedule.
A name and a domain each. Everything Saasmetry collects is attributed to one of them, so this comes first.
Paste a read-only key. Saasmetry verifies it against the provider before it stores anything, then backfills 90 days.
Which Stripe products, which repositories, which OpenRouter key. This is what makes a per-product number possible instead of one account total.
A dashboard is only worth having if you would act on it. These are the decisions that make the numbers arguable.
Every figure traces to the connection that produced it and the run that wrote it. When two providers disagree, you can see which one you are reading.
A product with no revenue provider shows no margin — not a loss. Nothing is inferred from an absence, because a guessed number is worse than a blank one.
One API key shared by three products is reported once, for the workspace. Dividing it three ways would put a number under each that nobody could defend.
When a sync fails the numbers stay and are labelled stale, with the provider’s own error. Blanking a dashboard on a network blip teaches you to distrust it.
Each one asks for the narrowest credential it offers. Where a provider has no read-only key, the connect step says so before you paste one.
Metered on products and integrations, because those are what cost Saasmetry money to store and poll.
$0/month
One product, the full picture
Most portfolios
$29/month
The whole portfolio, with the people who run it
$99/month
For an agency or a studio running many products
The ones worth answering before you paste a key into something you have not used before.
Anyone running more than one small SaaS — indie hackers, solo founders, and people shipping products faster than they can keep an eye on them. Saasmetry is the screen you open when you have four products live and no idea which of them made money last month.
Saasmetry never looks at your code, so how an app was built makes no difference — it reads the providers the app runs on. It also reads OpenRouter token spend, which is the bill AI-built products most often get surprised by: a product can look healthy on revenue and still lose money on inference.
You point each source at a product once, at setup — which Stripe products, which repositories, which OpenRouter key. Every figure afterwards belongs to a product rather than to an account, which is what makes a per-product margin possible instead of one total for everything.
Yes, and that is the screen the product exists for. Costs shows what each product earns against what it costs to run, read from each provider’s own billing API rather than estimated from usage, sorted worst margin first.
Every provider is asked for the narrowest credential it offers, and where a provider has no read-only key the connect step says so before you paste one. Keys are encrypted with a key belonging to your workspace alone and are never returned to the browser in full again.
The last good figures stay on screen and are labelled stale, with the provider’s own error attached. Blanking a dashboard on a network blip teaches you to distrust it, and a guessed number is worse than a blank one.
The free plan covers 1 product and 3 integrations with no card. Team is $29 a month for 10 products and every integration in the catalogue.
The free plan covers one product and three integrations, which is enough to find out whether the figures match what you already know.
Start free