OpenQuok is a Swiss-army Content OS platform. Individuals and teams use one workspace for social scheduling and directory launch.
Draft and schedule social posts. Review each post before publish. Build product profiles, autofill directory forms with the browser extension, and submit each listing on the directory site. Use the dashboard, the CLI, MCP, and the public API. Self-host when you need an open alternative to closed SaaS tools.
What you can do
Social Scheduling
- Connect social channels. Add Facebook Page, Threads, Instagram, LinkedIn, X, YouTube, TikTok, Dev.to, Bluesky, and Skool to a workspace. Each network keeps its own posting rules and limits — see the social channel catalog.
- Compose for each platform. Write once in Global mode or unlock a channel for its own caption, media, and settings. Preview each version before you schedule — see Global vs per-channel.
- Photo editor. Design and resize visuals for social channels in your browser. Pick platform aspect ratios, export PNG free, or save to your workspace when signed in.
- Humanizer. Rewrite drafts so they read less machine-written. Human and Roughen modes run on-device in Chrome — no account required to copy results.
- Posts management. Plan posts on the calendar, drag to reschedule, and review drafts on Home kanban — see Kanban board and Moving posts.
- Review and approvals. Share preview links and collect client comments before you schedule. Humans give final sign-off before anything goes live.
- Scheduling and time slots. Save drafts, pick a publish time, or use posting time slots per channel. Bundle channels into business profiles for clients or brands.
- Media library. Upload from your device, organize folders, and reuse files in the composer — see Media in posts for per-channel attachments.
- Threads and follow-up comments. Schedule multi-part posts and timed replies on supported networks. Delays, thread finisher, and cross-account plugs are covered in Automations.
- Templates and tags. Save composer presets with Templates for repeat workflows and label campaigns with tags in the composer footer.
- Social analytics. Compare post results and track audience changes across connected accounts. Per-network availability is listed under Platforms → Analytics (Social tab).
- API, CLI, and MCP. Schedule posts, manage plugs, and automate social workflows from scripts or agent clients. Start with OpenQuok Core, the CLI, MCP, or the Public API reference.
Directory launch
- Directory submission. Build a product profile on My Products, pick destinations such as PeerPush and Uneed, and launch with the browser extension. You review each form and submit on the directory site.
- Listing readiness and tracking. See required fields, save live listing URLs, and use per-site variants — see Profile variants.
- Directory analytics. Track domain rating for your product site and compare competitors on the Directory tab in Analytics (paid plans).
- Directory launch API, CLI, and MCP. List profiles, ensure variants, and check listing readiness programmatically — CLI, MCP tools, and the openquok-directory-launch skill.
- Build Backlinks. Filter backlink opportunities, bookmark sites for outreach, and manage your shortlist under Saved → Backlinks.
Agents, tools, and workspace
- AI drafting. Queue social posts from agents, the CLI, or the public API. Everything lands in the same review queue — you approve what publishes.
- Building blocks. Install skills and MCP servers for Cursor, Claude, OpenClaw, and the CLI — OpenQuok Core schedules posts; combine blocks in Skill Builder for custom agent setups.
- Playbooks. Run step-by-step marketing workflows that chain building blocks — viral carousels, video publish flows, and content-calendar batches — then approve every draft before anything goes live.
- Saved playbooks & backlinks. Libs browses Playbooks and Building blocks with hub-style filters, bookmarks listings (free; sync when you sign in), and Your library holds drafts and published stacks. Bookmark sites on Build Backlinks, then reorder and track outreach under Saved → Backlinks.
- Free creator tools. Skill Builder exports agent skills, Best time to post builds timing test plans, and channel-specific pages exist for each shipped network.
- Teams and workspaces. Keep brands and clients in separate workspaces, invite teammates, and manage timezone, profile, and .
Supported platforms
OpenQuok documents social posting channels and directory launch destinations separately. They share marketing language on the Channels hub, but connect and automate differently — see Platforms overview.
Social posting channels
OpenQuok ships OAuth or API integrations for Facebook Page, Threads, Instagram (Business and Standalone), LinkedIn profile and Page, X, YouTube, TikTok, Dev.to, Bluesky, and Skool.
Dev.to and Bluesky connect with credentials you paste in Add Channel — no OAuth redirect. Skool connects with the OpenQuok browser extension while you are signed in on skool.com.
Posting formats, follow-up comments, and social analytics vary by network. Some integrations require provider app approval or publicly reachable media URLs on self-hosted deployments.
Connect social channels · Posting rules · Social integrations (self-host)
Directory launch destinations
PeerPush and Uneed use a product profile on My Products and the same browser extension as Skool — for directory autofill, not OAuth to the directory site. You submit on peerpush.com and uneed.best yourself.
Directory site keys, variants, and extension handoff are in Directory integration and Connect rules → Directory launch.
Directory submission · Directory submission tool · Directory channel catalog
Supported Agents & MCP
- Autonomous agent hosts. OpenClaw, Hermes Agent, Grok Bot, Dots, Meta Muse, ThinkRail, Manus, Gemini Task, and Claude Duet install OpenQuok Core (
@openquok/auto-cli skill) or Connected Apps (MCP) and schedule from chat or a terminal — see Agent setup guides and the agents catalog.
- MCP clients. Antigravity CLI, Android Studio, ChatGPT, Codex, Cursor, Claude Code, Claude Cowork, VS Code / Copilot, Devin Desktop, Amp, Warp, Muse Code, and Grok Build connect OpenQuok over HTTP with a workspace programmatic token — see MCP setup guides and MCP getting started.
Drafts from every path land in the same review queue on Home and the calendar.
Create a programmatic token under Account → Settings → Developers → Access, or start on Cloud when you want hosted plans and billing handled for you.
OpenQuok Core · Building blocks · Playbooks · Build Backlinks · Agent setup guides · MCP setup guides · CLI getting started · MCP getting started · Agents catalog
Packages
How it works
Let AI agents handle volume — drafting and scheduling at scale. You handle quality: review and approve what goes live across your channels.
Terminal (openquok CLI · schedule posts · upload media · flip draft ↔ scheduled) · Chat (OpenClaw · Hermes · Claude · Cursor) · Web UI (calendar · kanban review · analytics · approve before publish)
Prerequisites
- Node.js 24.22.1+ (or run
nvm use — see root .nvmrc)
- Corepack (for pnpm)
corepack enable
Quick start
For a first-time local run — install dependencies, configure env for backend/ and web/, and wire optional workers / CLI auth — follow the Quick Start Guide.
Day-to-day commands (dev servers, tests, DB, deploy) live under Development environment. Production deploy notes are in Production deployment.
Self-host (Docker Compose)
Build from clone (default) — configure env, then build all services from the monorepo:
cp infra/self-host/.env.example infra/self-host/.env
# fill PUBLIC_SUPABASE_* / SUPABASE_SECRET_KEY (and matching VITE_* for the web image)
docker compose -f infra/self-host/docker-compose.yml up --build
Pull pre-built images (optional) — skip local builds for API and workers when published tags exist (ghcr.io/ratimon/openquok-* or docker.io/ratimon/openquok-*). Set OPENQUOK_IMAGE_TAG in .env, use the docker-compose.images.yml overlay, pull, then up — you still compose build web unless your VITE_* match the published web bake. Details: Docker (pre-built images). Maintainers: infra/self-host/PUBLISHING.md (tag self-host-v<semver> → CI publish).
When the stack is up, open the UI at http://localhost:4007 (API at http://localhost:3000). Full env and bring-up steps: Docker Compose (self-host).
Tech stack
- PNPM workspace
- Supabase DB & Auth
- Cloudflare R2
- Express.js
- Svelte 5
- Tailwind CSS
- DaisyUI
- Redis
- Stripe
- Resend
- Sentry
- Posthog
- Vercel
- Railway
Learn more at Architecture
Links
Product docs (General tab)
CLI, MCP, and Public API
Self-host & setup
- Developer quick start
- Installation — Docker Compose, pre-built Docker images, system requirements, development environment, and production deployment
- Social integrations — operator OAuth apps, env keys, and provider dashboards
- Admin setup — platform admin, OAuth apps, and post-deploy setup
- Configuration – Backend, Web, Workers, and CLI auth server
Compare & alternatives
- Compare — head-to-head feature and pricing comparisons with other schedulers
- Alternatives — best-alternatives guides when you evaluate Buffer, Hootsuite, and similar tools
Extensions Hub directories
Social
Featured Blogs
Contributing
License
| Path | License |
|---|
Repository default (backend/, web/, orchestrator/, sdk/, agent/src/, …) | AGPL-3.0-or-later |
agent/skills/ | MIT |
Compiled CLI code published as @openquok/auto-cli is AGPL-3.0-or-later. Agent skills under agent/skills/ are MIT so they can be copied into other agent setups without AGPL obligations on the skill text alone.
Star History
