Connect Your app to Saasmetry

A JSON endpoint of your own — the user count and any other figure only your database knows.

What Saasmetry reads

Refreshed every 15 min. Read-only throughout: Saasmetry never writes to Your app.

Your app is self-hosted, so the credential is created in your own instance rather than on a vendor dashboard.

Expose a JSON endpoint on your own app — a metrics or internal admin route. Any shape will do.
Point Saasmetry at its URL and write one mapping per figure, as target=path: users=data.active_users. The targets are users, customers, mrr, mrr_minor, arpu, arpu_minor, spend and spend_minor.
If the endpoint needs a key, paste it and set the header name if it is not Authorization. If it needs none, paste none.

Only GET is ever sent, and only to the address you give. Nothing is written back to your app.
Money is the trap: mrr expects major units (1234.56) and mrr_minor expects minor (123456). Most apps store cents, so mrr_minor is usually the right one — mapping the wrong one is off by a hundred and looks plausible. spend and spend_minor follow the same rule.
spend is how a product hosted somewhere Saasmetry has no adapter for still reaches the Costs page. Post your AWS, Render or Fly bill from a cron job and map it — spend=billing.usd — and margin works the same as it does for a provider that reports its own billing.
One endpoint can serve a whole portfolio. Return an object keyed per product and put each product's key in its data sources; the mapped paths are then read inside that key.
A path that holds no number is reported as a warning naming the path, not as a zero — a response that changed shape should not look like a product with no users.

Saasmetry encrypts the credential and only sends GET requests to the endpoint you configure.

Free plan, no card: one product and two integrations.