Our take
Activeregular commits- Activity
- 38
- Community
- 43
- Issues
- 47
- Pull requests
- 66
+11 stars in the last 10 days
Aptabase is an actively maintained, privacy-focused app analytics option with broad SDK coverage, though self-hosting comes with AGPL obligations and ongoing maintenance.
Good fit if
- You need analytics for a mobile, desktop or web app and want to minimize collected usage data.
- Your app uses one of the listed SDK platforms, or you are prepared to build your own SDK.
- You can use the managed cloud service or take responsibility for maintaining a self-hosted deployment.
Look elsewhere if
- Your project needs a license without the AGPL-3.0 obligations for the server code.
- You need an SDK for a platform that is not listed and cannot build one yourself.
- You need a recent release as a key adoption signal: the repository has had no release in the past year, despite ongoing commits and merged pull requests.
All health signals
| Last commit | 2026-10-10 (4 days ago) |
|---|---|
| Commits, last 90 days | 21 |
| Releases, last 12 months | 0 |
| Contributors | 12 (top contributor: 70% of commits) |
| Issues closed, last 90 days | 1 |
| Pull requests merged, last 90 days | 11 (typically merged in 0 days) |
| Project age | 3 years |
Checked on 2026-10-15 with the GitHub API.
Overview
Aptabase is an open-source analytics platform for mobile, desktop and web apps. It offers an alternative to Firebase and Google Analytics for teams that want to understand app usage while collecting minimal data and avoiding unique identifiers.
The project combines a dashboard with SDKs for platforms including Swift, Android, React Native, Flutter, Electron, Tauri and web apps. Teams can use Aptabase's managed cloud service or host the server themselves.
Key Features
- Tracks app usage through sessions and other essential metrics, with a built-in dashboard.
- Collects minimal usage data and does not use unique identifiers, according to the project.
- Provides SDKs for mobile, desktop and web frameworks, including Swift, Kotlin, Flutter, React Native and Electron.
- Supports both managed cloud use and self-hosting.
- Publishes the server and SDK source code for inspection and contribution.
- Allows teams to build their own SDK for platforms not listed by the project.
Use Cases
- A mobile app team wants usage analytics without adopting Firebase or Google Analytics.
- A desktop app developer using Electron or Tauri needs a shared analytics service across app sessions.
- A team using Flutter, React Native or native iOS and Android apps wants SDKs for its client platforms.
- An organization that wants to operate its own analytics service can self-host Aptabase instead of using the managed cloud.
What you need
Detected in the repository
- C# (main language on GitHub)
- A Dockerfile, so it can run in a container; a Compose file sets up the related services
- A test suite and automated checks on GitHub Actions
License in plain words
AGPL-3.0network copyleft
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license notice
- Share your changes: yes, the full source, also when people only use it over a network (e.g. as a hosted service)
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Choose the managed cloud service for the quickest setup, or follow the self-hosting guide to run Aptabase yourself. Select an SDK from the repository README for integration details.
Alternatives
- vince: Vince focuses on self-hosted website analytics, while Aptabase tracks product usage in mobile, desktop, and web apps through app-focused SDKs.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| aptabase | C# | AGPL-3.0 | 1.8k | Active |
| vince | Go | AGPL-3.0 | 2k | Inactive |
Considerations
The repository is active, with regular recent commits and merged pull requests, and contributions come from multiple people rather than being concentrated in one contributor. However, it has had no release in the past year, and only one issue was closed in the measured recent period, so teams should review the project's current release and support expectations before adopting it. Self-hosting requires taking responsibility for maintenance and updates. The server is licensed under AGPL-3.0, which requires sharing changes to the code; the README states that the SDKs use MIT licenses.
Found this useful?
Share it with someone who would like aptabase.