Amplio
github.com
- Free plan
- Windows
- macOS
- Linux
- Web
- API
- Self-hosted
What Amplio is
Amplio is a free, MIT-licensed, self-hosted product analytics platform for tracking events and examining user activity. Its dashboard supports event exploration, segmentation, funnels, retention, cohort management, user lookup, saved charts, and dashboards. The project says its ingestion API follows Amplitude’s HTTP V2 contract, allowing existing SDKs and event schemas to be ported with minimal changes. Browser and Node SDKs are listed, along with the /2/httpapi and /batch ingestion endpoints. Event data is kept in ClickHouse; metadata uses Postgres or SQLite depending on the deployment. The self-hosted setup uses Docker with Caddy, while a desktop app runs the analytics stack locally without Docker. Desktop installers are listed for macOS on Apple Silicon and Intel, and Linux AppImage and deb formats. The desktop documentation describes local ClickHouse and embedded SQLite storage, with events remaining on the user’s machine. The project describes itself as early and moving fast. Its roadmap lists session replay, experimentation, marketing attribution, alerting, and warehouse sync as later modules.
Who it suits
Amplio suits teams that want product analytics on infrastructure they control, including teams looking for an open replacement for Amplitude. Its desktop app may fit users who want a local analytics stack without Docker.
Good to know, and what to watch
- MIT-licensed and listed as free.
- Includes funnels, retention, cohorts, and user lookup.
- API contract supports porting existing SDKs and schemas.
- Desktop app runs locally without Docker.
- Desktop builds are listed for macOS and Linux.
- Project describes its development status as early.
- Session replay and experimentation are later roadmap modules.
- macOS desktop builds are unsigned and trigger Gatekeeper warnings.
Plans
Every plan and priceAmplio
Open source
The verdict
Amplio offers a broad set of product analytics features for teams willing to run the stack themselves. Its early status and unsigned macOS installers are worth considering before adopting it.
What the maker publishes
- Analytics
- The dashboard includes event exploration, segmentation, funnels, retention, user lookup, cohort management, saved charts, and dashboards. source
- Compatibility
- Its ingestion API mirrors Amplitude's HTTP V2 contract, and the project says existing SDKs and event schemas can be ported with minimal changes. source
- Data control
- Amplio stores event data in ClickHouse and says self-hosted events stay on infrastructure the user controls. source
- Deployment
- The self-hosted deployment uses Docker with Caddy, while the desktop app runs the analytics stack locally without Docker. source
- Desktop data handling
- The desktop README says events stay on the user's machine and describes local ClickHouse and embedded SQLite storage. source
- Desktop platforms
- The maker lists macOS installers for Apple Silicon and Intel, plus Linux AppImage and deb installers. source
- Development status
- The README describes Amplio as early and moving fast, and its roadmap lists session replay, experimentation, marketing attribution, alerting, and warehouse sync as later modules. source
- Installer limitation
- The maker says desktop builds are unsigned, so macOS Gatekeeper warns on first open. source
- Intended users
- The project describes Amplio as an open replacement for Amplitude for teams that want to run product analytics on infrastructure they control. source
- License
- The repository describes Amplio as MIT-licensed. source
- Product
- Amplio is an open-source, self-hosted product analytics platform for tracking events and analyzing segmentation, funnels, retention, cohorts, and user activity. source
- SDKs and API
- The project lists browser and Node SDKs, plus ingestion endpoints at /2/httpapi and /batch. source
- Security
- The architecture documentation says ingestion API keys are resolved to projects and unknown keys are rejected. source
- Storage
- Amplio uses ClickHouse for events and Postgres or SQLite for metadata, depending on deployment. source
Checked against the maker's pages on 4 Oct 2026.