Deploy vizier
The one agent-first platform for your entire business stack
junkiez/vizier:latest
Just deployed
/app/data
Deploy and Host Vizier on Railway
Vizier is a self-hosted, agent-first platform for building internal software end to end. Collections with typed fields, validation and per-role access; JavaScript functions; server-rendered pages; document templates; scheduled jobs; email and messaging integrations — one binary, one admin UI, and an MCP endpoint so AI agents can build and operate it directly.
About Hosting Vizier
Vizier ships as a single container with no external services to run. Deployment is one service plus a persistent volume mounted where the data lives. You set a public URL and an auth secret, and open the app: the first run walks you through creating the admin account and company profile. Because state is a file on disk, run a single replica and scale vertically; automatic off-site backups to any S3-compatible bucket are built in.
Common Use Cases
- Internal business systems — orders, inventory, CRM and receivables — with typed collections, validation rules, record history and per-role permissions, without writing a backend
- Form, webhook and API endpoints backed by JavaScript functions that read and write collections, send email, render PDFs and call out to other services
- Agent-built internal tools: point Claude or any MCP client at the instance and have it create collections, functions, pages and scheduled jobs directly
- Customer-facing content and landing pages rendered server-side from the same data, with scheduled reports and notifications on top
Dependencies for vizier Hosting
- A persistent volume for the data directory (databases, uploaded files and backups all live there)
- Nothing else — no external database, cache or queue is required
Deployment Dependencies
Required
- Railway volumes — persistent storage for the data directory
Optional
Everything below is optional and configured in the admin UI after the first run — none of it is needed to deploy, and you only supply credentials for the integrations you actually use.
-
Ollama — for a local or self-hosted model
-
Model Context Protocol — connect Claude or any MCP client to build and operate the instance
-
Any SMTP provider — outbound mail
-
Resend — outbound mail over the Resend API
-
Any IMAP mailbox — inbound mail into the shared inbox
-
X (Twitter) API — direct messages; paid tier
Implementation Details
The image listens on :8080 and stores everything under /app/data, which is where the volume should be mounted.
| Variable | Required | Notes |
|---|---|---|
PUBLIC_URL | yes | The instance's public URL. Startup fails if empty. |
AUTH_SECRET | yes | Signs sessions. Ships with a placeholder — set a strong value. |
DATA_DIR | no | Defaults to /app/data. Mount the volume here. |
HTTP_ADDR | no | Defaults to :8080. |
Healthcheck:
GET /api/v1/health → 200 {"status":"ok"}
Admin ui lives under /_ path
Optional integrations are configured in the admin UI rather than by environment variable: SMTP and Resend for email, Telegram and other messaging channels, AI providers, and scheduled S3 backups.
Why Deploy vizier 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 vizier 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
junkiez/vizier:latest
ghcr.io/junkiez/vizier:latest
