Proof points
A proof point is a figure read from a provider and shown on the listing. The founder does not type it in. The listing says verified by that provider, with the provider's logo.
MRR is one proof point, read from a billing provider. Uptime is another, read from Better Stack, CloudWatch, or Google Cloud Monitoring. Traffic is active users from Google Analytics. Each one is a provider, a field, a cadence, and a choice of exact, band, or do not show.
Proof points are separate from coupons. Publishing a coupon does not reveal a proof point. Connecting a proof point does not publish a coupon. Coupon and proof keys are stored separately, even when you paste the same string twice.
Other people see proof points on a public https listing that is not hidden. Ownership verification is optional and does not gate proof visibility.
Free for now
On submit or under Basic info, founders can mark a product free for now. When that flag is on and the MRR reading is 0, the public listing shows Free for now instead of $0 (exact) or 0-1k (band). The stored reading stays 0. Clear the flag when the product starts charging; readings above zero always show the normal value even if the flag is still on.
Exact value, a band, or do not show
For each proof point you turn on, you choose:
- Exact. The public listing and agents receive the figure from the last read.
- Band. They receive a range and a color. The stored reading is still the exact value. The number, and the size of the change, are not in the public page or the agent payload.
- Do not show. The field stays connected and keeps syncing, but it is omitted from the public listing and from what seekers and agents receive. Use this to hide one field while showing others from the same provider.
You still see the latest number on your own product page, including when the public choice is a band or do not show.
MRR bands, in the currency of that reading, are 0–1k, 1k–10k, 10k–50k, 50k–100k, 100k–200k, then bands 100k wide through 1M, then 1M+. If the largest total is not US dollars, the band is labeled with that currency. Dealpuffin does not convert it.
Uptime bands are the same for every observability provider: under 90% (red), 90–99% (amber), 99–99.9% (green), and 99.9% and above (green). Gray is the color when a proof point is not configured. It is not an uptime band. Traffic bands are label-only ranges (0–1k through 1M+) with no color scale. Band colors are for percentage fields such as uptime.
You set the order. A product card in the catalog shows the first three. The product page shows every proof point as a card: the value or band, the provider, when it last synced, how often it syncs, and whether the reading moved up, down, stayed flat, or is the first one.
Where MRR comes from
You choose daily, weekly, or monthly. The first read happens when you connect the key. After that, an hourly job reads the connections that are due. Sync now on the product page reads immediately.
If a provider returns more records than one sync can read, that sync saves nothing and leaves the previous reading in place. A partial total is not stored as MRR.
Stripe
MRR is the sum of active subscription prices, normalized to one month, before discounts. Metered prices are skipped. A quantity of zero adds nothing. If the account has more than one currency, the total is the currency that adds up to the most.
The read uses a restricted key with read on Subscriptions. See Connect Stripe.
Paddle
MRR is the sum of active subscription items with a recurring billing cycle, normalized to one month. One-off items on a subscription are skipped. Multi-currency accounts use the currency that adds up to the most.
The read uses a Paddle API key with subscription.read. See Connect Paddle.
Polar
MRR is the sum of active subscriptions, normalized to one month from each subscription’s amount and recurring interval. Multi-currency accounts use the currency that adds up to the most.
The read uses an organization access token with subscriptions:read. See Connect Polar.
RevenueCat
MRR is RevenueCat’s project overview metric (mrr), not a recalculation from raw receipts. Enter a project id when the key can see more than one project.
The read uses a V2 secret API key with charts_metrics:overview:read. See Connect RevenueCat.
Lemon Squeezy
MRR is the sum of active subscription prices for one store, normalized to one month. Enter a store id when the key can see more than one store.
Dodo Payments
MRR is the sum of active subscriptions’ recurring pre-tax amounts, normalized to one month from each payment frequency. Multi-currency accounts use the currency that adds up to the most.
Where uptime comes from
Uptime is a percentage, 0–100, for the 30 days ending on the day Dealpuffin reads it. An empty series saves nothing and leaves the previous reading in place. You choose daily, weekly, or monthly. The first read happens when you connect.
The same bands apply whichever provider you connect. Connecting uptime does not publish a coupon, and publishing a coupon does not reveal the reading.
Better Stack
- Open API tokens in Better Stack.
- Create a token named Dealpuffin and set the permission to Read-only.
- Copy the token once. Do not paste a Read & write token. Dealpuffin only reads monitors and availability, and the token string does not say which permission it has.
- Paste it on the product page. If more than one monitor uses this product’s host, enter that monitor’s id. One matching monitor needs no id.
A global token or a team Incidents token both work. The reading is that monitor’s availability.
CloudWatch
- In AWS, open IAM, then Users.
- Create a user named Dealpuffin. Do not enable console access.
- Add an inline policy whose only actions are
cloudwatch:GetMetricDataandsynthetics:DescribeCanaries. Do not attach the managed CloudWatchReadOnlyAccess policy. It also reads logs, X-Ray, RUM, and SNS. - Open Security credentials, then Create access key, and choose the option for a third-party service. Copy the access key id and the secret once. The access key id starts with
AKIA. Do not paste a root key or a role session key. - Enter the region the canary runs in. If that region has more than one canary, enter the canary name. CloudWatch does not return the URL the canary calls.
The reading is that canary’s SuccessPercent.
Google Cloud Monitoring
Cloud Monitoring does not accept an API key.
- In Google Cloud, open IAM, then Service accounts.
- Create a service account named Dealpuffin. Do not grant a role on that screen.
- Open Keys, Add key, JSON, and download the file. That file is a private key. Paste it on the product page. Dealpuffin encrypts it.
- Grant that service account only Monitoring Viewer (
roles/monitoring.viewer). Leave Editor and Owner off. - Enable the Cloud Monitoring API.
- If more than one uptime check uses this product’s host, enter that check’s id. One matching check needs no id.
Dealpuffin requests only the monitoring.read scope. The reading is the share of passed checks.
Where traffic comes from
Traffic is Google Analytics 4 active users for the rolling 30 days ending on the day Dealpuffin reads it (UTC calendar dates). A successful read of zero users is stored as zero. You choose daily, weekly, or monthly. The first read happens when you connect.
Traffic bands are label-only ranges: 0–1k, 1k–10k, 10k–50k, 50k–100k, 100k–500k, 500k–1M, and 1M+. They have no color. Connecting traffic does not publish a coupon, and publishing a coupon does not reveal the reading.
Google Analytics
Google Analytics does not accept an API key for this reading.
- In Google Cloud, open IAM, then Service accounts.
- Create a service account named Dealpuffin. Do not grant a role on that screen.
- Open Keys, Add key, JSON, and download the file. That file is a private key. Paste it on the product page. Dealpuffin encrypts it. The JSON includes
client_email. - In the same GCP project as that service account, enable the Google Analytics Data API and the Google Analytics Admin API. The Admin API is only used when you omit the property id.
- In Google Analytics, open Admin, then Property access management. Add the service account’s
client_emailas Viewer. Leave Editor and Admin off. - The property id is under Admin → Property settings (a number such as
123456789). Enter it when the service account can see more than one property. One accessible property needs no id.
Dealpuffin requests only the analytics.readonly scope. Access is granted on the GA4 property, not with a GCP project role.
Frequently asked questions
Does a listing show MRR automatically?
No. You connect a billing provider as a proof-point provider and choose MRR. Until you do, the listing has no revenue line.
Can I show a range instead of the exact number?
Yes. Choose band. Seekers and agents see the range, not the figure. Exact shows the number. Do not show keeps the field connected without putting it on the listing.
Can I hide one field from a provider that has several?
Yes. Choose do not show for that field. Other fields from the same provider can still use exact or band.
Do I type the number in?
No. The figure is a reading. A band is computed from that reading.
What proof points can I connect?
MRR from Stripe, Paddle, Polar, RevenueCat, Lemon Squeezy, or Dodo Payments; uptime from Better Stack, CloudWatch, or Google Cloud Monitoring; and traffic from Google Analytics. Each proof point is a provider you connect, not a number you type.