
# Web analytics on Northflank

Compare documented Web analytics deployments on Northflank, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/northflank/web-analytics/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: Northflank team and project; hosted platform or a separately connected customer cluster
- Provider group: application-platform
- Provider classification: The published Northflank recipes use its hosted platform. Northflank also offers connected customer clusters; those require separate application-specific evidence. Source: https://northflank.com/docs/v1/application/getting-started/create-a-project (checked 2026-11-20).
- Network: Private project services with explicitly exposed public ports
- Identity and access: Team/project roles, API tokens and secret groups
- Installation guidance: Deploy builds, containers, jobs and database add-ons in a project. The hosted platform is separate from Northflank BYOC: confirm the underlying account, cluster ownership and operating agreement for that option.
- Guidance source: https://northflank.com/docs/v1/application/getting-started/create-a-project
- Guidance reviewed: 2026-11-12


### Private and VPC ingress

Project-internal ports, public ingress and VPC ingress are distinct paths. Confirm the deployment mode and private-load-balancer availability; hosted-project documentation does not establish a customer-owned VPC deployment.
Source: https://northflank.com/docs/v1/application/network/networking-on-northflank (reviewed 2026-11-14).

The listings below have evidence for Northflank. Read each cloud evidence note for the applicable package, edition and support qualifications.

1 listing.


## Umami

Self-hosted website and event analytics application with dashboards and PostgreSQL storage.

- Listing: https://launchinyourcloud.com/directory/umami/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean, fly, heroku, northflank, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT License for upstream Umami.
- Licensing model: open-source
- Installation: Build from source, run the official prebuilt container or use its Docker Compose application/PostgreSQL setup.
- Architecture: Customer-operated web analytics service and PostgreSQL database
- Operations: Customer manages tracking endpoints, database, admin credentials, retention, TLS, backups and upgrades.
- Product website: https://umami.is/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Change the documented initial administrator password and configure production secrets. Third-party integrations, tracking destinations and external databases require separate configuration; Umami Cloud is a distinct offering.

MIT License for upstream Umami. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated web analytics service and PostgreSQL database. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- web-analytics: Website and event analytics through a deployed tracking endpoint and analytics application.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-digitalocean (checked 2026-11-12). 

- fly: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-fly-io (checked 2026-11-12). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-heroku (checked 2026-11-12). 

- northflank: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-northflank (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-railway (checked 2026-11-12). 


### Cloud deployment evidence

- Umami self-hosting on a DigitalOcean Droplet (digitalocean): https://docs.umami.is/docs/guides/running-on-digitalocean
  The project documents running the Umami application and PostgreSQL on a customer Droplet with PM2 and Nginx. The guide links older Ubuntu setup examples; use currently supported OS and Node.js versions, configure HTTPS and maintain backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Fly.io (fly): https://docs.umami.is/docs/guides/running-on-fly-io
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Heroku (heroku): https://docs.umami.is/docs/guides/running-on-heroku
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Northflank (northflank): https://docs.umami.is/docs/guides/running-on-northflank
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Railway (railway): https://docs.umami.is/docs/guides/running-on-railway
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Upstream release notes document current runtime/security work and credit multiple named contributors across successive releases.

Reviewed 2026-11-10.

- Maintenance and named release contributors: https://github.com/umami-software/umami/releases

- Public upstream project: https://github.com/umami-software/umami

### Sources

- Official installation and runtime: https://docs.umami.is/docs/install

- Upstream project and capabilities: https://github.com/umami-software/umami

- Current upstream license: https://raw.githubusercontent.com/umami-software/umami/master/LICENSE

- Umami self-hosted deployment on Fly.io: https://docs.umami.is/docs/guides/running-on-fly-io

- Umami self-hosted deployment on Heroku: https://docs.umami.is/docs/guides/running-on-heroku

- Umami self-hosted deployment on Northflank: https://docs.umami.is/docs/guides/running-on-northflank

- Umami self-hosted deployment on Railway: https://docs.umami.is/docs/guides/running-on-railway

### Licensing sources

- https://raw.githubusercontent.com/umami-software/umami/master/LICENSE

### Infrastructure sources

- https://docs.umami.is/docs/install


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The API documents an SSO token endpoint requiring existing authentication and Redis. This does not establish a generic SAML/OIDC enterprise identity-provider integration or its edition entitlement. Scope: Authenticated token exchange checked; enterprise federation remains unresolved. Source: https://docs.umami.is/docs/api-reference/sso (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official guide documents source builds, application containers and Compose. It explicitly identifies the HelmForge Kubernetes chart as third-party; change the default administrator password and configure the database and secrets. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.umami.is/docs/install (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The install guide requires the application runtime and a PostgreSQL database, but does not give a numeric whole-stack production CPU/RAM/storage minimum. Event volume, retention, query concurrency and HA determine capacity; provider demo allocations are not a 100-user, 1 TB HA sizing guarantee. Scope: Current upstream self-hosted topology; whole-system sizing remains unconfirmed. Source: https://docs.umami.is/docs/install (reviewed 2026-11-20).

- License pricing: Documented. The reviewed v3.5.0 application is MIT-licensed and can be self-hosted without a core software subscription. Retain the required copyright/licence notices; hosting, database, operations and Umami Cloud services are separate costs. Scope: Published self-hosted application terms; not a Cloud plan quote. Source: https://github.com/umami-software/umami/blob/v3.5.0/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v3.5.0, published 2026-11-12. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream umami-software/umami release record; commercial editions and deployment packages may differ. Source: https://github.com/umami-software/umami/releases/tag/v3.5.0 (reviewed 2026-11-14).






