One analytics for all your sites and apps.
One line for each site, one SDK for each app. Visitors, users, heatmaps, bots and revenue from Stripe, the App Store and Google Play, for all your projects together.
Free until your first $1k MRR.
The demo runs on our own apps, with example numbers.
1Who is here
Every visitor, live on a globe.
Where people are and where they came from, the post that mentioned you and how many it sent, and each sale where its buyer is.
- 🇺🇸/download · AustinGoogle
- +$9.99AstroChart · Stripe🇦🇪
TimeLoop, mentioned · Bluesky post by @coffeefirst.bsky.social · 3 days ago
2Your users
Your users, new and returning.
Who came today, this week and this month, who came back, and each person with every visit, where it came from and what they paid.
Active people
All projects · sites and apps-
Google /pricingToday Paid €19.00
-
ChatGPT /humanize2 days ago
-
Reddit /5 days ago
One of the demo's made-up people.
3Where they click
See where they click.
Heat on a picture of each page of your site and each screen of your app, who of the people behind each click paid later, and where people who left at checkout got stuck. Off until you turn it on.
- A heatmap on the real pageOnce a day Sumly takes a picture of each page people click on, on desktop and on phone, and lays the heat over it: the count on the busiest buttons, rage and dead clicks, and how far down people get.
- The same heat on your live siteOpen on yoursite.com paints it over the page itself for 15 minutes, so you can click around in it.
- Where they got stuck before leavingSumly knows who reached checkout and did not pay. Their clicks get a heatmap of their own, and their last rage and dead clicks before they left are listed nearest the exit first, each with its replay where replay is on.
- Taps in your app, on the screen itselfIn React Native and Expo, iOS and Android the SDK counts each tap and lays the heat over a real picture of each screen, rage and dead taps too. Off by default; you turn it on in the SDK.
- Replay a visit, if you want toSession replay on your website: off until you turn it on, then by default only for visitors who agreed, with every word and input masked. Kept 30 days.
Made-up numbers, as everywhere on this page.
4What brought customers
Follow one buyer, from the first visit to the payment.
Then see what each ad, sponsor or creator cost against what its people paid.
-
7 creators · TimeLoop −88%spent €1,19514 paying · brought €148 · +€71 a month
-
TikTok ads · TimeLoop −65%spent €3344 paying · brought €118 · +€14 a month
-
Newsletter sponsor · Humanize −95%spent €2251 paying · brought €12 · +€24 a month
-
Reddit ads · Humanize −88%spent €2002 paying · brought €23 · +€24 a month
-
Pinterest ads · AstroChart −100%spent €1340 paying · brought €0
Revenue by source, in the demo → Every cost and what it returned →
5Revenue
Every way in. One number.
22 payment providers, added up after fees and refunds, in euros.
Every jump in revenue, with its reason.
Each one marked on its day with the post, thread or video that sent the crowd, the week your Google Search Console clicks fell, or the day your app entered a top chart in the App Store or Google Play, and under it what one visitor from each source brings.
What one visitor brings, by source · 90 days
-
Instagram €0.12
-
TikTok €0.11
-
Google €0.11
6Only people
Bots kept out, and blocked.
Crawlers and scrapers posing as browsers are found by their network and how they behave, and kept out of every number and your plan. Block them in one click in your Cloudflare, bunny.net or Vercel, or with nginx and Apache rules for your own server.
Proxy crawlers, caught in the act.
A scraper renting home connections and VPNs in thirty countries looks like a crowd of people. Sumly sees what a crowd never does, keeps it out of every number, and learns the networks it keeps catching. With the autopilot on, the networks and pages it keeps hitting are blocked for you in Cloudflare, bunny.net or Vercel.
- 586 new visitors in two minutes, none from a link
- Nearly each on a page of its own
- Browser time zones that are not their countries
Disguised scrapers, found by their network and behaviour
- Alibaba Cloud AS45102 · AstroChartKept out Block in Cloudflare
- DigitalOcean AS14061 · ASO.bestBlocked automatically in Vercel
- /tools/top-charts/* proxy network · HumanizeKept out Copy the nginx rule
Blocks in
Cloudflare
bunny.net
Vercel
nginx and Apache
7Apps and AI
Every sale in your pocket, the moment it happens.
Sumly for iPhone and Android, on the same account you use on the web.
- Every sale, as it happensA notice for each sale and refund, with a till sound if you like, one when visitors rush in, and a summary each day or week.
- WidgetsToday's revenue, MRR and the people on your sites, on the Home Screen and Lock Screen.
- Your team tooEveryone on your team signs in with their own account and picks their own notices.


Screens from the app with the demo's example numbers. On Google Play now, coming soon to the App Store. Your plan comes from the web, so the app sells nothing and shows no ads.
Or just ask.
In plain words, here or from ChatGPT and Claude over MCP at sumly.dev/mcp. It reads your numbers; it changes nothing.
More on MCP →The month, packed for your accountant.
On the 1st, one zip from every provider you connect, with what is still missing, such as a Stripe Tax Invoice. By mail when you say so, in English or Slovenian.
Monthly reports →Now look around.
The real product with our own apps (TimeLoop, AstroChart, Humanize, file.fast and ASO.best) and example numbers: half a year of payments and three months of visitors, rebuilt each night.
MRR, revenue, profit and customers of every project, with the days that moved them.
Three steps, no code in your checkout to start
-
1
Connect a read-only key
Stripe, Paddle, Lemon Squeezy, Polar, Creem, RevenueCat, the App Store or Google Play. Up to three years of payments are read at once.
-
2
Add one line to your site
The script goes in your page head. Visitors start counting, with where they came from, and your store buttons carry the visit to your app.
-
3
See which visits pay
Stripe Payment Links, pricing tables, Polar links and Paddle buttons carry the visitor by themselves. Your own checkout takes one line: pass the visitor id in its metadata, and each payment counts for the source of that person's first visit.
Your keys stay yours
Read-only keys wherever the provider has them, encrypted at rest with AES-256, used only on the server and never sent back to a browser. Disconnect, and the key and everything read with it are deleted.
No IP addresses
Country and city come from the request, the address is never kept; a tap on an App Store button keeps only a hash of it, for an hour. In the EU and UK no cookie until the visitor agrees, and raw visits go after 25 months.
A team, with limits
Invite people as viewers, members, admins or your accountant, each to whole companies or to the projects they work on.
Several businesses in one account →Revenue tools and analytics tools, in one
Subscription dashboards do not count visitors, and analytics tools do not read your billing. Where the others are ahead is here too. Checked on their own pages, 3 November 2026.
| Sumly | DataFast | ChartMogul | Plausible | OpenPanel | |
|---|---|---|---|---|---|
| Subscription metrics from your billing | — | — | — | ||
| Visitor analytics | — | ||||
| Revenue by traffic source | partly | partly | partly | ||
| Who is likely to pay, from your own payers | partly | — | — | ||
| Costs and ROI by source, campaign and creator | partly | — | — | — | |
| Brand mentions marked on the traffic chart | partly | — | — | — | |
| App users met with their RevenueCat purchases | — | — | — | — | |
| App Store and Google Play read directly | — | — | — | ||
| RevenueCat, Lemon Squeezy, Polar and Creem | partly | — | — | — | |
| Bots posing as browsers: found, shown apart, blocked where your site is served | — | — | partly | — | |
| Mobile app for iOS and Android | Android, iPhone soon | — | — | ||
| Open source, can be self-hosted | — | — | — |
Partly: ChartMogul through attributes you send it, and a likelihood on sales leads without saying what it is built from; Plausible on its Business plan, and it leaves out data-centre traffic without showing it or blocking it; OpenPanel from revenue events your own code sends; DataFast with Lemon Squeezy and Polar but not RevenueCat or Creem, mentions from X and Reddit, and Meta Ads as its only cost. A dash: not offered, or not found on their own pages. Details and sources on each comparison page.
Black Friday: Sumly for life, one payment from $79, until 1 December →
Simple prices
Every plan reads every provider. Free holds 1 project until your first $1k MRR. Each paid plan is free for 14 days with no card, and the first 50 who pay keep a third off for as long as they stay.
- Every provider, and which visit paid
- Heatmaps, session replays and bot blocking
- MCP in Claude and ChatGPT, and the app
- Visits kept for 3 months, you alone
No card. Growth for the first 14 days, then Free if it fits.
Founding 50: $65 a month, for life
Everything in Free, plus:
- Unlimited projects
- 50,000 visits a month
- Unlimited MRR
- You and 2 more in the team
- Visits kept for 25 months
- 1,000 session replays a month
- Ask in Sumly, 50 questions a month
- Weekly report and jump marks
$0 due today. No card required.
Founding 50: $1210 a month, for life
Everything in Free, plus:
- Unlimited projects
- 500,000 visits a month, or up to 5 million as you grow
- Unlimited MRR
- Your whole team, each limited to their projects
- Visits kept for 25 months
- 5,000 session replays a month
- Ask in Sumly, 300 questions a month
- Weekly report and jump marks
$0 due today. No card required.
Visits are page and screen views; clicks and heatmaps never count. Session replays have their own allowance: 1,000 a month on Starter, 5,000 on Growth. Past 50,000 visits on Starter there is no extra charge: visits keep counting up to 60,000, then new ones are not counted until the 1st or an upgrade. Growth at $19 a month covers 500,000.
Free is for good while a project is small, and the workspace is never deleted while it stays on Free. After the trial, a bigger workspace that does not pay becomes read-only, and its data is kept for 30 days. To look around first, open the demo; it needs no account.
Prices in US dollars, before tax. More than 5 million visits a month? Write to us.
Moving from DataFast, Plausible or OpenPanel? Bring your history.
Questions
Which payment providers does Sumly read?
22 payment providers: Stripe, Paddle Billing, Lemon Squeezy, Polar, Creem, RevenueCat, the App Store and Google Play directly, and 14 more, such as Shopify, WooCommerce, PayPal, Gumroad and Adapty. A project can use several at once, for example Stripe on the web and RevenueCat in its app, and Sumly adds them up and shows what each brings.
Can Sumly change or move my money?
No. It asks for read-only keys wherever a provider offers them, keeps them encrypted, and never writes to your payment accounts.
How are visitors counted?
A small script on your site. It keeps a first-party id and takes country and city from the request. In apps, the Sumly SDK counts screens and taps, and payments come straight from the stores or RevenueCat.
Switching? Can I bring my history from DataFast, Plausible or OpenPanel?
Yes. Sumly imports DataFast with its API key, Plausible from its export zip or Stats API, and OpenPanel with a read-only client. It keeps only the days before its own script, imported visits never count toward your plan, and each import can be taken back. Import your history →
What will it cost?
Nothing until your first $1k MRR. Free holds 1 project and you alone, up to 10,000 visits a month in all, with nearly everything else in. Visits and their detail are kept 3 months on Free; payments and revenue are kept for good, and the workspace is never deleted while it stays on Free. Past that, Starter is $9 a month with unlimited projects, and Growth follows your traffic up to $99 a month for five million visits. Both are free for 14 days with no card, and the first 50 who pay keep a third off for life. A bigger workspace that does not pay after the trial becomes read-only, and its data is kept for 30 days.
How does it guess who is likely to pay?
From your own payers. Sumly looks at the project's visitors of the last 90 days and which of them paid. A visitor's chance to pay comes from how often people like them paid: the same device, system, browser, country and source, and as many days of visits. Their estimated value is that chance times what your payers paid on average. Until 5 payers are tied to visits, there is no estimate at all, rather than a guess from a site average. How the estimate works →
Try it with your own projects
Sign in with Google or a code by e-mail and connect your first project. The first 14 days of a paid plan are free, with no card.
Start freeOr look around first: open the live demo.