Deploy fronted
web element and rtc and the for call
matrix rtc
Just deployed
lk-jwt-service
Just deployed
web element
Just deployed
element call
Just deployed
Deploy and Host fronted on Railway
What is fronted?
Fronted is a lightweight frontend service that provides a user-facing interface for interacting with backend systems. It typically serves static assets, handles routing, and connects users to core services like authentication, messaging, or APIs. By deploying fronted, you enable a clean, accessible entry point for your application stack.
About Hosting fronted
Hosting fronted on Railway involves deploying a frontend service that can serve static files or act as a proxy to backend APIs. The process requires configuring environment variables for service URLs, client IDs, and themes, while ensuring integration with supporting services like MAS, Synapse, and LiveKit. Railway simplifies this by auto-injecting domains and managing secrets, so you don’t need to manually configure hostnames or credentials. With Railway, fronted can be deployed quickly, scaled automatically, and integrated seamlessly with other services in your stack, making it ideal for production-ready frontend hosting.
Why Deploy fronted on Railway
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying fronted on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Common Use Cases
Hosting a frontend interface for a Matrix-based communication stack
Serving static assets for Element Web or custom web clients
Acting as a proxy layer to connect users with MAS, Synapse, and LiveKit services
Dependencies for fronted Hosting
Backend services: MAS, Synapse, LiveKit, and JWT service for authentication and communication
Environment variables: Properly configured URLs, client IDs, and secrets to link fronted with backend services
Deployment Dependencies
Railway-managed environment variable injection (RAILWAY_PUBLIC_DOMAIN, RAILWAY_PRIVATE_DOMAIN)
Railway Documentation
Matrix Synapse Documentation
Matrix Authentication Service (MAS)
LiveKit Documentation
Template Content
matrix rtc
Penghuot/ess-helmLIVEKIT_DOMAIN
Domain for your LiveKit deployment. Example: livekit.example.com
LIVEKIT_API_KEY
API key for LiveKit server authentication. Example: lk_api_key_12345
LIVEKIT_API_SECRET
API secret for LiveKit server authentication. Example: lk_api_secret_67890
lk-jwt-service
Penghuot/ess-helmLIVEKIT_KEY
Alternate key for LiveKit client authentication. Example: lk_client_key_abcdef
LIVEKIT_URL
Base URL for LiveKit server. Example: https://livekit.example.com
LIVEKIT_SECRET
Alternate secret for LiveKit client authentication. Example: lk_client_secret_xyz
LIVEKIT_FULL_ACCESS_HOMESERVERS
Comma-separated list of homeservers with full LiveKit access. Example: synapse.example.com,another-hs.example.com
web element
Penghuot/ess-helmMAS_URL
Public URL of the MAS service. Example: https://mas-service-production.up.railway.app
SERVER_NAME
Matrix homeserver name (same as Synapse server name). Example: synape-production-7433.up.railway.app
HOMESERVER_URL
Public URL of the Synapse homeserver. Example: https://synape-production-7433.up.railway.app
ELEMENT_WEB_URL
Public URL of your Element Web client. Example: https://web-element-production.up.railway.app
ELEMENT_CALL_URL
Public URL of your Element Call service. Example: https://element-call-production.up.railway.app
LK_JWT_SERVICE_URL
Public URL of your JWT service for LiveKit. Example: https://lk-jwt-service-production.up.railway.app
ELEMENT_DEFAULT_THEME
Default theme for Element Web. Example: light
ELEMENT_WEB_CLIENT_ID
OIDC client ID registered for Element Web. Example: 00000000000000000000SEC0ND
element call
Penghuot/ess-helmLIVEKIT_URL
Base URL for LiveKit server (duplicate variable, ensure consistency). Example: https://livekit.example.com
SERVER_NAME
Matrix homeserver name (duplicate, ensure consistency). Example: synape-production-7433.up.railway.app
HOMESERVER_URL
Public URL of the Synapse homeserver (duplicate, ensure consistency). Example: https://synape-production-7433.up.railway.app
LIVEKIT_JWT_SERVICE_URL
Public URL of the JWT service used by LiveKit. Example: https://lk-jwt-service-production.up.railway.app
