Overview
OpenQuok Cloud vs self-hosting for the social scheduler — hosted plans, Stripe billing, pre-registered OAuth, and when to run your own stack.
Connect your agent today
Draft from chat, review in your calendar, and publish only what you approve.
Overview
OpenQuok Cloud is the hosted social scheduler: sign up, connect channels, and schedule posts without operating databases, workers, or provider developer apps. The product is the same application you can self-host; Cloud is who runs the stack, who registers OAuth apps, and how plan limits are billed.
Cloud has no free plan. New workspaces start a 7-day trial (no credit card required to explore). After the trial, an active Stripe subscription is required to keep scheduling on the hosted product.
Self-hosted installs skip that gate when Stripe is unset — see Stripe billing.
Cloud vs self-hosted
| OpenQuok Cloud | Self-hosted | |
|---|---|---|
| Plans and limits | Enforced per plan through Stripe | Stripe unset: billing UI disabled; subscription guards do not run |
| Channel connect | Pre-registered OAuth apps — click Connect and authorize | You register each provider app and supply keys |
| Trial | 7 days, no card to start | Not applicable |
| Billing | Stripe Checkout and Customer Portal at /account/billing | Not applicable unless you configure Stripe yourself |
| Support | Discord plus the refund policy | Community Discord; you operate the stack |
| Updates | Applied on the hosted service | You upgrade when you choose |
| Data location | Hosted by OpenQuok | Your infrastructure |
Same product, different operator
Calendar, composer, kanban, CLI, MCP, and the public API work the same on Cloud and self-host. How to use those surfaces lives in the Guide. This section is trial, plans, billing, and limits.