Squidex

What Squidex is

Squidex is an open source headless CMS for developers and the content teams they build for. The company's headline is "how modern companies manage content," and its pitch is one platform where you "create once, publish everywhere" to apps, websites and server applications. Content lives behind an API rather than inside a theme, so a blog, a product catalog or an internal tool can all read from the same place.

It is MIT licensed and runs on .NET. The comparison page lists the tech stack as C# and ASP.NET Core. The company says it "runs on any platform" through Docker or OS-specific binaries.

What you build and how

Squidex does not publish pages. You model content, edit it in the web interface, and your own front end fetches it. Here is what the platform covers, in the company's terms.

Content modeling and editing. The comparison page describes the field types: strings, numbers, booleans, dates, geolocation, JSON, arrays, references to other content and asset references. The same page also lists validation, localization and fallbacks, and import and export through the command line. Pricing text on the comparison page says Squidex plans include unlimited content items and locales. A recent post titled "Content Modelling for a Design System: Components over Page Types" shows the company thinks in terms of reusable components rather than one-off page templates.

Versioning and audit. Squidex "tracks every update with full version history." You can compare versions, roll back, and open detailed audit logs "showing exactly who did what, and when." For a blog or documentation team, that means a bad edit is a rollback rather than a restore from backup.

Workflow. A workflow engine lets you define who can create, review and publish content. The company calls it customizable and built to match "even the most complex team structures." A small editorial team can use a simple review step; a larger organization can model several roles.

APIs. There is a REST API built on OpenAPI and OpenID Connect, which the company recommends for automation, CI/CD pipelines and multi-language development environments. There is also a GraphQL endpoint that returns only the fields you ask for, with subscriptions for real-time updates in a website or app. The homepage has a "Try the API" section that tests live API responses against real CMS content.

Integrations. Every action in Squidex triggers an event, so you can connect it to external systems. The company's examples are publishing blog posts to Medium, posting tweets, and syncing updates the moment content changes. The integrations table on the comparison page also lists third-party systems such as Algolia, Azure Queue, Discourse, ElasticSearch, Fastly, Medium, Slack, Twilio and Twitter, and custom field editors and sidebar extensions.

Hosting. You can use the company's cloud service or host it yourself. It deploys through Docker or OS-specific binaries, and the company ships "ready-to-go Helm charts for Kubernetes." A banner on the homepage announces new support for PostgreSQL, MySQL and SQL Server. A customer quote mentions MongoDB and "advanced clustering," running multiple nodes in production.

Operations. The command line tool syncs data between instances, imports and exports assets, and manages configuration. Integrated backup and restore lets you move between on-premise and cloud. The company says Squidex is built for performance on .NET 10 and handles hundreds of thousands of content items.

Recent changes. A blog post dated Oct 02, 2026 describes release 7.24.0, which adds a dark theme across the whole UI, background jobs to export and migrate schema contents, console logging for scripts with a log viewer, and new limits for GraphQL and asset processing.

What the pages say about plans, support and users

The pricing model is the most distinctive part. The comparison page says "with Squidex you only pay based on the number of API calls and asset storage," and that all features are included whether you choose the highest or the lowest plan. The page lists € 19.00 for the smallest plan and € 49,00 per month for the medium plan, with unlimited content items and locales and pricing based on the number of API calls, with the project as the pricing unit. Because Squidex is open source, the page says, "it is free to use and modify, but users must pay for hosting and support." The homepage and the comparison page both invite you to create a free account.

Some features are tied to named plans on the comparison page. Staging environments and cloning projects are marked as Platinum plan features, and chat support and a support SLA are marked as part of a Support plan. Community support runs through a forum, and the site has Features, Integrations, Pricing and Help and Support sections.

The homepage declares Squidex "Open Source (MIT)," "GDPR Compliant" and "Secure." The comparison page lists authentication through OIDC for the API, a content CDN and an assets CDN, and cluster management for hosting.

Customer quotes on the homepage come from named people at Matmatch GmbH, Fortress Reklamebyrå AS, Green Parrot GmbH, CivicPlus, Woonz.nl and CaptiveAire Inc. The CTO of Green Parrot says they added the REST API within an hour and gave non-technical staff content management "without having to build an administration UI." The CivicPlus engineer writes, "We would recommend Squidex to anyone looking for an api first content management system." The Fortress Reklamebyrå quote says they chose Squidex to replace a legacy Keystone setup.

Who it suits

Squidex suits a developer or small agency that wants a headless CMS with an open source core and a clear way to run it on its own servers, and an operations team that wants review and publish rules on top of structured content. The API-call pricing is a good match for a site with many editors but modest traffic, or content-heavy sites that cache aggressively.

It is not a site builder. Nobody picks a theme, drags a layout or gets a public page from Squidex; you or a developer build the front end that reads the API. Marketers who want to see a page take shape while editing will be working in forms rather than on the page. The second caveat is cost shape. Usage-based pricing means a high-traffic site should check what its API call volume does to the bill, and self-hosting trades that bill for hosting and support work you carry yourself.