Overview - Installation
Set up OpenQuok — system requirements, Docker Compose self-host, local development, and Vercel / Railway production deploys for the social scheduler.
1 min read
Connect your agent today
Draft from chat, review in your calendar, and publish only what you approve.
Installation
Recommended path
Use Docker Compose for a full self-hosted stack (API, web, Redis, and workers). Use local development when you are contributing to the repo. For a production split without Compose, deploy API and web on Vercel and workers on Railway.
System requirements
CPU, RAM, ports, Docker, and operator-provided Supabase for self-host
Docker Compose (self-host)
Full app stack from the monorepo
Production deployment
Vercel API and web, Redis, optional BullMQ workers
Maintenance mode
MAINTENANCE_MODE write-freeze across backend, web, and workers
Development environment
Local development commands
Production Vercel
Vercel deployment detail for backend and web
Production Railway (workers)
Railway deployment detail for Always-on orchestrator worker services
Related Section(s)
General
What OpenQuok is and how to use the social scheduler
Cloud
Hosted plans, trial, and billing
Backend configuration
Env files and variables for the backend / Supabase workspace
Configuration - Worker
Worker env, Docker, Redis, Railway, and scripts
Frontend configuration
Environment variables for the SvelteKit app in web/
Super Admin
Platform admin setup after deployment