Plans and limits

On hosted vibecms every blog starts on the free plan. The free plan includes:

• 5 published posts
• 5 drafts at a time
• 10 images
• Agent keys, with 300 requests a day and 1,000 a month; writes are limited to 50 a day and 200 a month
• Unlimited version history
• A small “Published with vibecms” link at the bottom of every blog page

vibecms Cloud includes unlimited posts, 10 GB of media, analytics, a custom domain or subpath location, search indexing, no “Published with vibecms” link, and 5,000 agent requests a day. Agent requests are limited to 120 a minute, writes to 500 a day, and each key to 60 requests a minute, with no monthly cap (see API limits). Free-plan blogs serve pages with noindex, so search engines skip them. Self-hosted installs never show the link. Prices live on the pricing section of the site and are not repeated here.

Upgrade and manage

Open Dashboard > Settings > Plan & billing. The owner sees the current plan, the full allowance table, and Upgrade / Yearly checkout buttons. Once subscribed, Manage subscription opens the billing portal for payment details and cancellation; Invoices and payment details appears for past customers. Leaving checkout or the portal brings you back to Plan & billing. Checkout and the portal are owner-only actions — editors see “Only the owner can change the plan.”

Each blog has its own subscription. One person can pay for several blogs with the same email; the billing portal then lists every subscription paid with that email, including other products from the same seller. If one blog is paid for twice by mistake (for example two checkouts open in two tabs), it stays on the first subscription and support refunds the second.

Dashboard Upgrade to Cloud links open Plan & billing in a new tab, so unsaved writing stays in the editor without a discard prompt.

Canceling and failed payments

Canceling in the billing portal schedules the end of the subscription: the plan stays paid until the end of the current billing period, and Plan & billing shows Ends with that date instead of Renews. After it ends, the free plan applies and checkout is available again.

If a renewal payment fails, the subscription is past due and paid features stay on for a 7-day grace period from the first failed payment. Every dashboard page shows “Your last payment failed. Paid features stay on until date.” with Update payment, which opens the billing portal to fix the payment method; editors see a note to ask the owner instead. Starting a new checkout is not offered while a payment is past due.

The grace clock starts with the first accepted past-due notification and does not restart on repeated failures. If notifications are delayed while our endpoint is failing, the clock can start later, extending grace by at most that delay. Older or duplicate notifications never change the current clock. Legacy past-due subscriptions with an unknown failure date receive no retroactive grace. An accepted successful payment, including a completed checkout, ends that past-due episode; a later failed payment starts a new grace period.

If the payment is still failing when the grace period ends, the free plan applies (see below) and the notice changes to “Your last payment failed. Paid features are paused.” Nothing is deleted, including custom domain and subpath location settings. Once the payment goes through, the subscription is active again and paid features return immediately. A subscription that ends — canceled, unpaid after the retries run out, or revoked — drops to the free plan with no grace period.

When paid access ends

Nothing is deleted. Posts stay online and the blog keeps working, but paid features pause: the analytics dashboard and API lock and people-view collection pauses (server-side agent-read counting continues on the still-readable default-domain blog), custom domains and subpath locations stop serving, pages get noindex again, and free-plan limits apply once more. Posts over the free published limit stay published; the cap only blocks new publishes beyond five.

Actions that need an active plan fail with distinct codes — the same over REST and in the MCP tool error result: publishing past the free cap or adding a draft past five → BILLING_REQUIRED; reading analytics → ANALYTICS_PAID_PLAN; uploading past the free image count → media_quota_free; uploading past paid storage → media_quota_paid. Resubscribing unlocks everything again; a paused custom domain returns when the plan is active.