What is your developer-dependent CMS actually costing you? Calculate your costs and get a full report
What is your developer-dependent CMS actually costing you? Calculate your costs and get a full report
Evaluating Agility
Fit criteria backed by documented capabilities: when Agility suits your project, when it may not, and the questions to settle before you decide.
No CMS fits every project. This page describes what Agility does and doesn't do, so you can compare it with what your project needs. Use it early, before you invest in a proof of concept.
You want to own your front end. Agility is a headless CMS: it stores your content and delivers it through APIs, and your team builds and deploys the website or app outside Agility. See What Your Team Builds vs What Agility Provides. Agility recommends Next.js or .NET for new projects. Other stacks can read content through the Content Fetch API (REST) or the GraphQL API.
Editors need to manage pages, not just content. With page management, editors add and remove pages in the sitemap, choose a page model, place components and set SEO properties without a developer. See How Agility Works.
Content is reused across pages, sites or channels. Content in Agility is available to all your pages, so one item can appear on many pages, in several sitemaps, and in apps or other services through the API. See Publishing to Multiple Destinations and Building a Content Hub.
You run several sites, brands or regions. One instance can hold several sitemaps that share page models, components and content models, and an organization can hold several instances. See Using Agility for Multiple Sites and Locales.
You need editorial governance. Agility has custom roles, item-level permissions, approval workflows, scheduling and version history.
You want AI agents working on content, under control. The Agility CMS MCP Server lets AI assistants work with your content within each user's existing Agility permissions. Content it saves goes to the instance's default workflow state, typically Staging, and isn't live until it is published. See Governing AI Access to Agility CMS.
You want the CMS run for you. Agility is a SaaS platform hosted on Microsoft Azure, and it delivers content and assets through the Fastly CDN. There is nothing to install for the CMS. See Hosting, Security & Compliance and Content Delivery & CDN Architecture.
No one will own the front-end code. Agility doesn't build your website. You need a developer or a partner to build it, host it and keep it running. Starters and AI coding tools can speed this up (Vibe Coding with Agility), but someone still has to understand, review and maintain the code.
You need one product to be your CMS, search, forms and analytics. Agility manages content and pages. Search, forms and analytics are integrations, each with its own tool and setup. See What Your Team Builds vs What Agility Provides.
You need the CMS installed on your own servers. Agility CMS can't be installed on-premises: it is a multi-tenant SaaS platform (see the FAQ on the pricing page). Your website can still be hosted wherever you choose, including on-premises. If you need private or dedicated hosting, contact sales. If the concern is where data is stored, read Data Residency & Data Regions first.
Talk these through with your team. The answers usually make the decision clear.
