Squidex

Squidex is an open-source, self-hostable headless CMS (Content Management System) that serves structured content through a rich HTTP API.

  • Development
  • Web & Publishing
Squidex is an open-source, self-hostable headless CMS (Content Management System) that serves structured content through a rich HTTP API. You define content types, create content in a web administration interface, and publish once to websites, mobile apps, or server applications. It suits developers who want a free, MIT-licensed, API-first content hub with built-in version history and no vendor lock-in.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

70/100 Good

Maintained
100last commit 1 day ago
Popular
682,517 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
59no serious findings, 18 minor, CI, tests, OpenSSF Scorecard 4.3/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
2,517
Open issues
5
Last commit
2026-11-21
Latest release
7.24.0
License
MIT
Activity
rising

Checked today - source: GitHub (Squidex/squidex)

Resources & Compatibility

Requirements not published yet.

Checked today - source: Docker Hub image tags and published docs

First-install notes

  • Docker settings must exist first Before starting Squidex with Docker Compose (a tool that starts Docker containers), make sure the docker-compose.yml and .env (settings) files are downloaded and configured, then run docker-compose up -d. If these files are missing or empty, Squidex won't start with the right configuration. source
  • Install Docker on the cloud server If you are using an AWS EC2 server (a remote computer in Amazon's cloud), install Docker and add your user to the docker group, then log out and log back in before Squidex setup. This permission step is what lets your account run Docker commands without access errors. source
  • Run the AWS setup script After Docker is ready on that server, run /opt/squidex/setup-squidex.sh and answer the prompt for your domain. This starts the Squidex Docker setup for you; skipping it can leave the service unconfigured or not running. source
  • Getting help Setup questions, feature requests and bug reports go to the official Squidex support forum (support.squidex.io); the project README points new users there. source

Fetched today - each note links to its source

Alternatives (4)

  • Cockpit - Cockpit is a lightweight web-based server administration interface for Linux hosts, used by sysadmins to manage storage, networking, contai…
  • Contentful
  • Sanity.io - Sanity is a hosted backend for structured content with a real-time API, globally distributed CDN, and a powerful, but simple query language.
  • Strapi - Strapi is an open-source headless CMS that turns visual content models into ready-to-use APIs, letting developers build content-powered app…

Checked today - source: AlternativeTo

Common questions

What must be prepared before starting Squidex with Docker Compose?

The docker-compose.yml and .env files must be downloaded and configured first. If they are missing or empty, Squidex will not start with the right configuration.

Why might Docker commands fail on AWS EC2 after installing Docker?

Add the user to the docker group, then log out and log back in before Squidex setup. This permission step lets the account run Docker commands without access errors.

Do I need a reverse proxy when self-hosting Squidex on a small server?

Most people deploy it on a small server with Docker and a reverse proxy for HTTPS.

Answers sourced from github.com, github.com, opentools.dev

Community

Collected today - public community threads