Skip to content

Ackee

Self-hosted, privacy-focused web analytics with no cookies.

Self-hostedNot yet verified
Report issueDemo online
MIT★ 4200

Open the official app on ackee.electerious.com

This tool is hosted by its maintainers. Click below to open ackee.electerious.com in a new tab — it's their official demo.

Browse developer tools →

What's next with Ackee?

Choose how you want to get started.

Use it free

Open the official tool or demo — no account needed.

Free

Self-host it

Run the open-source version on your own infrastructure.

Open

What is Ackee?

Ackee is a self-hosted website analytics tool designed for users prioritizing privacy and data control. It enables website owners to track traffic and generate insights without relying on third-party services, addressing concerns about user data collection and surveillance. Built on Node.js, Ackee operates entirely on the user's server, ensuring complete transparency and customization. Privacy-conscious developers, independent bloggers, and organizations handling sensitive data often use Ackee to monitor site performance while maintaining anonymity for visitors. The tool solves the problem of traditional analytics platforms that aggregate user data, offering a decentralized alternative where users retain ownership of their metrics.

How it works

Ackee is an open-source analytics platform that runs on a user's own server, providing website traffic insights without tracking individual users. Its primary purpose is to deliver privacy-first analytics by anonymizing data through a multi-step process, ensuring visitor identities remain obscured. The tool caters to individuals and organizations seeking control over their data infrastructure. By hosting Ackee locally, users avoid reliance on external services, making it ideal for projects with strict privacy requirements or compliance needs. Ackee offers domain management, allowing users to track multiple websites under a single dashboard. It provides metrics such as page views, referrers, and session durations, presented in a minimalistic interface. The tool's anonymization process removes personally identifiable information (PII) from raw data before storage, ensuring compliance with privacy regulations like GDPR.

How to use it

  1. 1Clone the Ackee repository from GitHub and install Node.js dependencies. 2. Configure domains in the settings panel and generate tracking scripts for each site. 3. Deploy the application to a server, ensuring HTTPS is enabled for secure data transmission. 4. Access the dashboard to view aggregated statistics and manage tracking codes. Practical tips include setting up a reverse proxy for the dashboard, configuring firewall rules to restrict access, and regularly updating the server to maintain security.

What it can do

  • analytics tracking

Use cases

Assumptions and limitations

Assumptions

  • source: https://github.com/electerious/Ackee
  • license: MIT — free to use
  • privacy: Self-hosted — you control your data

Limitations

  • Requires technical expertise to set up and maintain server infrastructure
  • Lacks real-time data visualization compared to commercial analytics tools
  • Limited built-in reporting features compared to platforms like Google Analytics
  • Dependent on Node.js runtime and server configuration for operation
  • Smaller community support compared to widely adopted analytics solutions

Understanding the result

Self-hosted, privacy-focused web analytics with no cookies.

Tool details

  • Clearly flagged when a network request is needed.
  • No account, no sign-up, and no tracking of your content.
  • Powered by (MIT).
Built with
(electerious/Ackee)
License
MIT
Runs locally
No — requires a network request
Verification
Not yet verified
Input
Query
Output
Text
Open-source source & license

Built with electerious/Ackee. OpenToolVault provides the discovery and browser interface while crediting the original project maintainers.

Built with
License
MIT
View source on GitHub

Open-source project

OpenToolVault is an independent directory. We are not affiliated with or endorsed by this project.

References

Frequently asked

How does Ackee ensure user privacy?

Ackee anonymizes data through a multi-step process that removes personally identifiable information (PII) from raw traffic data before storage. This includes stripping IP addresses, user agents, and referrer information, ensuring visitor identities cannot be reconstructed. All data is processed locally on the user's server, eliminating third-party data collection.

How does Ackee's architecture differ from traditional analytics tools?

Unlike cloud-based services like Google Analytics, Ackee operates as a self-hosted server application. This means data is processed and stored locally, giving users full control over their metrics. The Node.js-based architecture allows for customization but requires manual server management, contrasting with the automated infrastructure of SaaS analytics platforms.

How do I add a tracking script to my website?

After configuring domains in the Ackee dashboard, generate a tracking script snippet. Paste this code into the HTML of your website's pages, typically within the <head> or <body> section. The script collects data locally on your server, with no data transmitted to external servers. Ensure the script is correctly placed to capture all traffic.

How does Ackee compare to alternatives like Matomo or Google Analytics?

Ackee differs from Matomo (formerly Piwik) by emphasizing minimalism and privacy through its anonymization process, while Matomo offers more extensive customization options. Compared to Google Analytics, Ackee lacks real-time reporting and integration with other Google services but provides full data ownership. Both Matomo and Google Analytics operate as SaaS solutions, whereas Ackee requires self-hosting.

What should I do if the dashboard is unreachable after deployment?

Check server logs for errors in the Node.js application. Ensure the server's firewall allows traffic on the configured port (e.g., 3000). Verify that the domain's DNS settings correctly point to the server's IP address. If using a reverse proxy, confirm that it's properly configured to forward requests to Ackee's backend.

Spotted something wrong with Ackee, or want to maintain it? See how to help.