No software fee
Self-hosting is not a hosted plan tier. You pay for your own servers, database, infrastructure, and any social network developer apps you use.
OpenQuok Free self-hosting
Alternative scheduleron your serversame OpenQuok but free
A free alternative to paid schedulers like Buffer and Hootsuite when you deploy OpenQuok on your own server — no software fee under AGPL.
AGPL-3.0-or-later
Inspect and modify the source under the licence terms. You can even run your own Scheduler as SaaS as long as you stay opensource.
Choose your path
Hosted cloud, self-host dockerized scheduler, or your own cloud stack
Start on openquok.com with a free trial, or run OpenQuok yourself. Operator paths have no software fee under AGPL.
Hosted cloud plan
You want us to run OpenQuok for you.
- We run updates and security for your workspace
- Start a 7-day free trial — no credit card required
- Meta, Google, and TikTok apps are ready for cloud workspaces
Docker Compose self-host
You run OpenQuok on your own server or homelab.
- Run web, API, Redis, and workers on one machine
- Store uploads on the server; optional CLI profile for agent login without API keys
- You manage the server, secrets, upgrades, and backups
Cloud production stack
You deploy on Vercel, Railway, or other cloud hosts.
- Run web, API, and workers on services you control
- Same scheduler with your env vars and scaling rules
- You pay for Redis, Supabase, storage, and workers in your accounts
Start here
Checklist before you go live
Requirements, deployment, and optional agent auth — follow these steps before you open your instance to users.
Docker Compose self-host guide
Run OpenQuok on one server with our step-by-step Docker guide.
Production deployment (custom cloud)
Run web, API, and workers on cloud hosts you pick, such as Vercel or Railway.
CLI device-login walkthrough
Blog walkthrough for agent sign-in without storing API keys on the server.
System requirements
Check disk, ports, and Supabase before your first install.
Self-hosting docs overview
How the pieces fit together and where to start in the docs.
CLI auth and OAuth server
Let agents sign in from the command line without API keys on the server.
Social integrations
Set up each social network your team will connect in the dashboard.
Connect channels
Set up social networks
Create developer apps and env vars for each network. Your team connects accounts in the dashboard once you finish.
Connections overview
What you set up vs what your team connects in the app.
Meta Threads
Register your Meta app and connect Threads to your instance.
Get Instagram API access and link it to OpenQuok.
Facebook Page
Set up a Meta app for Facebook Page posting.
YouTube
Turn on YouTube in Google Cloud and connect it.
TikTok
Register a TikTok developer app and add your callback URL.
Create a LinkedIn app and connect personal profiles.
LinkedIn Page
Set up posting to a LinkedIn Company Page.
X (Twitter)
Register an X developer app and add your callback URLs.
Dev.to
No app needed — users add their own API key in the dashboard.
Modify further
Tune each layer of your stack
For maintainers who want to go beyond the quick start — open the guide for the backend, web, worker, or CLI piece you are changing.
Backend configuration
Env files, Supabase, Redis, and service keys for the API.
Supabase
Create a project, copy API keys, and match dashboard settings.
Database and migrations
Run OpenQuok migrations before the first user signs up.
Redis cache
Point the API at Redis for cache and job queues.
Docker (local services)
Run Redis locally or follow the self-host Compose stack.
Upload storage (R2 or local)
Store media on disk or in Cloudflare R2 for publishing.
Google sign-in
Wire Google OAuth for dashboard login on your domain.
Email (Resend or local)
Send sign-up and notification email from your instance.
Rate limiting
Tune auth, API, and upload limits for your deployment.
Sentry
Send API errors to Sentry when you enable monitoring.
Stripe billing
Optional — enable subscriptions when you bill workspaces.
Web configuration
Vite env files and defaults for the dashboard origin.
Vite (SvelteKit)
Set VITE_* vars, HTTPS dev, and API proxy rules.
SEO and marketing defaults
Meta tags and social links for your public domain.
Config defaults
Company name, navigation, and fallback site copy.
PWA metadata
App name and icons in web-config.json.
AI crawlers and robots.txt
Let search and AI crawlers read your public pages.
Worker configuration
BullMQ workers, Redis, and the admin queue dashboard.
Workers with Docker
Start Redis and worker scripts on your machine.
Redis and queues
Share REDIS_* settings between API and workers.
Railway (workers)
Deploy always-on workers on Railway.
CLI auth server
Env vars for openquok auth:login on your network.
Auth server architecture
How device login flows between CLI, browser, and API.
Neon Postgres
Host auth-server state in Neon when you split services.
Scaling and Postgres
Run more than one auth server against pooled Postgres.
Self-hosting FAQ
Self-host OpenQuok,answered
Common questions about cost, stack size, parity with hosted OpenQuok, social apps, CLI auth, and exposing Compose on a VPS.
Docker Compose is a single-host operator bundle under infra/self-host/ — API, web, Redis, and workers on one machine you control. Production deployment splits the same services across cloud hosts you choose (for example Vercel for web, Railway for API and workers). Both paths need an external Supabase project; neither is a hosted plan tier. Start with Docker Compose or production deployment.
OpenQuok charges no software fee on operator-run paths under AGPL-3.0-or-later. You still pay for servers, Supabase, bandwidth, TLS, and any social developer apps you register. The hosted cloud plan on openquok.com follows pricing tiers. Compare all three paths on Self-host OpenQuok.
Docker Compose runs web, API, Redis, and three BullMQ workers from infra/self-host/docker-compose.yml. Production deployment wires the same roles across separate cloud services — see production deployment and worker configuration. You supply an external Supabase project in both paths. Optional --profile cli adds Postgres and the device-login auth server. Start with system requirements.
Yes. You get the same calendar, kanban, composer, agents, Public API, and MCP tools. Hosted plan limits apply only to the cloud plan on openquok.com. Operator-run Compose and production stacks skip hosted billing and use your own developer apps. Compare paths on Self-host OpenQuok.
On self-host, yes — for OAuth networks you connect. Fill only the environment for channels you use, then recreate API and workers. Dev.to uses a user API key in the dashboard with no operator app. See social integration docs and the optional provider table in Docker Compose.
Yes. Start Compose with --profile cli, register an OAuth app with the device callback URL, and use openquok auth:login from the agent host. Read agent configuration and OAuth server admin — or follow the device-login walkthrough.
The stack targets trusted local or private-network operators — not a multi-tenant public edge by default. Put TLS in front, set NOT_SECURED=false, restrict published ports, rotate secrets, and read operator responsibilities before you open registration on the internet.
Lazy and don't want to operate a server?
Start a hosted workspace on openquok.com. We run updates, edge TLS, and cloud OAuth apps so your team can connect channels and schedule in minutes.