Webinar: The Future of CMS

Compare Package Features & Details

Review and compare all available plan details, features and components. Let's find the plan that works for you.

Pricing (All prices listed are USD)
Monthly Price-$279$579$879
Package Limits
Content Items1,00010,00020,00050,000
Digital Channels11510
Additional Users -$15 /user$15 /user$15 /user
Data Limits
Storage1 GB1 TB1 TB1 TB
Bandwidth 1 GB250 GB250 GB500 GB
Requests 100k2M5M5M
Additional Storage$150 /TB$150 /TB$150 /TB$150 /TB
Additional Bandwidth $65 /TB$65 /TB$65 /TB$65 /TB
Additional Requests $5 /1M$5 /1M$5 /1M$5 /1M
Daily Crawl 
Multi-Domain Indexing  
Custom Page Ranking  
Index Size-10,00020,00050,000
Online Support
Service Level Agreement-IncludedIncludedIncluded

Questions on the Details

What are pages?

Agility has full page management giving you pre-defined page object structures allowing you to create sitemaps for your websites.  Each page you create counts towards your number of pages.  Version history does not count towards your limit.  When using dynamic pages which creates a page from a list of content items, the initial dynamic page placeholder counts as a page, but items in the dynamic page list do not count towards your page count.

What are users?

Users are the logins and credentials for accessing Agility CMS and managing your content.  Users are assigned roles to have specific access within the system.

What are roles?

Roles are the different security levels that are assigned to users within the system.  The primary roles used in the system are Administrator, Manager, Publisher, Designer, Approver, Editor, Contributor.  There are additional roles that are specific to User-Generated Content and Ecommerce.

What is an SLA?

SLA stands for Service Level Agreement and is a commitment that Agility follows in terms of uptime and response time provided to our customers.  Some packages do not have SLA's in place while our Enterprise package can have completely custom SLA agreements created.  Our general SLA agreement can be found here.

What is the Sync Architecture?

The sync architecture is used to synchronize your content to different web servers in order to separate your frontend solution from Agility.  When content is published, it is pushed down to these web servers and stored locally.  The benefit to this is extreme performance as well as scalability as you can push content to hundreds of servers and have each server a separate entity, therefore eliminating a single point of failure.  It is a decoupled approach to building out your solutions that is very powerful and can be used in conjunction with the headless APIs to more quickly build high performing solutions.

What are locales?

Locales are different languages or region codes.  For example, en-us and en-ca are two types of locales.  Each locale has its own content and pages.  Items between locales can be linked together such that similar content can be easily grouped with each locale.  In the pages sitemap, a single page can be built in multiple locales and linked together so proper navigation can be maintained across locales.

What is user-generated content?

User-generated content (UGC) is content that primarily comes in from different sources.  This includes form submissions from your website, registered users, comments, or ratings and likes.  

What is the difference between monthly and annual pricing?

Monthly pricing is for customers that pay for their account monthly.  Annual is for customers that pay for the full year upfront.  Monthly pricing is available to self-serve packages using a credit card.  The same packages can also be paid annually in which a discount is usually applied.  Please see the pricing per package for details.

All pricing is shown in US Dollars (USD).

What are content items?

Content items are individual pieces of content stored within the system.  For example, you can have singular content items or content lists.  Each content item in a list counts towards your content limit.  Previous versions of your content do not count towards your content item count.  For example, you can have an item of content with hundreds of changes (version history), but this is only counted as a single content item.

If you have an item that is connected across multiple locales or languages, those are considered multiple items.