Choosing a content management system for a university is rarely a feature comparison. It is a decision about how the institution wants to operate. Higher education websites sit at the intersection of admissions traffic, distributed editorial teams across academic departments, accessibility compliance, brand governance, and integrations with student information systems. A CMS that handles all of that without breaking is a different category of product from a CMS that is "easy to install."
Cascade CMS, built by Hannon Hill, is one of the few platforms designed from the start for that operating model. It is widely deployed across higher education in the United States, and the reason it endures is structural rather than aesthetic.
What Cascade CMS Actually Is
Cascade CMS is a SaaS-hosted authoring application. Hannon Hill operates the CMS itself, applies upgrades, and guarantees its availability. Editors log in to a web interface, draft and approve content through configurable workflows, and then publish.
Publishing in Cascade is the part that surprises people new to the platform. When an editor clicks Publish, Cascade renders the content and pushes the resulting files to a separate production web server that the institution operates. The CMS is not the website. The website lives on infrastructure outside Cascade, and that infrastructure is what visitors actually hit.
This separation is a feature, not a quirk. It means the public site stays online if Cascade has a maintenance window. It also means that the production hosting environment is the institution's responsibility, which is the part most institutions underinvest in. We covered that gap in detail in The Cascade CMS Hosting Gap.
Why Cascade Fits Higher Education Specifically
The structural fit comes from how Cascade handles governance and scale.
Distributed contribution with central control. A large university typically has dozens of departments publishing content, each with their own editorial standards. Cascade's permissioning is granular at the asset level. Marketing can lock down templates and brand-critical components while still allowing departments to publish freely within their assigned sections.
Workflow that survives turnover. Approval workflows in Cascade are configured per content type and per section. New hires are added to roles, not stitched into custom approval chains. When a department head changes, the workflow keeps running.
Accessibility checks integrated into authoring. Cascade includes built-in accessibility checks and integrates with Siteimprove for prepublish validation. This matters for institutions facing increasing regulatory pressure under WCAG 2.1 AA and Section 508 for public-facing campus content.
Templating that does not require constant developer intervention. Cascade's templating layer (Velocity and XSLT) lets developers define structured content models that non-technical editors fill in. Brand consistency is enforced by the template, not by editorial discipline alone.
Reporting that finds stale and broken content. Cascade ships with reports for stale pages, broken links, accessibility failures, and orphaned assets. For institutions that publish thousands of pages across hundreds of contributors, these reports are how content stays current.
Where Cascade Does Not Help
Cascade is not a hosting product. It does not run your production website. Performance during enrollment spikes, CDN strategy, security patching of the web server, SSL lifecycle, and uptime SLAs all live in the production environment that receives Cascade's published output. Hannon Hill is not responsible for that environment, and most institutions do not have an explicit owner for it either.
Cascade also does not replace integration work with student information systems, learning platforms, or single sign-on. It exposes APIs and connectors, but the integration architecture is something the institution designs and operates.
These gaps are why eWay Corp exists as a Cascade partner. We operate the production hosting environment that receives Cascade's published output and the integrations that connect it to campus systems, so the SaaS CMS and the website it publishes to are operated as a single accountable platform.
Frequently Asked Questions
Is Cascade CMS hosted by Hannon Hill or by the institution?
The Cascade CMS application itself is SaaS, hosted by Hannon Hill. The production website that receives Cascade's published output is hosted by the institution or its hosting partner. These are two separate environments with separate operational responsibilities.
Does Cascade CMS work for institutions with hundreds of contributors?
Yes. Cascade's permissioning, workflow, and template enforcement model is specifically designed for distributed contribution at institutional scale. Most large universities running Cascade have hundreds of named editors across academic and administrative departments.
Can Cascade integrate with our student information system or single sign-on?
Yes. Cascade supports SAML and LDAP authentication, exposes a Web Services API, and integrates with most campus systems through standard connectors. The integration design is the institution's responsibility, not Hannon Hill's.
What is the difference between Cascade hosting and Cascade Website Hosting?
Hannon Hill hosts the Cascade SaaS application. Cascade Website Hosting refers to the production environment that receives the published output and serves it to visitors. eWay Corp specializes in operating the latter for higher education institutions.