Forrit CMS
Enterprise content management without enterprise complexity.
Forrit CMS gives content teams one governed place to create, manage, reuse and publish content across websites and digital channels. It combines structured content, visual page building and headless delivery, so you don't have to choose between a traditional web CMS and a headless content platform.
01 · Structured content
Create once. Use everywhere.
Instead of re-typing the same information into individual pages, you define content types for the things your organisation publishes, such as products, interest rates, policies, locations or contact details, and the relationships between them.
Each item is maintained once, in one place. When it changes, the update is reflected everywhere that item is referenced as soon as the change is published. Usage information shows editors where an item is referenced before they change it, which matters when one update can touch hundreds of pages.
How structured content works
Define a content type with the fields and relationships you need
Create each entry once, in one place
Reference it from any page, project or channel
Check where it is used, update it once, and publish the change everywhere
Structured content capabilities
Structured content types
Model content once as reusable, structured types, rather than locking it inside individual pages.
Relationships between content
Link entries to each other, such as a product to its rates, documents and FAQs, so pages are assembled from reusable parts.
See where content is used
Before changing an item, editors can see the pages and entries that reference it, so they understand the impact first.
02 · Web and headless
Web pages and headless content, from one platform.
Forrit is not simply a headless CMS. It is a hybrid: build and manage web experiences where they make sense, and publish structured JSON where you need headless delivery, from the same content.
Websites are built from reusable components and pages that your editors manage. Apps, APIs and other front ends consume the same content as pure JSON. Both are served by dedicated delivery channels, separate from the CMS.
One content source, two ways to deliver
Model and manage content once in Forrit CMS
Publish web pages through the HTML channel, built from your components
Publish structured JSON through the JSON channel for apps, APIs and other front ends
Serve both from dedicated delivery channels, separate from the CMS
Delivery capabilities
HTML and JSON delivery
Publish the same content as full web pages or as pure JSON with no markup, ready for any front end.
The right model for each channel
Run a marketing site as managed web pages and an app as headless JSON, without maintaining two content platforms.
Separate delivery tier
Published content is served by dedicated Web and JSON delivery channels, never by the systems your editors use.
03 · Components and pages
Governed components. Editors in control.
Developers build components once: reusable templates that format your structured content for display. Editors then assemble pages from those approved building blocks and preview them, without needing a developer for every new page.
Because a component is defined once and reused wherever it is placed, an improvement to its template, such as an accessibility fix or a design refresh, applies wherever that component is used.
From component to page
Developers build a component template for a content type
Editors add components to a page and assign content to them
Preview the page before it goes for approval
Improve the component once and every page that uses it benefits
Component and page capabilities
Reusable components
Developers build components once and editors reuse them across sites, cutting the time to deliver rebrands, campaigns and launches.
Page templates
Start new pages from templates with the right components already in place, so pages follow your standards from the first draft.
Consistent brand and policy
Shared components and approval workflows keep layouts, branding and policy consistent, however many sites you run.
04 · Workflow and governance
Govern centrally. Empower teams locally.
Large estates need local teams to move quickly without losing central control. In Forrit CMS, each project can have its own users, permissions, workflows and publishing schedules, while your organisation keeps governance of the wider platform and the elements every project shares.
Every change is made in a task branch, reviewed with a before-and-after view of what is changing, approved through a configurable workflow and recorded in the audit history. Find out more about control and content governance security.
From draft to live
Make changes in a task branch, away from live content
Review what is changing with a before-and-after view
Approve through your configured workflow
Publish, with a full audit history and the option to roll back
Governance capabilities
Projects for every team
Give each site, brand or business unit its own project, with its own users, permissions, workflows and publishing schedules.
CMS roles and permissions
Decide exactly who can create, edit, approve and publish, enforced consistently across sites, teams, agencies and subsidiaries.
Approval workflows
Customisable workflows and tailored approval policies control what gets published, all tied back to each user's identity.
Release history and rollback
Changes are prepared in task branches and previewed before going live. Release history and full rollback let you reverse a change quickly.
Complete audit trail
Every CMS task, action and change is securely logged, giving you an audit history of who did what, and when.
AI under the same controls
Changes made by an authorised AI assistant through the Forrit MCP server land in task branches, just like changes made by people, so they are reviewed and approved before anything is published.
05 · Localisation and variants
The right version for every market and audience.
Content can have localised versions for each language and region you publish in, and variants for different audiences or requirements, all managed alongside the original rather than as disconnected copies.
Combine AI translation with specialist agency translation, and review the results in a built-in workflow before anything goes live. See how Forrit helps you scale globally.
From master to every version
Create the master version of your content
Produce localised versions with AI or agency translation
Add variants for specific audiences or requirements
Review and approve each version before it is published
Localisation capabilities
550+ locales
Publish content in more than 550 languages and regional variants from a single CMS.
AI and agency translation
Use fast, low-cost AI translation alongside specialist agency translation where accuracy matters most.
Built-in review workflow
Translations can be reviewed and approved before they are published, so you can be confident in the results.
Audience variants
Create variants of content for different audiences or requirements, and control which page components appear for each variant.
06 · Media management
Media management with security built in.
The integrated media library gives teams one place to store, find and reuse images, documents and other assets. Every upload is scanned for malware before it joins the library, and AI-assisted tagging adds metadata to help teams organise and discover media.
What happens when a file is uploaded
An editor uploads an image or document to the Media Library
The file is scanned for malware in near real time
Clean files join the Media Library; threats are blocked
Media capabilities
One shared media library
Media is tagged with metadata by AI on upload, and each asset can have multiple responsive versions for every format and screen size.
Malware scanning on upload
Every file is scanned for malware in near real time, so harmful content is stopped before it enters the CMS.
Find media faster
AI-assisted tags and metadata help editors search the library and reuse approved assets instead of uploading duplicates.
07 · Built to connect
A CMS that connects, rather than trying to do everything.
Forrit is composable. Its architecture is designed to integrate with the enterprise services around it rather than absorbing all of their functions into the CMS, so you can connect the CRM, analytics, forms, payment, personalisation and digital asset management services you already rely on.
Developers extend the platform with .NET SDKs and work with content programmatically through the GraphQL API. Authorised AI assistants can work with content through the Forrit MCP server, under the same review controls as people.
Integration capabilities
Connect the services you rely on
Integrate CRM, analytics, forms, payment, personalisation and DAM services, so each system does the job it does best.
Composable and extensible
Our .NET SDKs let developers customise layouts, build tailored components and integrate the products and services you already use.
GraphQL API
Work with content types, entries, components and pages programmatically to automate content operations and connect other systems.
AI-ready, under control
Authorised AI assistants can work with your content through the Forrit MCP server, with every change landing in a task branch for review.
One content foundation
Governed content, without dictating how every experience is built.
Forrit CMS gives your teams a single governed place to create and reuse content, and the freedom to deliver it as web pages or headless JSON. See how the rest of the platform supports it.
- Product
Service Delivery Hub
Provision, manage and operate the cloud platform behind your digital estate, with automated environments, central visibility and managed upgrades.
- Platform
The Forrit Platform
See how Forrit CMS, the Service Delivery Hub and your digital experiences fit together on one secure platform.
- Key benefit
Security
Seven layers of protection, from edge security and Airlock Publishing to secure development and ISO 27001 assurance.
Use the Tab key to move through each testimonial
Forrit CMS questions, answered
Forrit CMS is a hybrid headless enterprise CMS. It combines structured content, visual page building with reusable components, and headless JSON delivery, so you can run managed web experiences and headless channels from the same content platform, with governed workflows around every change.
Not for every page. Developers build governed components once, and editors assemble new pages from those components, assign content and preview the result themselves. Developer time goes into creating new kinds of component rather than building each page.
Yes. Forrit CMS shows where an item is referenced across your pages and content before you change it, so editors understand the impact of an update before it is sent for approval.
Changes are made in task branches, reviewed with a before-and-after view, approved through configurable workflows and recorded in an audit history. Role-based permissions decide who can create, edit, approve and publish, and published changes can be rolled back.
Yes. Content can have localised versions in more than 550 locales and variants for different audiences or requirements. Translations can come from AI or specialist agencies and are reviewed in a built-in workflow before they are published.
Forrit is composable. Developers can integrate services such as CRM, analytics, forms, payments, personalisation and digital asset management, extend the platform with .NET SDKs, and work with content programmatically through the GraphQL API.
Yes, under your control. Authorised AI assistants can work with content through the Forrit MCP server. Their changes land in task branches, so they go through the same review and approval workflow as changes made by people.