Squidex

Headless CMS, based on MongoDB, CQRS and Event Sourcing.

Slowing · 38
38/100
Slowing

Activity has dropped noticeably. Check the repository before committing to it.

Maintenance 8/40
Releases 16/25
Community 11/20
Momentum 4/15

Commit activity more than 19% of tracked projects; popularity more than 54%. How this is calculated.

Commits, last 11 months

2025-10: 8 commits 2025-11: 3 commits 2025-12: 2 commits 2026-01: 4 commits 2026-02: 10 commits 2026-03: 6 commits 2026-04: 10 commits 2026-05: 5 commits 2026-06: 1 commits 2026-07: 3 commits 2026-08: 3 commits
2025-10 55 total 2026-08
Stars2.5k
Latest release7.23.0 · 16 Apr 2026
Repo updated27 Sept 2026
LicenceMIT
Built with.NET

Is Squidex actively maintained?

Over the last 11 months the project absorbed 55 commits, of which 7 arrived in the most recent quarter — roughly 2 commits a month.

Activity is cooling: commits are down 67% against the previous quarter. One slow quarter is normal; two in a row is a signal.

The most recent tagged release, 7.23.0, is about 6 months old.

Squidex ranks #37 of 48 tracked content management systems (cms) projects. Several better-maintained options exist in the same category — they are listed below.

What Squidex actually does

Squidex is a headless content management system that relies on MongoDB, command query responsibility segregation, and event sourcing. It provides a backend interface to store and manage structured content, which you can then distribute to various front-end applications via an API. The platform is written in .NET and distributed under an MIT licence.

Best fit: It suits teams that are already invested in the .NET ecosystem and require a structured content repository with audit trails powered by event sourcing.

Worth knowing: The moderate development activity and dependency on both MongoDB and event-sourcing architectures mean you should anticipate a steeper operational and debugging curve than with traditional database-backed CMS options.

Deployment notes

You will typically need to provision a separate MongoDB instance, configure persistent storage for your data, and place the application behind a reverse proxy to handle TLS termination.


Alternatives to Squidex

Projects in the same categories, ordered by health score.