Deploy and Host Atomic on Railway

About Hosting Atomic on Railway

Atomic runs well on Railway using the upstream all-in-one container, which bundles the web UI, API server, and nginx reverse proxy in a single service for one-click browser access.

Tech Stack

• Atomic all-in-one container (ghcr.io/kenforthewin/atomic:1.32.4)
• Rust backend (atomic-server) with SQLite storage
• React web frontend served through nginx
• Railway managed networking and persistent volume

Why Deploy Atomic on Railway

Railway gives Atomic a fast production path with managed HTTPS, simple variable management, and persistent volume support while keeping the deployment minimal by reusing the upstream container entrypoint.

Common Use Cases

• Personal knowledge base hosting with browser access
• Shared team notes and semantic search workspace
• Self-hosted MCP-enabled knowledge server
• Persistent long-running Atomic instance for desktop and mobile clients

Deployment Notes

Atomic is deployed as a single HTTP service using ghcr.io/kenforthewin/atomic:1.32.4 and listens through nginx on container port 8081. Set PORT=8081 so Railway routes traffic to the correct process, and mount a persistent volume at /data for SQLite databases and application state. PUBLIC_URL should point to the Railway public domain for MCP/OAuth discovery support.

Dependencies for Atomic on Railway

This template uses one service and no external database dependency.

Deployment Dependencies