
# Web analytics on Railway

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

Canonical page: https://launchinyourcloud.com/clouds/railway/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: Railway workspace, project and environment; platform-managed infrastructure
- Provider group: application-platform
- Provider classification: Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Source: https://docs.railway.com/projects (checked 2026-11-20).
- Network: Project/environment private networking with separately exposed public services
- Identity and access: Workspace/project access and scoped deployment tokens
- Installation guidance: Deploy application containers and data services into your project. Community templates require review of source images, credentials, volumes and release compatibility; they do not imply upstream vendor support.
- Guidance source: https://docs.railway.com/projects
- Guidance reviewed: 2026-11-12


### Project networking

Private networking connects services inside a project environment using encrypted tunnels and internal DNS. This project boundary does not give the customer ownership of the underlying infrastructure account.
Source: https://docs.railway.com/networking/private-networking (reviewed 2026-11-14).

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

2 listings.


## Plausible Community Edition

Website analytics tracker and dashboard available as a self-hosted Community Edition.

- Listing: https://launchinyourcloud.com/directory/plausible-ce/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPLv3 for Plausible Community Edition. Commercial/cloud-only features and branding have separate terms.
- Licensing model: open-source
- Installation: Use the official Community Edition Docker Compose repository and configure the application, PostgreSQL and ClickHouse services.
- Architecture: Customer-operated analytics application, tracker endpoint and persistent analytics databases
- Operations: Customer manages tracker delivery, ingestion, databases, email configuration, TLS, backups and CE upgrades.
- Product website: https://plausible.io/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Use the CE feature list when evaluating functionality; managed-service funnels, revenue metrics, SSO and other features are not automatically available in the self-hosted edition. Plausible Community Edition v3.2.1 removes the /storybook endpoint after CVE-2026-8467 showed it could permit remote code execution when exposed to an untrusted network. Upgrade affected v3.0–v3.2 deployments to v3.2.1 or later; until upgraded, block /storybook at the reverse proxy or equivalent network layer.

AGPLv3 for Plausible Community Edition. Commercial/cloud-only features and branding have separate terms. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated analytics application, tracker endpoint and persistent analytics databases. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- web-analytics: Website traffic, referral and event analytics using the self-hosted Community Edition tracker and dashboard; some commercial cloud features are excluded.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/plausible--plausible-community-edition (checked 2026-11-12). 


### Cloud deployment evidence

- Plausible Community Edition deployment on Railway (railway): https://railway.com/deploy/plausible--plausible-community-edition
  This community template deploys the Plausible Community Edition image with PostgreSQL, ClickHouse and a mail service in a customer project. ClickHouse uses community configuration packaging. Review image versions, storage and outbound email, and create the initial owner promptly; this is distinct from paid Plausible Analytics hosting.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official contribution documentation credits community work on the tracker, integrations and self-hosting. The upstream release stream includes ongoing Community Edition maintenance.

Reviewed 2026-11-10.

- Documented community contributions: https://plausible.io/docs/contribute

- Community Edition release maintenance: https://github.com/plausible/analytics/releases

### Sources

- Official installation and runtime: https://github.com/plausible/community-edition

- Upstream project and capabilities: https://github.com/plausible/analytics

- Current upstream license: https://raw.githubusercontent.com/plausible/analytics/master/LICENSE.md

- Current self-hosted edition scope: https://plausible.io/self-hosted-web-analytics

- Plausible CE v3.2.1 remote-code-execution fix: https://github.com/plausible/analytics/releases/tag/v3.2.1

### Licensing sources

- https://raw.githubusercontent.com/plausible/analytics/master/LICENSE.md

### Infrastructure sources

- https://github.com/plausible/community-edition


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 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: Explicitly unsupported. The vendor explicitly excludes SSO from Community Edition. SSO in the managed Cloud feature set does not establish that the AGPL self-hosted CE distribution includes it. Scope: Plausible Community Edition versus managed Cloud feature comparison. Source: https://plausible.io/self-hosted-web-analytics (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The versioned CE recipe supplies a Compose stack for Plausible, PostgreSQL and ClickHouse. Configure the base URL and unique secret, persistent storage and either automatic TLS or your reverse proxy; follow the matching release upgrade instructions. Scope: Versioned Community Edition v3.2.1 deployment stack. Source: https://github.com/plausible/community-edition/blob/v3.2.1/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/plausible/community-edition/blob/v3.2.1/compose.yml. Artifact reference: v3.2.1.

- Minimum footprint / sizing: Documented. The reviewed Community Edition recipe recommends at least 2 GB RAM and a CPU supporting SSE 4.2 or NEON for its analytics/database stack. Size retention and traffic separately. Scope: Versioned Community Edition v3.2.1 deployment recipe. Source: https://github.com/plausible/community-edition/blob/v3.2.1/README.md (reviewed 2026-11-14).

- License pricing: Documented. Community Edition is free to self-host under AGPLv3; operators pay for hosting and maintenance. Cloud subscription features and services are separate, and the vendor excludes SSO and several premium features from CE. Review AGPL obligations for modifications and redistribution. Scope: Community Edition software terms, excluding cloud charges and managed Cloud subscriptions. Source: https://plausible.io/self-hosted-web-analytics (reviewed 2026-11-20). Supporting source: Published v3.2.1 application licence — https://github.com/plausible/analytics/blob/v3.2.1/LICENSE.md.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed upstream release is v3.2.1, published 2026-05-15. This is a dated release snapshot, not a support designation, a future cadence promise or approval to replace a provider package. Scope: Upstream plausible/analytics release record; commercial editions, LTS branches and provider packages can differ. Source: https://github.com/plausible/analytics/releases/tag/v3.2.1 (reviewed 2026-11-17).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Plausible CE storybook code-execution advisory (security-advisory): CVE-2026-8467 concerns the exposed /storybook endpoint; the 3.2.1 CE patch removes it. Scope: Plausible Community Edition v3.0–v3.2 image tags, including the prerelease aliases enumerated by the vendor; fixed in v3.2.1. Conditions: The endpoint must be reachable from a public or other untrusted network. This is a review of an existing disclosure, not a new vulnerability announcement. Action: Upgrade affected CE installations to v3.2.1 or later. Until then, block /storybook at the reverse proxy or an equivalent boundary. Source: https://github.com/plausible/analytics/releases/tag/v3.2.1; reviewed 2026-11-17.




## 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).






