Comparison

An open-source alternative to Google Analytics

Most people leaving Google Analytics are not chasing a feature. They want data they own, a tool they can understand, and one fewer consent problem. Here is what that move actually involves, including the parts that are worse.

Checked August 2026Written to be fair
What Google Analytics is

Google Analytics, in its own terms

Google Analytics is the default web analytics platform, free at the tier almost everyone uses, deeply integrated with Google's advertising products, and processed on Google's infrastructure. Its scale and its integrations are real advantages, and no self-hosted tool replaces the advertising side of it.

Checked against Widely documented; verify current terms with Google directly in august 2026. Products change; verify anything you are deciding on.

Side by side

Where they actually differ

 FalorbGoogle Analytics
Where data livesYour servers, your databaseGoogle's infrastructure
LicenceMIT, readable and forkableProprietary
CostFree; you pay for a serverFree at the common tier
Ad platform integrationNoneDeep, and a real reason to stay
Raw event dataIn your own tables, queryableVia export, on their terms
Unit of analysisThe person, across every propertyEvents and sessions per property
Learning curveSmall; far fewer conceptsSubstantial
The honest answer

Which one you should actually use

Choose Google Analytics if
  • You buy Google ads and need conversion data flowing back into them.
  • Your reporting, attribution or agency workflow is built on GA already.
  • Nobody on the team can take on running a database.
  • You need the integrations, not the analytics.
Choose Falorb if
  • You want the raw data in your own database, permanently.
  • You run several sites and want one audience across them.
  • You want a tool a new team member can understand the same afternoon.
  • You would rather not send your visitors' behaviour to an ad company.
What it looks like

The Falorb side, in the real interface

The Falorb portfolio dashboard: headline figures across five properties above a ranked list, each site with its own sparkline and period-over-period change.The Falorb portfolio dashboard: headline figures across five properties above a ranked list, each site with its own sparkline and period-over-period change.
Every property on the first screen, with one identity graph underneath
Questions

vs Google Analytics: the usual questions

Can I run both during a migration?

Yes, and it is the sensible way to do it. Both scripts can sit on the page together while you build confidence that the numbers line up. Expect them to disagree: different bot filtering, different session definitions and different consent handling mean two analytics tools essentially never report the same figure.

Will my historical Google Analytics data come across?

No. Falorb starts counting when you install it. You can export your Google Analytics history for your own records, but there is no import that would make it comparable, because the underlying definitions differ. Running both in parallel for a period is the practical way to bridge it.

Do I still need a cookie banner?

That depends on your jurisdiction and how you configure things, and it is not a question a vendor should answer for you. What is true technically: Falorb sets no third-party cookies, stores no raw IP addresses, and has a cookieless mode that persists nothing on the device at all.

The fastest way to decide is to run it

Clone the repository, bring the stack up with Docker Compose and paste one script tag. Ten minutes, and no account anywhere.