
# Content management & CMS on Render

Compare documented Content management & CMS deployments on Render, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/render/content-management/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: Render workspace, project and services; platform-managed infrastructure
- Provider group: application-platform
- Provider classification: Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Source: https://render.com/docs/deploys (checked 2026-11-20).
- Network: Private services with separately exposed public endpoints
- Identity and access: Workspace membership and deployment credentials
- Installation guidance: Deploy application services and databases using a Blueprint or Docker/source build; configure persistent disks, secrets and recovery.
- Guidance source: https://render.com/docs/deploys
- Guidance reviewed: 2026-11-12


### Private networking

Services in the same region can use Render private networking. Free web services can send but cannot receive private-network requests. Review the actual paid service and endpoint requirements.
Source: https://render.com/docs/private-network (reviewed 2026-11-14).

The listings below have evidence for Render. Read each cloud evidence note for the applicable package, edition and support qualifications.

1 listing.


## Squidex

Self-hosted headless CMS with structured content, APIs and assets.

- Listing: https://launchinyourcloud.com/directory/squidex/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, render, heroku, vultr
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Squidex application, database and asset storage using provider-specific instructions.
- Operations: 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.
- Product website: https://squidex.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.

MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Squidex application, database and asset storage using provider-specific instructions. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Self-hosted headless CMS with structured content, APIs and assets.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-aws-ec2 (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-azure (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-gcp (checked 2026-11-19). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-render (checked 2026-11-19). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-heroku (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-vultr (checked 2026-11-19). 


### Cloud deployment evidence

- AWS EC2 Guide (aws): https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-aws-ec2
  Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Guide (azure): https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-azure
  Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP Guide (gcp): https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-gcp
  Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Render Guide (render): https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-render
  Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Install on Heroku | Squidex (heroku): https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-heroku
  Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Install on Vultr | Squidex (vultr): https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-vultr
  Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

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

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/Squidex/squidex/graphs/contributors

- Upstream project: https://github.com/Squidex/squidex

### Sources

- AWS EC2 Guide: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-aws-ec2

- Azure Guide: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-azure

- GCP Guide: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-gcp

- Render Guide: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-render

- Install on Heroku | Squidex: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-heroku

- Install on Vultr | Squidex: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-vultr

- MIT LICENSE: https://github.com/Squidex/squidex/blob/master/LICENSE

- Releases v7.24.0: https://github.com/Squidex/squidex/releases

### Licensing sources

- https://github.com/Squidex/squidex/blob/master/LICENSE

### Infrastructure sources

- https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-aws-ec2

- https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-azure

- https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-gcp

- https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-render

- https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-heroku

- https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-vultr


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The official external-identity guide documents configuring an external Azure AD/OAuth identity provider for self-hosted Squidex. The Compose example also exposes Google/GitHub/Microsoft credentials. The separately documented Squidex.Identity project is deprecated and must not be presented as a maintained SSO service. Scope: Self-hosted Squidex external-provider configuration; not the deprecated Squidex.Identity server. Source: https://docs.squidex.io/id-01-getting-started/installation/external-identity-providers (reviewed 2026-11-20). Supporting source: Upstream Compose identity configuration — https://raw.githubusercontent.com/Squidex/squidex-hosting/master/docker-compose/docker-compose.yml.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream hosting repository supplies a Compose stack with Squidex 7, MongoDB 6 and a Caddy proxy, persistent mounts and environment-based identity settings. These moving examples need compatible supported image versions, secrets and backups; the stack is not a replicated database/HA design. Scope: Upstream Squidex 7 Compose example; assess database support and image versions separately. Source: https://raw.githubusercontent.com/Squidex/squidex-hosting/master/docker-compose/docker-compose.yml (reviewed 2026-11-20). Deployment artifact: https://github.com/Squidex/squidex-hosting/tree/master/docker-compose. Artifact reference: master (moving branch); Squidex major 7 / MongoDB major 6 in reviewed example.

- Minimum footprint / sizing: Sources checked — unresolved. The official Compose stack establishes application, MongoDB and proxy dependencies, but no quantitative CPU/RAM/storage production floor was established in the reviewed installation materials. Confirm content volume, database replication, caches and concurrency before sizing. Scope: Upstream deployment topology; no workload-tested minimum established. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-docker (reviewed 2026-11-20). Supporting source: Reviewed Compose services — https://raw.githubusercontent.com/Squidex/squidex-hosting/master/docker-compose/docker-compose.yml.

- License pricing: Documented. MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Squidex; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/Squidex/squidex/blob/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 7.24.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Squidex upstream application; verify compatibility with the selected package. Source: https://github.com/Squidex/squidex/releases/tag/7.24.0 (reviewed 2026-11-19).






