GraphQL and REST are usually treated as an either/or decision made once, at the start of a project. Comparing them on payload shaping, reference resolution, caching, tooling and error handling shows that the honest answer differs per request, and that mixing both in one application is a reasonable design rather than a failure of discipline.
Squidex 7.22.0 and 7.23.0 brought a simpler way to make string fields searchable, resolvable comments with a dedicated view, HTTP requests from scripts, and an upgrade to .NET 10 and Angular 21. The follow-up release added SSRF protection for asset downloads and scripting HTTP clients.
Integrate Squidex seamlessly to your tech stack. With its headless architecture and robust API, it provides the freedom to define your schemas, choose your tools, and deliver content across multiple platforms.
Version 7.21.0 shipped in Q3 2025 with AI-assisted schema generation, support for FerretDB as a database backend, an inline filter in the content list and the X-Fields header on all content endpoints. Here is what each of those changes means when you build or operate a Squidex installation.
Squidex 7.19.0 replaces rule actions with a new flow system, adds a cron trigger, JSON response compression and persistent AI chat history. This is what changed in the second quarter of 2025, including the one migration detail you should check before you upgrade.
Squidex 7.18 adds early support for MySQL, Postgres and SQL Server as storage backends, and slims down the official container by moving ImageMagick and Kafka behind build flags. This update walks through what changed in Q1 2025, what you need to do if you relied on the removed libraries, and which search and identity bugs were fixed.
Squidex 7.16.0 adds APIs and a UI to define indexes for content collections, extends scripting with content queries and non-JSON request bodies, and ships OpenTelemetry exporters for logs and metrics. Several editors in the UI were simplified and mentions in comments now have autocompletion.
Two releases shipped in Q3 2024: 7.14.0 and 7.15.0. They add article and image generation with OpenAI and Dall-E, ARM Docker images, custom OIDC servers for teams, new content update statements and control over field enrichment, plus an update of the management UI to Angular 18.
New editor for markdown and rich text has been released. Sets the foundation for new collaborative features coming soon.
Two releases shipped in the first quarter of 2024, 7.12.0 and 7.13.0. The largest change is a new job system that puts rules and backups on shared background infrastructure, with notifications when a job finishes, alongside fixes to comments, the Rich Editor, full text search and the API.
I am happy to share a couple of new and improved features and give you some guideline how to leverage them.
Empower your content strategy with Squidex, the ultimate Headless CMS: Master advanced customization and seamless integration.
The hopefully last release candidate for 7.0 has been released and this is a good moment to introduce the new changes of this major version. This version has been battle tested with existing databases and a lot of new API tests that also covers areas of the product that have not been tested automatically yet.
A new feature has just been landed that allows content embedding into text fields such as markdown or rich-text.
Notifo is a general purpose notification framework. It has been developed for Squidex to be able to subscribe to changes for a single content item or schema, contributors or whatever you are interested in and to get push notifications when something changes. It is Open Source and available for everybody now.
By default a headless CMS is very decoupled from the frontends. This makes it much harder for your content editors, because they lack in understanding where a content is used. The main problem is that the frontend is not controlled by the headless CMS. Therefore integrated editing features are hard to implement. But Squidex has some features to make the live easier for your content editors.
Squidex performance is mainly driven by external services like MongoDB. To improve scalability it is important to keep CPU work low. Therefore a small microservice has been introduced to outsource image resizing.
I get a lot of questions from people over different channels. Some users write me emails with technical questions, other use skype or slack or github issues. And most of the time I write the following answer:
Dear User, Please understand that we only give support over the community forum. Please open a support ticket there and it will be answered as soon as possible.
In this blog post I want to explain the reasons behind that.
A headless CMS is very similar to a database. It provides an API and user interface to manage your content of course you can also retrieve the content using. In almost every use case you want to apply a filter to only query the content items you actually need. The question is: How fast are these queries and filters?
January 2021 is packed with a lot of small and bigger improvements. One of the highlights is the support for geo searches for geolocation fields. In this blog post, I will showcase the most important improvements.