Open SourceSelf hosting
Self-Hosting with Railway
Planned one-click deployment flow for Railway.
Railway deployment is planned but not yet available.
Why consider AccessLayer Cloud instead?
If you do not need to run AccessLayer in your own infrastructure, AccessLayer Cloud is usually the simpler choice.
- No deployment pipeline to maintain
- Upgrades and platform operations handled by AccessLayer
- Faster access to newly released product capabilities
- Less risk around ongoing maintenance for databases, secrets, and service health
Feature availability
Self-hostable builds are published for teams that need deployment control, but AccessLayer Cloud may receive new features and platform improvements first.
Status
- Current status: Coming soon
- Planned approach: one-click deployment template
Planned One-Click Flow
- Open Railway template link
- Provision services
- Set required environment variables
- Deploy and validate with a smoke test
Expected Inputs
- AccessLayer environment variables
- Required connector and API secrets
- Domain configuration, optional at first
Temporary Recommendation
Use Self-Hosting with Docker until the Railway template is published.
Feedback
If Railway is your preferred target, share your requirements on the Contributing and Feedback page.