Enonic

What it is

Enonic is a headless CMS that the company also calls a composable CMS, presented on its homepage as a "Source of Truth for Humans and AI." The same page puts it this way: "Enonic is a modern headless CMS. Build secure and engaging websites that scale, with tools that fit your architecture." The product serves two audiences at once. Developers get structured content and APIs for the frontend of their choice, and content editors get a visual editing tool called Content Studio. The buyer it speaks to is an organization with a real website estate, such as a public agency, an insurer or a sports league, rather than a single founder. The company menu includes a page titled "Why Choose Norwegian?", and every customer story on the homepage comes from a Norwegian organization.

What you build and how

What you build with Enonic is mainly websites, portals and web applications whose content lives in a structured repository and is edited by non-developers. The homepage lists three promises for the platform itself: structured content, "out of the box APIs for every need," and support for AI driven development.

The editor is Content Studio. The homepage says it gives editors "a powerful tool to manage structured content efficiently with smart workflows," and lists three qualities. You create in a user-friendly interface. There are "handy AI features to boost productivity." And you work visually with interactive previews, so an editor sees how content will appear rather than filling in a form blind. The product menu has its own sections for Features, AI, Content Modeling, Development, Security, Open Source and Enterprise Apps, which outlines how the company divides the platform.

Enonic's long guide to headless CMS explains the thinking behind the product. It argues that a traditional CMS keeps content and presentation in one layer, so content cannot easily be reused on another channel, while a pure headless CMS "acts as a specialized database" that lets developers build clients with their favorite tools but leaves editors with forms and little else. It sums up the pattern in two lines: "Traditional CMS: The editor is happy, but the developer is unhappy. Headless CMS: The developer is happy, but the editor is unhappy." Its answer is what it calls the next gen headless CMS, which "can structure content and compose websites" in one system, with "the added (and optional!) functionality of visual page editing, previewing, hierarchical tree structuring, URL and SEO management, page templates, detailed permissions, back-end integrations, and API customization." The guide says such a system is also called a composable CMS, the term Enonic uses for itself on the homepage.

The guide's side-by-side table spells out what it expects of that kind of system: content types, a rich text editor, an image service, web APIs, a hierarchical tree structure, content-level access control and workflow on the content side, and on the web side a presentation layer, a landing page editor, page templates, preview, URL handling and SEO. It also argues for block editors, where editors insert blocks such as rich text, images, video embeds or tables inside an otherwise structured content type, and for version history and editorial workflow statuses such as draft, in review and published. Read it as the company's own picture of the editing experience Content Studio aims at.

The site shows what teams build with it through named use cases. Under the product menu are an Education Website, a Public Sector Website, a Customer Portal, a Localized Marketing Site and a Next.js website, alongside a general Headless CMS entry. The homepage describes the Next.js case as building websites with React and using the same technology for server-side and client-side rendering across pages. A "Modern stack website" case describes building websites faster "using a modern digital stack with headless CMS and modern frameworks." For multilingual work, the homepage points to "Solving localization challenges with layers," which it describes as managing content in different markets and regions from a single editorial source.

The guide also makes a point about reach. It says native apps were the initial driver for the rise of headless, and that a headless CMS can deliver content to iOS or Android apps and also handle image handling, workflow approvals, publishing dates and taxonomy. The same stored content can feed a landing page, a smartwatch or digital signage, depending on what each channel shows. On frameworks, it walks through Next.js, Nuxt, SvelteKit, React, Angular and Vue as frontends a headless CMS should serve, and compares GraphQL and REST as the two common API styles.

On the finished result, the end user sees whatever frontend you build, or the pages composed in the optional presentation layer. For the developer, there is a Developer Sandbox link on the homepage and a Developers section in the navigation. Around the product sit training and certification, partner resources, a community, guides and product news videos.

Pricing, support and customer stories

The site publishes no prices in the pages we hold; the homepage offers Watch Demo and Try for Free buttons, a Pricing link and a Contact Us link. The guide's chapter on pricing models warns that request-based pricing can climb once traffic picks up, and argues that a next gen headless CMS with an optional presentation layer removes the need to buy a separate system for page composition.

The evidence of use is mostly customer stories. Tuva Sverdstad, Product Manager on Team nav.no, is quoted saying "We use Enonic as the foundation for how we build and manage content. Every page, every product, and every component is a building block we can reuse across the site." The story headline adds that with "a well-thought-out content strategy and structured content in Enonic, NAV took steps toward a more user-friendly and predictable website." The Norwegian Directorate of Health is described as delivering complex information from several sources via multiple channels to different users in one solution, using a reusable structured content model. Gjensidige is described as making its design system work with the Enonic platform for both editors and developers. Thomas Torjusen, Head of Media and CDO of the Norwegian Professional Football League, says "All our clubs now have one stable and user-friendly platform," adding that the new websites "have increased brand visibility and user information."

These are the company's selected stories rather than independent reviews, and they point to large public and corporate sites with many content types and many authors.

Who it suits and who it does not

Enonic suits organizations with both developers and editors, where content is structured, reused across pages and channels, and edited by people who should not need a developer for routine changes. A public agency with many services to explain, a company running sites in several markets from one editorial source, or a league running one platform for many clubs all match the stories on the homepage. A team using React or Next.js that wants to keep its own frontend fits the use cases the site shows, and so does a team that wants visual previews and page composition without giving up an API.

It is less obviously a fit for a solo founder who needs one landing page. A headless setup means someone builds and hosts the frontend, and structured content modeling is more work than dragging blocks onto a page. The guide itself says that in early headless systems the content editors "simply didn't ask for it," and that headless is "primarily developer driven," which is why it presents the composable approach with visual tools as the remedy. Buyers who want a price list before a conversation will need to go through the demo or contact route.