Deploy and Host VPS Fleet Watch Hub with Beszel on Railway

A persistent Beszel hub for external VPS agents and fleet alerts.

About Hosting VPS Fleet Watch Hub with Beszel

Operators managing a small fleet of VPS machines outside Railway.

Set USER_EMAIL to your real administrator address before deploying. Sign in with USER_PASSWORD from Railway variables, add a system and install the upstream Beszel agent on that VPS. Configure its HUB_URL and TOKEN for outbound WebSocket connectivity.

Included services and storage

Service	Persistent storage	Public access
App	/beszel_data	HTTPS domain

First deployment

Review required inputs in the deploy form and supply your own administrator email where requested.
Deploy the services and wait for the application and any database migrations to finish.
Open the generated HTTPS domain and follow the workflow above.

Why Deploy VPS Fleet Watch Hub with Beszel on Railway

The definition supplies an HTTPS endpoint, generated credentials where supported and explicit storage paths. PostgreSQL, when present, stays private. Public upstream image manifests are locked to immutable digests so an upstream tag change does not silently replace a running version.

Common Use Cases

Monitor VPS CPU and memory history.
View Docker statistics from an external agent.
Configure fleet threshold alerts.

Dependencies for VPS Fleet Watch Hub with Beszel

Upstream application and its documentation. The upstream authors own the application and its license. This recipe does not claim application authorship or official endorsement.
A Railway plan with resources sufficient for these services. Hosting, storage and outbound traffic are billed by Railway; no software subscription, bank connection, SMTP account or provider credit is included.

Operational limits and backups

This template deploys only the hub. It cannot inspect Railway host metrics or a Railway Docker socket. Agents must be installed separately on machines you administer. SSH polling is disabled; agents connect outward through HTTPS/WebSockets.

Run one replica for volume-backed applications. Schedule volume backups and export important application data; a persistent volume is not a backup. Keep generated secrets with the backups and review upstream migration notes before changing the pinned image. Credentials cannot all be rotated by changing first-run environment variables after accounts already exist.

Validation status

Prepared on 2026-10-18 from upstream installation documentation and public image manifests. Railway schema, variable references and publication metadata are checked before publication. Application runtime boot checks were not performed. This is an independently authored deployment recipe for existing software, not a claim of novel software, audited security or Railway partner verification.

Deploy this recipe

Review the required inputs and hosting resource costs before deploying.

Related deployment recipes

Uptime Kuma with Persistent Storage — Uptime checks, alerts and status pages with persistent monitor data.
ntfy Private Notifications with Persistent Data — Private push notifications with generated admin and persistent storage.
Supplier Page Watch with ChangeDetection — Private supplier-page monitoring with durable diffs and bounded polling.

These are separate deployments; no preconfigured integration between the applications is implied.

Disclosure: this template is maintained independently. Its maintainer may earn Railway usage kickbacks when other people deploy it. Railway bills hosting separately; no paid software subscription or provider credits are included.