EU-Hosted Web Analytics with an Open-Source Exit Path
Section titled “EU-Hosted Web Analytics with an Open-Source Exit Path”HitKeep EU Cloud runs managed web analytics in Frankfurt for teams that want regional hosting without operating the instance themselves. The US region remains available, but the product, export model, and self-hosted build do not change with the region.
Best fit
Section titled “Best fit”Choose HitKeep Cloud when you want:
- a self-serve production pilot
- explicit EU or US region choice
- managed updates, backups, and mail delivery
- Google, GitHub, and Microsoft sign-in for accounts and invitations
- the same dashboard, API, automatic events, Search Console import, Opportunity recommendations, AI visibility, MCP option, and exports as self-hosted
- city, provider, and ASN audience context from derived IP metadata, without storing raw visitor IP addresses
- less operational work before the first report exists
Choose self-hosting instead when your organization must own the server, data directory, backup process, and network boundary directly.
Region choice
Section titled “Region choice”- EU Cloud:
cloud.hitkeep.eu, hosted in Frankfurt, Germany. - US Cloud:
cloud.hitkeep.com, hosted in Virginia, United States.
Pick the region that matches your users, contracts, and privacy review. Region choice is a deployment decision, not a different product edition.
What cloud handles
Section titled “What cloud handles”HitKeep Cloud removes common day-two tasks:
- operating the service runtime
- upgrades and patching
- backups in the selected region
- mail transport for reports and account flows
- infrastructure-level monitoring
You still keep the export path. HitKeep data can be exported in JSON, CSV, Parquet, NDJSON, and XLSX where supported.
Cloud facts
Section titled “Cloud facts”Use Facts and Limits for canonical runtime and memory use.
| Fact | HitKeep Cloud detail |
|---|---|
| EU region | Frankfurt, Germany at cloud.hitkeep.eu |
| US region | Virginia, United States at cloud.hitkeep.com |
| Operations handled | Runtime operation, updates, backups, mail delivery, and infrastructure monitoring |
| Export path | JSON, CSV, Parquet, NDJSON, and XLSX where the product surface supports them |
| IP metadata | Stores derived country, region, city, provider, and ASN fields for analytics reporting, not raw visitor IP addresses |
| Privacy caveat | Region choice and cookie-less defaults help review, but do not replace legal analysis or consent decisions |
| When to self-host | Choose self-hosting when your organization must own the server, data directory, backup process, and network boundary directly |
Cloud is also the fastest path for an AI visibility pilot: create a workspace, add one site, install hk.js for AI-referred visits, and forward crawler fetch records from CloudFront or another server-side source.