dotCMS Cloud Anywhere

Vendor-operated content platform deployed into a customer cloud account.

4 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

    Cloud Anywhere onboarding and vendor management through customer-cloud access roles

  2. Operated by

    Vendor or service partner

    Vendor operates the Cloud Anywhere application through its management plane and scoped customer-cloud access; agree support access, logs, egress and exit procedures.

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

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

    Cloud Anywhere Quickstart ↗ · Source checked 2026-11-19

  • Azure: Customer cloud account · Vendor / partner-operated

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

    Cloud Anywhere Quickstart ↗ · Source checked 2026-11-19

  • Google Cloud: Customer cloud account · Vendor / partner-operated

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

    Cloud Anywhere Quickstart ↗ · Source checked 2026-11-19

dotCMS provisions and operates Cloud Anywhere through its automation and delegated access to a dedicated customer account, subscription or project. The separately customer-operated self-hosted edition is outside this listing.

Operating responsibility source ↗ · Checked 2026-11-20

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

Install methodCloud Anywhere onboarding and vendor management through customer-cloud access roles
InfrastructureServers / containers
dotCMS Cloud Anywhere tenant with vendor Lighthouse management and customer cloud access roles. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.
Licensing modelCommercial Only
Commercial dotCMS Cloud Anywhere service terms; the public core-code licence does not grant service entitlements.
LicenseCommercial dotCMS Cloud Anywhere service terms; the public core-code licence does not grant service entitlements.

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%) · 3 documented · 1 unresolved. Evidence coverage is not a feature score.

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

The current dotAuth guide documents system/site SSO settings for OAuth2/OIDC and SAML, including separate redirects for site and administrator login. Validate the selected service plan, release and identity mapping; site inheritance is not the same as configuring every redirect at the IdP.

Current dotCMS application authentication; Cloud Anywhere service entitlement/version must be confirmed · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

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

Official container guidance provides Docker and multi-service Compose examples with persistent data volumes. The developer all-in-one image is for local evaluation; it is not the Cloud Anywhere managed-service architecture or a production HA baseline.

Upstream application container examples; selected managed deployment follows its separate contract · Deployment artifact ↗ (Current reference examples; pin a supported application and backing-service release) · Reviewed 2026-11-20

Documented · Editor reviewed.

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

The standard-stack requirements specify a multicore processor, dedicated 8+ GB RAM and 100 GB disk, with PostgreSQL and OpenSearch dependencies. These application-stack requirements do not size a contracted Cloud Anywhere topology or validate 100-user/1-TB HA capacity.

Upstream standard-stack baseline; managed-service deployment sizing is separate · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
Not confirmedEvidence and scope for License pricing

The public core-code licence does not establish the Cloud Anywhere managed-service price, order or operating/support entitlements. Obtain the agreement for the customer-cloud service.

Selected self-managed application or customer-cloud service; contract confirmation required · Source ↗ · Reviewed 2026-11-19

Sources checked — unresolved · 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 vendor operates the installation through its control plane and AWS role or GCP service account. Public core code and Cloud Anywhere service licensing are different; this is not a fully customer-operated instance.

Category fit

Content management & CMS
Vendor-operated content platform deployed into a customer cloud account.

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
  • 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
  • GravSelf-hosted flat-file content management system.
    • AWS
    • DigitalOcean
    • Linode
    • Vultr
    • Hostinger
    • LumaDock
    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.

    • Cloud Anywhere Quickstart ↗ · AWS, Azure, Google Cloud

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

      dotCMS Cloud Anywhere tenant with vendor Lighthouse management and customer cloud access roles. The vendor operates the installation through its control plane and AWS role or GCP service account. Public core code and Cloud Anywhere service licensing are different; this is not a fully customer-operated instance.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory