Strapi Self-Hosted

Headless CMS for managing structured content and delivering it through APIs.

5 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Node.js production deployment with a supported SQL database; container/Kubernetes options

  2. Operated by

    Your team

    Customer operates application servers, database, media storage, backups and upgrades.

Deployment boundaries by provider
  • AWS: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Strapi self-hosting compatibility ↗ · Source checked 2026-11-12

  • Azure: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Strapi self-hosting compatibility ↗ · Source checked 2026-11-12

  • Google Cloud: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Strapi self-hosting compatibility ↗ · Source checked 2026-11-12

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodNode.js production deployment with a supported SQL database; container/Kubernetes options
InfrastructureServers / containers
Classified for the documented long-running Node.js application/server deployment with a database; headless APIs do not imply a function-based or static-only deployment.
Licensing modelOpen Source / Open Core
The broad self-hosted listing includes the MIT core and separately licensed Enterprise feature code under ee/ directories; paid hosting alone is not the reason for this classification.
LicenseMIT core; commercial Growth/Enterprise features and terms differ

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
Edition-dependentEvidence and scope for Single sign-on

The self-hosted pricing page offers SSO as a paid Growth add-on and includes it in Enterprise. The listed identity options include SAML 2.0 and OAuth2 providers; Community does not gain those entitlements.

CMS self-hosted admin-user authentication; paid-plan/add-on scope · Source ↗ · Reviewed 2026-11-20

Edition-dependent · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The Strapi 5 Docker guide supplies development/production Dockerfile and Compose examples for building your own application image. Strapi explicitly does not publish an official container image; do not label a third-party image as upstream-supported.

Upstream courtesy examples for a custom Strapi 5 project · Deployment artifact ↗ (Current Strapi 5 Dockerfile/Compose examples; pin project dependencies and base images) · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The deployment guide lists a minimum of 1 CPU core, 2 GB RAM and 8 GB disk, with 2+ cores, 4 GB+ and 32 GB+ recommended. Database and workload sizing remain separate.

Strapi deployment-guide baseline; not an end-to-end infrastructure bill · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

Community is free under MIT. Growth is listed at $45/month including three admin users, with additional users at $15/month. SSO is a separate priced add-on; Enterprise is quoted. Hosting is separate.

Self-hosted CMS software plans; not Strapi Cloud hosting · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

Strapi v5.63.0 was published November 18, 2026. It changes invalid-filter, array-limit, null, locale-permission, and AI-job behavior; test queries and rolling upgrades before rollout.

Upstream Strapi 5 release · Source ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Show all fields (7 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

This entry covers self-hosted Strapi, not Strapi Cloud. Review workflows, audit logs and other editorial controls are plan-dependent. Confirm supported database/runtime versions and storage requirements for the selected release. Strapi 5.62.0, released November 12, 2026, includes a security patch whose detailed disclosure was delayed to allow operators time to upgrade. It also changes invalid boolean-filter handling, so self-hosted operators should review compatibility and upgrade promptly. Strapi v5.63.0 changes filter behavior: invalid or previously dropped conditions now return errors or no results, arrays are limited to 100 items, null semantics change, locale permissions are not automatically restored, and AI jobs require rolling-upgrade care. Test existing queries, permissions, and mixed-version nodes before rollout.

Category fit

Content management & CMS
Headless content management with content modeling, editorial administration and APIs; paid governance features depend on plan.

Compare within Content management & CMS

  • ApostropheCMSCustomer-operated content management and website application framework.
    • Heroku
    Customer-operated · Open Source / Open Core
  • Cockpit CMSSelf-hosted structured content and API management application.
    • Railway
    Customer-operated · Open Source / Open Core
  • Confluence Data CenterCommercial self-managed Confluence edition for enterprise collaboration and knowledge management. New Data Center subscriptions are restricted to eligible existing Atlassian customers.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • CrafterCMSSelf-hosted content authoring and delivery platform.
    • AWS
    Customer-operated · Open Source / Open Core
  • Directus Self-HostedSelf-hosted content and data management with APIs over your SQL database.
    • Railway
    Customer-operated · Source Available
  • dotCMS Cloud AnywhereVendor-operated content platform deployed into a customer cloud account.
    • AWS
    • Azure
    • Google Cloud
    Vendor-operated BYOC · Commercial Only
  • DrupalOpen-source content management system for building and operating websites.
    • AWS
    Customer-operated · Open Source / Open Core
  • Ghost Self-HostedOpen-source publishing and membership CMS with documented customer-operated Linode and DigitalOcean deployments.
    • DigitalOcean
    • Linode
    Customer-operated · Open Source / Open Core

Showing 8 of 25 other listings in Content management & CMS. These products address related workflows; read their category-fit notes before comparing scope. See all of Content management & CMS →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Strapi self-hosting compatibility ↗ · AWS, Azure, Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      The vendor explicitly identifies AWS, Azure and Google Cloud for self-hosted Strapi. This is its Node.js application in customer infrastructure, not Strapi Cloud; production database, backups and updates remain customer responsibilities.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory