OwnlyticsDo you need your own analytics server? Probably not
No, you do not need your own server to own your analytics. A Cloudflare Worker with a D1 database in your account gives you the ownership without the machine, and a hosted plan gives you the convenience without either. Whether you want any of that at all depends on a short list of questions.
Fig.Illustrative: a $30/month tool over 36 months against Ownlytics pricing. Check each vendor’s current price.
What does "own your analytics" actually mean?
People bundle several different wants into one phrase. Pull them apart first:
- Data location. Whose account holds the database?
- Data control. Who can read it, and for what?
- Cost shape. Subscription, or a payment you make once?
- Effort. Who updates it and fixes it when something breaks?
- Independence. Does it keep working if the vendor disappears?
A dedicated server answers the first, second and fifth well and the fourth badly. That is why it is the heaviest option and the one most small teams should skip.
The four realistic setups
- A VPS or home server running an open analytics app. Maximum control, maximum upkeep. You handle the operating system, the database, backups and security patches.
- Serverless in your own cloud account. The app runs as code the platform executes on demand. This is how Ownlytics self-hosted works: a Worker and a D1 database in your Cloudflare account. Our post on how this works on Cloudflare Workers covers the moving parts.
- A hosted plan. The vendor runs everything. Ownlytics Hosted runs on Supabase, from $9 a month for 50,000 events or $19 a month for 250,000, with unlimited websites and nothing to install or update.
- No dedicated analytics at all. Rely on what your payment provider and your host already show you.
A checklist you can run in five minutes
Answer yes or no. Count the yeses in each block.
Lean toward serverless self-hosting if:
- You are comfortable running one terminal command, and Node.js 22 or newer is on your machine.
- You already have, or are happy to create, a Cloudflare account.
- You want the data in an account you control.
- You dislike another monthly subscription.
Lean toward hosted if:
- You do not want to touch a terminal or think about updates.
- You want setup done for you and a sign-in link by email.
- Your volume sits comfortably under 50,000 or 250,000 events a month.
Lean toward a server you run yourself if:
- You already operate servers for other reasons, and one more service costs you nothing extra.
- You have a policy that requires infrastructure in a specific place.
Lean toward no dedicated analytics if:
- You have no traffic to speak of, and your payment dashboard answers every question you have.
- You are not going to look at the numbers.
If you would not look at it weekly, the cheapest setup is none. If you would, avoid the heaviest one.
Example (made-up numbers for illustration)
Two founders, both selling a small product.
Founder A has a day job, one site, and about 300 visits a day. She wants to know which posts lead to sales and does not want a new monthly bill. She is fine with a terminal. She picks serverless self-hosting: one payment, free Cloudflare plan, one update command now and then.
Founder B runs three client sites and hates maintenance. He wants "it works, send me the link." He picks hosted, because an hour of his time per update would cost more than $9.
Neither of them needed a server, and neither choice is wrong.
Fig.What you get on your own Cloudflare account. Sample data, not a real site.
What you give up with each option
Honest limits, because every setup has them:
- Serverless self-hosted: you depend on your Cloudflare plan limits, and the update command is your responsibility. Our Cloudflare free plan docs list the numbers at the time of writing, and you should check Cloudflare's current limits.
- Hosted: plans have an event allowance, and you rely on us to run the service. Going over does not break tracking or lose data, but you will be asked to move up a plan if it keeps happening.
- Your own server: time. The cost is rarely money. It is the evening you spend when a disk fills up.
- No analytics: you will not know which source earned a sale, and that gets expensive in guesses.
When you should not bother with any of this
If you have not published anything yet, you do not need analytics. Ship first. Add a tracker the week you have something worth measuring. You can also change your mind later: a self-hosted install can be removed, and hosted plans can be cancelled at any time, with data kept for 30 days after the subscription ends.
If you are comparing categories, the hosted docs show how hosted differs from self-hosted side by side, and one-time vs monthly analytics cost over three years puts numbers on the money side.
At a glance
| Setup | Who runs it | Where the data lives | Effort |
|---|---|---|---|
| Your own server | You | Your machine | High |
| Serverless on Cloudflare | You (light touch) | Your Cloudflare account | Low |
| Hosted | The vendor | Vendor's database | None |
| No dedicated analytics | Nobody | Your payment provider | None |
If you want to see what the dashboard looks like before choosing, try the live demo.
FAQ
Do I need a server to run self-hosted analytics?
Not with Ownlytics. It runs as a Cloudflare Worker with a D1 database in your own account, so there is no server for you to maintain.
Is a hosted plan "owning" my data?
The data sits with the vendor, so ownership in the strict sense is different. Ownlytics Hosted uses a shared Supabase database with per-user access checks, and we say we do not sell or share your data. Read the hosted terms and privacy page and decide if that is enough for you.
Can I switch from hosted to self-hosted later?
Both run the Ownlytics dashboard, but check the current docs or ask us how to move existing data before you commit. Hosted data is kept for 30 days after a subscription ends, and you can ask for an export in that window.
What if I just want to know where my sales come from?
You can start with the question rather than the infrastructure. Our guide to revenue attribution explains what a sale needs to be credited to a source.