Can I keep my data in my own cloud account with Tally?

No. Tally is hosted: your visits and payments are stored on servers we rent and run in the United States. The privacy notice lists what is kept and for how long.

Which payments does Tally read that DataBull doesn't name?

Paddle and Lemon Squeezy. Both connect with an API key; Paddle sales link by the visitor's id in Paddle.js customData, Lemon Squeezy's by checkout custom data, and either by the buyer's email.

Does Tally send alerts to Telegram?

Yes, and to email, Slack, Discord or any webhook. Every sale and refund can alert as it's linked, with its credited source; spikes, drops and digests can go out too.

Compare · as of November 2026

Tally vs DataBull

DataBull sells a one-time licence that runs on your own Cloudflare account, with a hosted beta beside it. Tally is hosted, reads Paddle and Lemon Squeezy as well as Stripe and Polar, and shows the evidence behind every sale it links.

Start for free

14 days free, no card needed.

01In short

If you want to pay once and keep the data in your own Cloudflare account, DataBull is built for that, and it also reads Dodo Payments and Creem. If you sell through Paddle or Lemon Squeezy, want alerts in more places than Telegram, or want each sale's receipt and a coverage figure with its fixes, Tally fits better. Both choose cookies per site, and both have an MCP server and a CLI.

02Side by side

	DataBull	Tally
Price	Self-hosted is $49 once, with lifetime updates and unlimited websites and events. Hosted (beta) is $9/month for 50,000 events and $19/month for 250,000. [1][2]	From $9 a month for 10k events to $169 a month for 10M, every site included. A year costs 9 months.
Trial	No free trial is stated; self-hosted sales are final. [1]	14 days free, no card needed.
Where it runs	Self-hosted runs as a Worker with a D1 database on your own Cloudflare account; hosted dashboards each get a database on DataBull's Cloudflare account. [1][3]	Hosted by us, on servers we rent and run in the United States.
Source code	Not open source; the source code isn't included. [1]	Not open source either.
Payment providers	Stripe, Polar, Dodo Payments and Creem, with others through a Payments API. [1]	Stripe, Paddle, Lemon Squeezy and Polar, each connected with a key you create.
Cookies	Chosen per website: first-party cookies, fully cookieless with a daily-rotating salted hash, or cookieless until the banner reports consent. [1]	The same three choices per site: cookie, cookieless, or consent-first.
Alerts	Telegram alerts for each sale with its source, refunds, traffic spikes and a daily digest. [1]	Sales, refunds, spikes and drops, and daily or weekly digests, by email, Slack, Discord, Telegram or webhook.
Assistants and the command line	A built-in MCP server with read-only keys stored as a hash, and a CLI with JSON output. [4][1]	An MCP server, a command line and a REST API, with keys shown once.
Reading and goals	Goals and funnels that end at the payment; scroll depth and reading time per page, buyers compared with everyone else. [1]	Goals and funnels with the revenue of converting visitors; engaged time and scroll depth per page, buyers against everyone else.
After you stop paying	Hosted data is kept for 30 days after a subscription ends, then deleted; an export can be requested. [3]	Tracking stops 7 days after a paid plan ends; what was recorded stays in your account.

03Where DataBull is better

A one-time $49 licence with lifetime updates: no subscription if you self-host. [1]
Self-hosted, the data stays in your own Cloudflare account. [1]
It reads Dodo Payments and Creem, which Tally doesn't, and other providers through its Payments API. [1]
Its hosted plans count up to 250,000 events for $19/month. [1]
It imports your Plausible history into the dashboard. [1]

04What Tally does differently

Paddle and Lemon Squeezy are read as well as Stripe and Polar, with refunds, and chargebacks where the provider reports them.
Every sale has a receipt with the method that linked it and how sure that is; a sale nothing links says so.
Coverage shows the share of revenue linked to a visitor and the code that fixes the rest.
Session replay and heatmaps, and Labs: your visitors as an ecosystem and a river from first source to sale.
Nothing to install or upgrade: one tag, and a key for each provider.

05Switching from DataBull

Replace DataBull's tag with Tally's in the head of every page, and connect your payment provider with a key; its past 365 days come in.
If your checkout passes DataBull's visitor id, pass tally_visitor_id from the _tally_vid cookie instead; the Coverage page has the snippet for Node, Next.js, Python, Ruby and PHP.

06Questions

Can I keep my data in my own cloud account with Tally?
No. Tally is hosted: your visits and payments are stored on servers we rent and run in the United States. The privacy notice lists what is kept and for how long.
Which payments does Tally read that DataBull doesn't name?
Paddle and Lemon Squeezy. Both connect with an API key; Paddle sales link by the visitor's id in Paddle.js customData, Lemon Squeezy's by checkout custom data, and either by the buyer's email.
Does Tally send alerts to Telegram?
Yes, and to email, Slack, Discord or any webhook. Every sale and refund can alert as it's linked, with its credited source; spikes, drops and digests can go out too.

07Sources

Each statement about DataBull comes from DataBull's own pages, read on November 9, 2026. Products change: check theirs before you decide.

DataBull: home page and pricingdatabull.app
DataBull Hosted (beta)databull.app
DataBull docs: hosteddatabull.app
DataBull docs: MCPdatabull.app