Agencies & Enterprise

Enterprise deployments, agency-first.

Most Total CMS enterprise deployments happen through an agency: you build and run the sites, your client is the institution. This page is written for both of you — the licensing model for the agency, and the diligence material for your client’s reviewers.

How enterprise licensing works

Enterprise and multi-site deployments are licensed per site, on a volume curve quoted per project — not at list price, and not from a published tier table. Licensing is billed as a monthly or annual subscription with managed hosting included through our own infrastructure, so one line item covers the license, the hosting, and updates applied.

Billing for each site starts at go-live — publicly accessible, production domain pointed — not on a planned deployment schedule. How development and staging environments are licensed during the build phase is part of each quote.

There’s a monthly minimum on subscription agreements, so the model fits deployments of roughly five sites and up. For one or two sites, standard licenses are the better deal — that’s why they exist.

A subscription that ends in ownership

Every subscription license carries the same structure as our one-time licenses: a 24-month minimum term, after which the license confers a perpetual right to run the software. Stay subscribed and that perpetual version advances with you; cancel after the term and the sites keep running on the version you have, on any hosting you choose, forever.

No other CMS subscription works this way. There is no runtime license enforcement in Total CMS — serving pages is never gated by validation, and no billing issue or outage on our side can take a live site offline. The subscription buys hosting, updates, and support. It never holds your client’s site hostage.

Standard license terms are in the EULA; enterprise subscriptions are governed by separate written agreements that carry the same 24-month-to-perpetual structure.

What the subscription covers

For your client’s reviewers

When your client’s IT, security, or procurement team needs to sign off, send them these — they’re written for exactly that reading:

Total CMS’s source is public and present in every deployment — your client’s security team can audit the claims rather than take them on trust. Deployments on isolated networks, EU-resident infrastructure, and environments that preclude vendor connectivity are all supported; the trust page covers each.

The one-person company question

Total CMS is built and run by one person, and your client’s procurement process may ask about that directly. Here’s the honest answer.

Aspect Services, LLC was incorporated in 2008 and has operated continuously since, with 4,500+ Total CMS licenses deployed. More importantly, the architecture is the continuity plan: content is flat files in an open format on infrastructure you control, the source ships with every deployment, licenses are perpetual after their term, and nothing we operate needs to stay reachable for a site to serve pages. If Aspect Services disappeared tomorrow, every deployed site would keep running indefinitely.

Most vendors answer the continuity question with promises. This one is answered by the design.

Start a conversation

Enterprise licensing is quoted per project. Write to sales@totalcms.co with:

  • roughly how many sites, and on what timeline
  • whether you need EU or otherwise specific hosting regions
  • anything unusual: isolated networks, SSO requirements, compliance frameworks in play

You’ll be talking to Joe Workman, who builds the product and will build your quote. Expect a reply within a day or two.