Squidex
Self-hosted headless CMS with structured content, APIs and assets.
8 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Application platform deployment
Runs in
Documented customer environment
Squidex application, database and asset storage using provider-specific instructions.
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- Render: Customer platform workspace
- Heroku: Customer platform workspace
- Vultr: Customer cloud account
- AWS
- Azure
- Google Cloud
- Render
- Heroku
- Vultr
Servers / containers
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.
AWS EC2 Guide ↗ · Source checked 2026-11-19
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Azure Guide ↗ · Source checked 2026-11-19
- 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.
GCP Guide ↗ · Source checked 2026-11-19
- Render: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Render Guide ↗ · Source checked 2026-11-19
- Heroku: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Install on Heroku | Squidex ↗ · Source checked 2026-11-19
- Vultr: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Install on Vultr | Squidex ↗ · 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 method | Application platform deployment |
|---|---|
| Infrastructure | Servers / containers 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. |
| Licensing model | Open Source / Open Core MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
| License | MIT 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.
5 of 12 fields researched (42%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
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.
Self-hosted Squidex external-provider configuration; not the deprecated Squidex.Identity server · Source ↗ · Upstream Compose identity configuration ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
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.
Upstream Squidex 7 Compose example; assess database support and image versions separately · Source ↗ · Deployment artifact ↗ (master (moving branch); Squidex major 7 / MongoDB major 6 in reviewed example) · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
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.
Upstream deployment topology; no workload-tested minimum established · Source ↗ · Reviewed Compose services ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Squidex; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
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.
Squidex upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19
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
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.
Community & 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.
Category fit
- Content management & CMS
- Self-hosted headless CMS with structured content, APIs and assets.
Compare within Content management & CMS
- ApostropheCMSCustomer-operated content management and website application framework.
- Heroku
- Cockpit CMSSelf-hosted structured content and API management application.
- Railway
- 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
- CrafterCMSSelf-hosted content authoring and delivery platform.
- AWS
- Directus Self-HostedSelf-hosted content and data management with APIs over your SQL database.
- Railway
- dotCMS Cloud AnywhereVendor-operated content platform deployed into a customer cloud account.
- AWS
- Azure
- Google Cloud
- DrupalOpen-source content management system for building and operating websites.
- AWS
- Ghost Self-HostedOpen-source publishing and membership CMS with documented customer-operated Linode and DigitalOcean deployments.
- DigitalOcean
- Linode
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
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- AWS EC2 Guide ↗docs.squidex.io
- Azure Guide ↗docs.squidex.io
- GCP Guide ↗docs.squidex.io
- Render Guide ↗docs.squidex.io
- Install on Heroku | Squidex ↗docs.squidex.io
- Install on Vultr | Squidex ↗docs.squidex.io
- MIT LICENSE ↗github.com
- Releases v7.24.0 ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- AWS EC2 Guide ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Azure Guide ↗ · Azure
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- GCP Guide ↗ · Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Render Guide ↗ · Render
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Install on Heroku | Squidex ↗ · Heroku
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Install on Vultr | Squidex ↗ · Vultr
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- AWS EC2 Guide ↗ · AWS
- Infrastructure evidenceChecked
- docs.squidex.io/id-01-getting-started/installation/platforms/in … ↗
- docs.squidex.io/id-01-getting-started/installation/platforms/in … ↗
- docs.squidex.io/id-01-getting-started/installation/platforms/in … ↗
- docs.squidex.io/id-01-getting-started/installation/platforms/in … ↗
- docs.squidex.io/id-01-getting-started/installation/platforms/in … ↗
- docs.squidex.io/id-01-getting-started/installation/platforms/in … ↗
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Community, governance or adoption evidence ↗github.com
- Upstream project ↗github.com