Plone

Self-hosted enterprise content management and publishing platform.

3 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

    CloudFormation; Docker / Compose; Application platform deployment

  2. Operated by

    Your team

    Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.

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.

    plone-in-a-box ↗ · Source checked 2026-11-19

  • Linode: Customer cloud account · Customer-operated

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

    plone-in-a-box ↗ · Source checked 2026-11-19

  • DigitalOcean: Customer cloud account · Customer-operated

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

    plone-in-a-box ↗ · Source checked 2026-11-19

  • Hetzner: Customer cloud account · Customer-operated

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

    plone-in-a-box ↗ · Source checked 2026-11-19

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

Install methodCloudFormation; Docker / Compose; Application platform deployment
InfrastructureServers / containers
Plone 6 backend, Volto frontend, database and persistent assets via plone-in-a-box. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.
Licensing modelOpen Source / Open Core
GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseGNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

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.

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

Single sign-on
AvailableEvidence and scope for Single sign-on

The community pas.plugins.oidc add-on documents OpenID Connect authentication for Plone. This is an add-on integration rather than a universal core entitlement; validate its Plone/backend/front-end compatibility and provider mapping for the selected deployment.

Maintainer documentation for a Plone PAS OIDC add-on · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

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

Cookieplone is the upstream-recommended project generator and creates the selected Plone backend/frontend project. It supplies an application project/deployment workflow, not an automatically hardened cloud-account infrastructure stack.

Plone 6 Cookieplone project generation; Classic and Volto variants have different requirements · Source ↗ · Deployment artifact ↗ (Moving generator repository; select compatible pinned template/dependency versions) · Reviewed 2026-11-20

Documented · Editor reviewed.

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

The Plone 6 guide recommends 2 GB or more RAM per site and 40 GB or more disk. Volto frontend installation needs at least 2 GB RAM; lower backend process minima and swap figures are not whole-stack sizing. Addons, caches, builds and HA require additional resources.

Rough upstream Classic/Volto requirements, not a 100-user/1-TB HA benchmark · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Plone; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (8 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.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

The community provides provider-specific deployment examples; foundation governance does not imply a commercial support contract for those recipes.

Community & maintenance

The reviewed upstream contributor history includes mauritsvanrees, jensens, vangheem, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Category fit

Content management & CMS
Self-hosted enterprise content management and publishing platform.

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.

    • plone-in-a-box ↗ · AWS, Linode, DigitalOcean, Hetzner

      Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      Plone 6 backend, Volto frontend, database and persistent assets via plone-in-a-box. The community provides provider-specific deployment examples; foundation governance does not imply a commercial support contract for those recipes.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory