What gets deployed
The template connects the services over Railway’s private network and supplies
the shared PostgreSQL DSN, NATS URL, and encryption key. Database migrations
run before the server starts.
Deploy the template
1
Open the template
Click Deploy on Railway above, sign in, and choose the workspace where
you want to create the project.
2
Review the project
Confirm that the server, control plane, PostgreSQL, and NATS services are
included. Review the resource plans and generated variables before
deploying.
3
Wait for the services
Railway provisions the backing services, applies database migrations, and
starts the server and control plane. Wait for every service to become
healthy.
4
Open Filament
Open the public domain for the Filament server. If the template has not
created one, select the server service and generate a domain under
Settings → Networking.
Run execution
Railway has no Kubernetes Jobs API, so the template setsDISPATCH_MODE=inproc. Every pipeline run executes inside the control-plane
service and shares its CPU and memory.
Increase the control-plane service’s CPU and memory for concurrent or
resource-intensive pipelines. Use the
Kubernetes deployment when runs need
isolated containers or independent resource configuration.
Before production
- Configure authentication before storing sensitive connector credentials on
a public deployment. Authentication is disabled when
AUTH_PROVIDERis unset. - Keep
ENCRYPTION_KEYbacked up and unchanged. Replacing it makes existing encrypted credentials unreadable. - Configure retention and backups for PostgreSQL and JetStream to match your recovery requirements.
- Pin the server and control-plane images to the same Filament release, and upgrade both together.