
Deploy cabinet 0.5.0
Cabinet from https://github.com/cabinetai/cabinet
Cabinet
cabinet
Just deployed
/app/data
Deploy and Host cabinet 0.5.0 on Railway
cabinet 0.5.0 is a self-hosted, AI-first knowledge base and workspace for getting real work done with AI agents. It brings your files, tasks, conversations, scheduled routines, and agent team together in one private environment, with your knowledge stored as portable files instead of locked inside a proprietary platform.
About Hosting cabinet 0.5.0
Deploying cabinet 0.5.0 on Railway gives you an always-on Cabinet workspace accessible from any browser. The template runs the Next.js application, Cabinet daemon, realtime events, terminal connections, and reverse proxy together as one service. A Railway volume keeps your files and agent state safe across deployments, while environment variables configure authentication and AI providers. Set a KB_PASSWORD, attach persistent storage at /app/data, and provide credentials for the AI provider you want to use. Railway then handles container builds, health checks, networking, restarts, HTTPS, and future deployments.
Common Use Cases
- Build a private AI workspace where agents can organize knowledge, create files, and complete tasks using shared context.
- Run always-on routines for research, reporting, content production, project tracking, and recurring operational work.
- Give founders and distributed teams a shared, browser-accessible operating system for documents, tasks, dashboards, and AI agents.
Dependencies for cabinet 0.5.0 Hosting
- A persistent Railway volume mounted at
/app/datato preserve Cabinet files, configuration, conversations, and agent state across deployments. - An AI provider configuration, such as OpenCode with OpenRouter or another supported provider, plus any required API key or account credentials.
Deployment Dependencies
- cabinet source repository
- Railway documentation
- Railway volumes
- OpenCode documentation
- OpenRouter API keys
Implementation Details
The template deploys Cabinet as a Docker service and starts the complete web app and daemon stack behind a single public Railway port.
Recommended configuration:
| Variable | Recommended value | Purpose |
|---|---|---|
CABINET_DATA_DIR | /app/data | Location of persistent Cabinet data |
KB_PASSWORD | A strong secret | Protects the public Cabinet URL |
HOSTNAME | 0.0.0.0 | Makes the service reachable through Railway |
PORT | 3000 | Public application port |
NODE_ENV | production | Enables production behavior |
CABINET_PUBLIC_DAEMON_ORIGIN | same-origin | Routes realtime daemon traffic through the public origin |
| Provider API key | Provider-specific | Enables AI agent execution |
Attach the Railway volume to /app/data before relying on the deployment for persistent work. Do not publish or share the generated domain until KB_PASSWORD is configured.
Why Deploy cabinet 0.5.0 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 cabinet 0.5.0 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.
Template Content
cabinet
callmechristian/cabinetKB_PASSWORD
Password to login. !!! leaving blank means anyone can access the endpoint
CABINET_DATA_DIR
Recommended: /app/data
