# Is Agility Right for Your Project? When It Fits and When It Doesn't

> Source: https://agilitycms.com/docs/overview/is-agility-right-for-your-project

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.

## Agility tends to fit when

**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](/docs/overview/what-your-team-builds-vs-what-agility-provides). Agility recommends [Next.js or .NET](/docs/developers/why-we-recommend-nextjs-and-dotnet) for new projects. Other stacks can read content through the [Content Fetch API](/docs/developers/content-fetch-api) (REST) or the [GraphQL API](/docs/developers/graphql-api).

**Editors need to manage pages, not just content.** With [page management](/docs/overview/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](/docs/overview/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](/docs/developers/sitemaps), and in apps or other services through the API. See [Publishing to Multiple Destinations](/docs/overview/publishing-to-multiple-destinations) and [Building a Content Hub](/docs/overview/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](/docs/overview/using-agility-cms-for-multiple-sites) and [Locales](/docs/editors/locales).

**You need editorial governance.** Agility has [custom roles](/docs/owners-admins/custom-roles), [item-level permissions](/docs/owners-admins/item-level-permissions), [approval workflows](/docs/editors/workflows), [scheduling](/docs/editors/schedule-content-changes) and [version history](/docs/editors/versioning).

**You want AI agents working on content, under control.** The [Agility CMS MCP Server](/docs/developers/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](/docs/owners-admins/governing-ai-access).

**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](/docs/owners-admins/hosting-security-and-compliance) and [Content Delivery & CDN Architecture](/docs/developers/content-delivery-and-cdn-architecture).

## Agility may not be the right fit when

**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](/docs/developers/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](/docs/overview/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](https://agilitycms.com/pricing)). Your website can still be hosted wherever you choose, including on-premises. If you need private or dedicated hosting, [contact sales](https://agilitycms.com/contact-agility-cms). If the concern is where data is stored, read [Data Residency & Data Regions](/docs/owners-admins/data-residency-and-data-regions) first.

## Questions to settle before you decide

Talk these through with your team. The answers usually make the decision clear.

1. **Who will edit, and how often?** List the roles, how many people, and how often each publishes.
2. **What do editors need to control?** Content only, or pages, layouts and SEO as well?
3. **Where does content go?** One website, several, apps, signage, a search index, other systems?
4. **Who builds and hosts the front end?** In-house, a partner, or both? Which framework?
5. **What has to integrate?** Search, forms, analytics, commerce, CRM, single sign-on, translation.
6. **What governance do you need?** Approvals, permissions by section or item, audit, scheduling.
7. **How many locales and regions?** And is the content per locale mostly translated or mostly different?
8. **What are the non-negotiables?** Data region, security review, uptime, accessibility.

## Next steps

- If it looks like a fit, read [How Agility Works](/docs/overview/how-agility-works), then [Run a Two-Week Proof of Concept](/docs/overview/run-a-two-week-proof-of-concept).
- If you're unsure which way to use Agility, read [Headless, Hybrid or Traditional: Choose Your Delivery Model](/docs/overview/choose-your-delivery-model).
- To compare it with other options on equal terms, use [Choosing a Headless CMS: A Capability Checklist](/docs/overview/choosing-a-headless-cms).
- For questions this page doesn't answer, [contact Agility](https://agilitycms.com/contact-agility-cms).

---

## Related pages

- [Evaluating Agility](https://agilitycms.com/docs/overview/evaluating-agility.md)
- [What Your Team Builds vs What Agility Provides](https://agilitycms.com/docs/overview/what-your-team-builds-vs-what-agility-provides.md)
- [How Agility Works: A 10-Minute Architecture Tour](https://agilitycms.com/docs/overview/how-agility-works.md)
- [Choosing a Headless CMS: A Capability Checklist and Questions to Ask Any Vendor](https://agilitycms.com/docs/overview/choosing-a-headless-cms.md)
- [Run a Two-Week Proof of Concept](https://agilitycms.com/docs/overview/run-a-two-week-proof-of-concept.md)
- [Headless, Hybrid or Traditional: Choose Your Delivery Model](https://agilitycms.com/docs/overview/choose-your-delivery-model.md)
- [Getting Your Content Out: Data Portability and Exit](https://agilitycms.com/docs/overview/data-portability-and-exit.md)
- [Building the Replatforming Business Case](https://agilitycms.com/docs/overview/replatforming-business-case.md)
- [Evaluate Agility with an AI Agent in 30 Minutes](https://agilitycms.com/docs/overview/evaluate-agility-with-an-ai-agent.md)

Index of every docs page: https://agilitycms.com/docs/llms.txt