Platforms
The Platforms We Operate. CMS, Cloud Infrastructure, and Everything Between.
eWay operates five platforms as a continuous managed service: Drupal, WordPress, Cascade Website Hosting, AWS, and Azure. Each one is managed from infrastructure through application layer, under a single engagement, with defined SLAs and a team that doesn't hand off at go-live.
CMS Platforms
Drupal
For government, higher education, and complex multi-department environments
Full platform details →Drupal powers 24% of all government websites, for good reason. We operate Drupal as a fully managed WebOps platform: AWS or Azure infrastructure, application patching under SLA, RBAC integrated with Active Directory, editorial workflows, WCAG 2.1 AA accessibility, and enterprise search via OpenSearch or Solr.
What we manage
- Multi-site networks (50+ departments)
- RBAC · Active Directory · SAML · LDAP
- Multilingual · translation workflows
- Editorial approval workflows · scheduling
- WCAG 2.1 AA compliance
- OpenSearch · Solr · Elasticsearch
Primary sector: Government · Higher Education
WordPress
For large multi-department organizations that need enterprise governance, not commodity hosting
Full platform details →Enterprise WordPress is not the same problem as a five-page website. Large organizations need plugin governance, custom RBAC, SSO, publishing workflows, multisite network management, and search infrastructure for 50,000+ content items. We manage WordPress at full stack with defined SLAs.
What we manage
- Core · plugin · theme patching under SLA
- SSO · RBAC · Active Directory · Entra ID
- Custom publishing workflows & approval chains
- Multisite network architecture & governance
- OpenSearch · Redis · performance stack
- WAF · DDoS · file integrity monitoring
Primary sector: Higher Education · Nonprofits · Healthcare
Cascade Website Hosting
For higher education institutions already on Cascade CMS who need production infrastructure operated properly
Full platform details →Hannon Hill manages the Cascade CMS SaaS. eWay manages the production infrastructure that receives your published output: the AWS or Azure environment, CDN, performance layer, DNS, and identity integrations that Hannon Hill doesn't own and your internal team shouldn't have to.
What we manage
- AWS · Azure production hosting infrastructure
- CloudFront · Azure CDN edge acceleration
- SSO · SAML · LDAP · Active Directory · Entra ID
- Publish target configuration & troubleshooting
- DNS management & SSL certificates
- 24x7 monitoring & alerting
Primary sector: Higher Education
Cloud Infrastructure Platforms
Amazon Web Services (AWS)
AWS Solution Provider Partner · Public Sector Partner · AWS Marketplace Seller · 10+ years
Full platform details →We operate AWS environments for public sector organizations, managing the full shared responsibility gap from VPC to application layer. Infrastructure, security, identity, CI/CD pipelines, CMS platforms, migration, and ongoing operations under one engagement.
What we manage
- AWS Solution Provider Partner, 10+ years
- AWS Public Sector Partner
- AWS Marketplace Seller
- Available via Carahsoft
- EC2 · RDS · Aurora · Systems Manager · WAF delivery designations
Primary sector: Government · Higher Education · Nonprofits · Healthcare
Microsoft Azure
Microsoft Cloud Solution Provider · Azure for Government Partner · Available via Carahsoft
Full platform details →Government agencies have decades of investment in the Microsoft stack: SQL Server, ASP.NET, Active Directory, Dynamics, SSRS, SSIS. As a Microsoft CSP and Azure for Government partner, we operate Azure environments for public sector, managing compute, database, networking, security, and identity under one engagement.
What we manage
- Microsoft Cloud Solution Provider (CSP)
- Azure for Government Partner
- Available via Carahsoft
- Microsoft licensing included through CSP
- SQL Server · ASP.NET · Active Directory · Entra ID
Primary sector: Government · Higher Education
How we operate
Not a host. Not a dev shop. Not a platform.A WebOps Operator.
There are three ways most organizations manage their platforms today. None of them is what we do.
Hosting provider
Manages the server. Doesn't touch the CMS, the application, the security layer, or the identity configuration. When your Drupal module causes a performance problem, your hosting provider's answer is a support ticket, not a fix.
You still own most of the problem.
Dev agency
Builds the platform and hands it off. The environment you receive at go-live begins drifting from a secure, performant state the day the project closes, and continues drifting until the next project engagement begins.
They're done. You own the problem from here.
WebOps platform
Gives you tools to operate the platform yourself. You still need engineers to use those tools, manage deployments, handle incidents, tune performance, and maintain security posture. Better tooling. Same staffing problem.
Better tooling. Same staffing problem.
eWay: WebOps Operator
We operate the platform. Infrastructure, application, security, identity, performance, patches, incidents: all of it, under one engagement, with a dedicated team and defined SLAs. You publish content. We operate everything underneath it.
One partner. Full accountability. Continuous operation.
Included in every managed platform engagement
These are not add-ons. They are the standard.
We don't build modular service tiers where customers must opt into basic operational practices. These capabilities are included in every engagement across every platform we operate.
24x7 monitoring & alerting
Continuous infrastructure and application monitoring with alerting and defined escalation paths. Not reactive ticket submission after something breaks.
Patching under SLA
OS, CMS core, plugins, modules, and dependencies patched on a defined schedule with critical vulnerability SLAs. Not ad-hoc when someone notices a CVE.
Dev / Test / Staging / Production
Isolated environment pipeline as a standard operating model, not a premium tier. Changes are validated through staging before production promotion. Every time.
Backup validation & DR testing
Backups are validated to complete successfully. Restores are tested to actually work. DR readiness is checked against defined RTO/RPO targets, not assumed.
Dedicated project manager
One point of contact who knows your environment, your team, and your procurement requirements. Not a shared support queue. A person.
Security architecture
WAF, DDoS protection, identity governance, vulnerability scanning, access control reviews, and audit logging. Managed continuously, not set up once and left.
CI/CD pipelines
Version-controlled deployments with approval gates, automated testing, staging validation, and rollback capability. Managed through AWS CodePipeline or Azure DevOps.
Monthly operational reporting
Infrastructure health, security posture, performance metrics, incident summary, SLA compliance, and cost optimization findings. Documented every month.
Frequently Asked Questions
Questions decision makers ask before engaging
Do you operate on both AWS and Azure, or do we have to choose?
We operate on both. Most of our clients run on AWS, but for organizations with an existing Microsoft infrastructure investment (Active Directory, SQL Server, Dynamics, .NET applications), Azure is often the better fit. Some clients run a mixed environment: CMS platforms on AWS, Microsoft workloads on Azure. We manage both.
We already have a hosting provider and a dev agency. Why do we need a WebOps Operator?
Because your hosting provider doesn't touch the application layer, and your dev agency leaves when the project closes. Between those two gaps lives your actual operational risk: unpatched plugins, drifting security configurations, unvalidated backups, unmanaged performance degradation, and no defined owner when something fails at 2am. A WebOps Operator closes that gap.
Can you manage a platform we didn't build?
Yes. Most of our engagements start this way. We conduct a Platform Assessment during Phase 1 discovery to document the current state of your infrastructure, application, security posture, and operational coverage. We then establish a baseline, identify gaps, and begin managed operations. We don't require you to rebuild to engage us.
What does a typical engagement look like in the first 90 days?
Phase 1 is discovery and architecture review. We assess your current environment, document what exists, identify security and operational gaps, and define the scope of managed operations. Phase 2 is environment build or remediation: bringing your environment up to our operating standard, establishing the four-environment pipeline, and configuring monitoring and alerting. By day 60-90 most clients are in full managed operations with the monthly governance cycle running.
How do government agencies procure your services?
Multiple paths are available. Direct engagement with standard government contract documentation. AWS Marketplace for agencies with existing Marketplace agreements. Azure CSP procurement for Microsoft stack engagements. Carahsoft for both AWS and Azure services using established government contract vehicles. Our SBA 8(a), MBE, DBE, and SBA Small Business certifications support set-aside and direct-award procurement.
Do you manage CMS platforms and cloud infrastructure together, or are those separate engagements?
Together. That is the entire point. The CMS platform and the cloud infrastructure it runs on are not separate problems. They are one operational environment that requires one accountable team. We scope each engagement to include both layers, which is what allows us to close the full shared responsibility gap.
Ready to operate a platform?
Stop managing vendors.
Start operating a platform.
Schedule a consultation and we will assess your current platform environment, identify operational gaps, and outline what a managed engagement looks like for your organization. Available direct, via AWS Marketplace, via Azure CSP, and through Carahsoft.