How do I deploy aliasvault on Railway?

You can deploy aliasvault on Railway by clicking the "Deploy Now" button on this page. Railway will automatically set up all the necessary services and configurations for you.

What are the system requirements?

Railway handles all the infrastructure requirements. You only need a web browser to deploy and manage your application.

Is this template free to use?

Yes, this template is free to use within your existing Railway account.

Can I customize this template?

Yes, you can fully customize this template. After deployment, you will have full control of what you've deployed in your Railway project.

How do I get support for this template?

You can get support through our community forum: aliasvault-railway-f8fc2d81, or click "Get template help" for this template for more assistance.

Deploy and Host AliasVault on Railway

About Hosting

AliasVault is an open-source, end-to-end encrypted password and email alias manager.
This Railway template uses the official ghcr.io/aliasvault/aliasvault:latest all-in-one image, which bundles API, web client, admin panel, task runner, SMTP service, and database stack into one container for easy deployment.

Why Deploy

Keep full control of your vault data and hosting environment.
Run the complete AliasVault stack without manual multi-container wiring.
Get fast setup for personal, lab, and demo environments.
Reuse the same deployment pattern across Railway environments.

Common Use Cases

Personal password manager with private self-hosting.
Team demo/staging instance for evaluating AliasVault.
Migration sandbox before moving to a dedicated VPS setup.
Lightweight homelab deployment with managed Railway runtime.

Dependencies for Deployment

Deployment Dependencies

Item	Value	Notes
Container image	`ghcr.io/aliasvault/aliasvault:latest`	Official all-in-one image
Public HTTP port	`80`	Routed by Railway domain
Health endpoint	`/api`	Built-in API health check path
Data paths	`/database`, `/logs`, `/secrets`, `/certificates`	Persistent volumes recommended
Required env vars	`PORT`, `HOSTNAME`	`PORT=80` for routing
Recommended env vars	`FORCE_HTTPS_REDIRECT`, `PUBLIC_REGISTRATION_ENABLED`, `IP_LOGGING_ENABLED`	Safe defaults included
Optional email vars	`PRIVATE_EMAIL_DOMAINS`, `HIDDEN_PRIVATE_EMAIL_DOMAINS`, `SMTP_TLS_ENABLED`	SMTP depends on DNS/network setup

Notes:

Railway HTTP routing targets one internal port; this template targets 80.

SMTP ports (25, 587) may not be reachable in all Railway plans/regions. Treat built-in email receiving as optional unless your network path is confirmed.