Strapi Cloud hosting vs separate CMS licensing — what do I need to change?

Teams adopting Strapi need to decide whether self-serve Cloud is actually enough, because paid CMS capabilities such as SSO and workflows are now clearly split from Cloud hosting plans and can change the total cost materially.

Use Strapi Cloud hosting only if Community features are enough; add Growth only when collaboration or governance needs clearly outweigh per-seat CMS cost.

Blockers

Who this is for

Candidates

Use Strapi Cloud hosting only

As of 2026-03-30, Strapi Cloud is explicitly a hosting-only product. Strapi’s January 13, 2026 billing clarification states that even paid Cloud plans do not include paid CMS capabilities, and those require a separate CMS Growth or Enterprise license. Official docs show one Free plan and three paid hosting plans: Essential, Pro, and Scale. The December 22, 2025 pricing update added yearly billing with a 20% discount for Cloud hosting only, and says paid Cloud starts at "$18/month" or "$15/month" billed yearly.

When to choose

Use this when you mainly want managed Strapi hosting with low ops and you do not need paid CMS collaboration or security features. It is the right fit if Community Edition features are sufficient and the decisive factor is avoiding per-seat CMS spend.

Tradeoffs

Lowest commitment and simplest procurement for managed hosting, but no paid CMS features are unlocked by the hosting subscription alone. You still pay overages for API requests, asset bandwidth, and asset storage on paid plans.

Cautions

As of 2026-03-30, this split has already occurred. Free Cloud is personal, non-commercial use only, scales to zero, and can be suspended when free limits are exceeded. Current docs list Free at 2,500 API requests/month and Essential at 50,000 for new subscriptions after the December 22, 2025 change. Overages on paid Cloud are billed at "$1.50 / 25k requests", "$30.00 / 100GB" bandwidth, and "$0.60 / GB per month" storage.

Sources

Use Strapi Cloud plus a separate CMS Growth license

As of 2026-03-30, this is the main self-serve path if you need paid CMS capabilities while staying on Strapi Cloud. Strapi’s January 15, 2025 pricing announcement puts Growth at "$15/month per seat" and positions it for advanced collaboration and publishing, including Releases and Content History with 30-day retention. The January 13, 2026 support clarification confirms this CMS license must be purchased separately from Cloud hosting and then linked to the Cloud project. Strapi’s December 22, 2025 FAQ also says yearly billing currently applies only to Cloud hosting plans, while Growth remains monthly.

When to choose

Use this when you want managed hosting plus paid CMS features for a growing team, but do not need full enterprise procurement. It is the decisive option when Community is insufficient and the extra per-seat CMS cost is still acceptable.

Tradeoffs

You keep Cloud’s low-ops hosting model and add collaboration features incrementally, but total cost becomes the sum of hosting plus per-seat CMS licensing. Billing is split across two products, so Cloud annual discounts do not reduce the Growth license cost.

Cautions

Applying or changing a CMS license key on Strapi Cloud triggers a new deployment and can temporarily slow or interrupt requests. Premium UI tags can still appear after activation even when the licensed feature is working normally.

Sources

Use Strapi Cloud plus Growth and the SSO add-on, or move to Enterprise

As of 2026-03-30, SSO is not included in self-serve Cloud hosting and is not unlocked unless you also buy the CMS-side entitlement. Strapi’s January 15, 2025 pricing announcement says the SSO add-on costs "$50/month per seat" for teams on Growth, while Enterprise remains custom-priced and includes SSO with 365-day content history. The January 13, 2026 clarification lists SSO among the paid CMS capabilities that remain separate from Cloud hosting plans. This means identity and compliance-driven teams should treat hosting and CMS licensing as separate budget lines from the start.

When to choose

Use this when the blocker is centralized identity, stronger governance, or enterprise support rather than just managed hosting. The decisive factor is whether SSO and longer retention justify either the Growth-plus-add-on stack or a move to Enterprise.

Tradeoffs

You get the security and governance features missing from Cloud-only adoption, but cost rises quickly because the spend is seat-based on the CMS side and still separate from hosting. Enterprise may simplify packaging, but official pricing is custom rather than transparent self-serve.

Cautions

Do not assume buying Pro or Scale Cloud unlocks SSO, workflows, or other premium CMS capabilities. As of 2026-03-30, that assumption is explicitly contradicted by Strapi’s billing documentation.

Sources

Facts updated: 2026-03-30
Published: 2026-04-03

Related questions

Try with your AI agent

$ npm install -g pocketlantern
$ pocketlantern init
# Restart Claude Code, Cursor, or your MCP client, then ask:
# "Strapi Cloud hosting vs separate CMS licensing — what do I need to change?"
Missing something? Request coverage