
Countly
Cloud or self-hosted app analytics, with an optional cookieless mode, open source.

Aptabase is analytics for mobile, desktop and web apps rather than websites: it records only the events an app sends, with no automatic page views. The server is open source under AGPL-3.0 and runs in the vendor’s EU or US region or on your own server; it sets no cookies and counts users with a server-side hash whose salt changes daily.
1.27 KB compressed
2.53 KB uncompressed · measured 17 Sep 2026
Aptabase has no script to paste into a page: its web SDK is the npm package @aptabase/web, which is bundled into your app. Measured: the build of package version 0.5.0.
Billed by events · checked 17 Sep 2026
Aptabase is analytics for mobile, desktop and web apps, not for websites. It records only the events your code sends, and the vendor itself says it is not meant for marketing site statistics such as page views, referrers or UTM campaigns. The web SDK targets single-page applications, where each full page reload starts a new session.
It fits developers who want counts of sessions, events, app versions, operating systems and countries without identifying users. The vendor lists SDKs for 17 platforms, one of them community-maintained, from Swift, Kotlin and Flutter to Electron, Tauri, .NET MAUI, Unity and Godot.
Aptabase is run by Technov Solutions SRL in Romania. The server is open source under AGPL-3.0, the SDKs under MIT, and the hosted service has an EU and a US region.
Sign up in the EU or US region and create an app. Its App Key, shown under Instructions in the dashboard, starts with A-EU or A-US and tells the SDK where to send data. Install the SDK for your platform, initialize it with the key and call the track function wherever you want to count something. For web apps the package is @aptabase/web.
To self-host, the vendor’s self-hosting repository provides a Docker Compose file with PostgreSQL, ClickHouse and the Aptabase app on port 8000. Change the placeholder passwords and secret first. The first account is registered in the app and activated through a link printed in the container logs.
As documented on the vendor’s own pages. “Partly” means the feature has limits or is only on some plans.
What the vendor documents. A platform that is not listed has no guide, plugin or package from the vendor.
No. According to the documentation, the SDKs set no cookies and send no device or advertising identifiers. Sessions get a random short-lived ID from the SDK, and the server derives a daily-rotated hash from the IP address and User-Agent without storing either. The vendor says no consent banner is needed; whether that holds for your app depends on the rules that apply to you.
Your analytics are paused. Aptabase charges no overage fees, emails you when you are close to the monthly limit and, once you exceed it, disables analytics until the start of the next month. Every call to the track function counts as one event.
Yes. The free plan covers up to 20,000 events a month and needs no credit card. Paid plans are billed monthly by event volume, and every plan includes unlimited apps, the live view, session timelines and CSV export.
In the region you choose: the EU, in Germany, or the US, in Virginia. The two regions run as separate deployments, and the data processing agreement lists Tinybird for event storage and Amazon Web Services for hosting in each region. Analytics data is kept for up to five years.
How each value is collected: methodology. Why tools get no overall score: our reasoning.
Same category, ordered by how many traits they share with Aptabase: cookie handling, self-hosting and open code.
Compare Aptabase with another tool →

Cloud or self-hosted app analytics, with an optional cookieless mode, open source.

Cloud app analytics, cookieless by default.