Overview - OpenQuok Cloud
Comaprison between Cloud hosted Paid Plan vs self-host free plan.
Connect your agent today
Draft from chat, review in your calendar, and publish only what you approve.
OpenQuok Cloud
What the hosted product gives you, and how it differs from running OpenQuok yourself.
OpenQuok Cloud is the same application you can run on your own servers. You use it at openquok.com. The features match self-hosting: calendar, composer, agents, CLI, MCP, and the public API.
The difference is who does the work. On Cloud, OpenQuok runs the hosted stack, registers the social developer apps, and enforces limits from your plan.
You connect channels and schedule posts. You do not manage database(including Redis and supabase), workers, CLI Auth/MCP servers or maintain OAuth keys/ API integration with different social platforms.
There is no free plan
On Cloud, a workspace without a paid subscription cannot use the scheduler. New accounts see the plan until they subscribe or start a free trial.
Most new workspaces can use a 7-day trial instead. You can explore without a credit card. When the trial ends, you need an active subscription to keep scheduling.
Self-hosting does not use this gate. If you run OpenQuok yourself and leave Stripe unset, there is no hosted paywall. You operate the server, backups, and social apps.
Tip
Read Self-host OpenQuok for paths and cost, or Installation for step-by-step docs. Operators who enable Stripe on their own instance can bill workspaces the same way Cloud does — Stripe billing.
Cloud vs self-hosted
| OpenQuok Cloud | Self-hosted | |
|---|---|---|
| Plans and limits | Enforced per plan through Stripe | Stripe unset: billing UI off; guards do not run |
| Channel connect | Pre-registered OAuth — click Connect and authorize | You register each provider app and supply keys |
| Trial | 7 days for eligible accounts | Not applicable |
| Billing | Stripe at /account/billing | Not applicable unless you configure Stripe |
| Support | Email, Discord, and refund policy | Community Discord; you operate the stack |
| Updates | Applied on the hosted service | You upgrade when you choose |
| Source code | OpenQuok runs the hosted build and ships updates. We maintain the product; you do not patch the hosted servers. | open source on GitHub (AGPL-3.0-or-later). You may change the code for your instance. You apply upgrades at your own risk. |
| Data location | Hosted by OpenQuok | Your infrastructure |
Warning
You may run OpenQuok as a service for your customers/others. The license is AGPL-3.0-or-later. If you offer OpenQuok (or a modified version), you must release your source under the same license. You cannot ship a closed proprietary fork. See the repository and the LICENSE file for the full terms.
Tip
Calendar, composer, CLI, MCP, and the public API behave the same on Cloud and self-host. How to use the product is in the Guide.