Self-hosting gives a team control over deployment, storage and network boundaries. It also makes the team responsible for backups, upgrades, GeoIP data, proxy configuration, secrets, rate limits and deletion workflows.
| Area | Self-hosted | Nanolytica Cloud |
|---|---|---|
| Infrastructure | You operate the application, ClickHouse, SQLite backups and reverse proxy. | The hosted service runs the shared infrastructure; deployment-specific guarantees still need confirmation. |
| Privacy boundary | You choose network, logs, retention and access controls. | You rely on the Cloud architecture and should review its collector, retention and sharing behavior. |
| Maintenance | Plan upgrades, migrations, health checks and GeoIP refreshes. | Start with a managed dashboard and move only when operational control is worth the work. |
Before you deploy
- Set the trusted proxy CIDR and verify the application logs report the expected client address behavior.
- Mount the GeoIP database deliberately and test country coverage with aggregate requests.
- Set ClickHouse TTLs, backup schedules and log retention that match your policy.
- Restrict public dashboards and document how site deletion affects event rows and backups.
Use the privacy architecture as a checklist, or try the hosted live demo before taking on the operational surface.