Deploy on Railway

The Kaneo Railway template provisions PostgreSQL, a Kaneo API service, and a web service. This template uses separate API and web images, unlike the bundled Docker Compose guide.

​

Deploy the template

1. Open the template and sign in to Railway.
2. Review the services, persistent database volume, and environment references.
3. Generate a secret with openssl rand -hex 32 and set it as AUTH_SECRET on the API service.
4. Deploy and wait for the services to become healthy.

The template supplies the database connection and service URL references. Keep those references rather than replacing them with literal example credentials.

​

Open Kaneo

Open the public web URL and create the initial administrator account. Make a project and task to check the API connection. If you add custom domains, update the public URL settings on the services that consume them. The browser must reach the public API URL; Railway’s private service hostname is for server-to-server traffic.

​

Add the features you need

Configure optional settings on the API service, then redeploy affected services:

• Email for invitations and account notifications.
• Sign-in providers for your identity provider.
• File storage for task attachments.

​

Keep it running

Review Railway’s service logs when a health check fails. For browser failures, check the public API URL and allowed origins before redeploying. Set up database and storage backups using Backups and recovery as a checklist. Record the deployed versions and read the upgrade guide before changing images. For connection, sign-in, and upload problems, see Troubleshooting.