Is HitKeep open source?
Yes. HitKeep’s application source is MIT licensed and available on GitHub, so engineering, security, and procurement teams can inspect the product foundation before running it.
Open-Source Sovereign Web Analytics
HitKeep is open-source sovereign web analytics for teams that want useful reporting without handing the whole analytics workflow to an ad-tech platform, hosted-only vendor, or opaque assistant integration. You can self-host the same product as one binary, or start in managed EU/US cloud when you want HitKeep to run the operational layer.
What sovereign analytics means
Section titled “What sovereign analytics means”Sovereign analytics means the deployment model, data location, access model, and export path stay explicit. In HitKeep, that means self-hosting is a first-class path, managed cloud has an EU or US region choice, the public tracker is cookie-free by default, and exports remain available in open formats.
It does not mean compliance is automatic. HitKeep reduces the tracking surface and keeps deployment choices clear, but your legal basis, notices, retention policy, and transfer analysis still depend on your organization and jurisdiction.
Who it is for
Section titled “Who it is for”Use this path when you need:
- open-source privacy-first web analytics that security and engineering teams can inspect
- self-hosted analytics with no required PostgreSQL, ClickHouse, Redis, Kafka, or hosted analytics service
- managed EU or US cloud analytics with a visible region choice
- cookie-free pageviews, automatic events, goals, funnels, ecommerce, UTM reporting, and scheduled reports
- Google Search Console aggregate import for mapped site properties
- AI visibility analytics for crawler fetches and AI-referred visits when you wire the needed signals
- governed analytics for AI assistants through read-only MCP and scoped API client tokens
- open exports for migration, audit, archive, or internal analysis
Deployment choices
Section titled “Deployment choices”Use single-binary self-hosted analytics when direct control over the runtime, network policy, backup process, and data directory is the deciding factor. HitKeep keeps the database and internal queue embedded in the same Go process.
Use EU or US cloud analytics when the first blocker is operations. HitKeep Cloud handles updates, backups, SMTP, monitoring, and day-two work while keeping the same dashboard, API, MCP option, and export story.
Privacy defaults
Section titled “Privacy defaults”The public tracker is cookie-free by default and supports Do Not Track behavior. Automatic events record interaction types such as outbound clicks, file downloads, and form submissions without storing form field values.
Read the privacy-first web analytics guide, digital sovereignty guide, and PECR and ePrivacy guide before treating any analytics setup as complete.
AI assistant access
Section titled “AI assistant access”HitKeep keeps human dashboards and assistant access in the same permission model. The optional analytics for AI assistants with MCP route accepts scoped API client bearer tokens, does not accept dashboard cookies, and exposes read-only aggregate analytics.
Use MCP when an approved assistant or internal reporting tool needs to answer traffic, event, ecommerce, AI visibility, Search Console, or docs questions. Use open exports and takeout when the job needs portable files instead of live assistant queries.
Can I self-host HitKeep?
Yes. HitKeep can run as one Go binary with embedded DuckDB and embedded NSQ. Core analytics do not require PostgreSQL, ClickHouse, Redis, Kafka, or a separate queue.
Does HitKeep use cookies?
HitKeep’s public tracker is cookie-free by default. It uses sessionStorage for an opaque session tuple, so PECR and ePrivacy analysis can still depend on your jurisdiction and consent approach.
Can AI assistants query HitKeep analytics?
Yes, when MCP is enabled and an approved assistant uses a scoped API client bearer token. The v1 MCP surface is read-only and aggregate-only.
What makes HitKeep sovereign analytics?
HitKeep gives you control over deployment, region, retention, exports, and assistant access. You can self-host it, choose managed EU or US cloud, and keep analytics portable through open exports.