Containers as a Service

Containers as a Service, or CaaS (pronounced “cass”), enables customers to run an application and all its dependencies in isolated processes. These isolated processes, also known as code packages, have everything the app needs to reliably run its software in any environment (including the app, runtime, system libraries, etc.). With all critical elements packaged together, applications can be easily moved from one environment to another. Simply put, CaaS is like an application suitcase, with wheels.

Why CaaS?

A current challenge for many customers is portability, the ability to lift and shift applications and their dependencies from one environment to another. Application dependencies may be hard to locate, there may be limited hardware space to hold applications, or potential conflicts between programs running on the same computer. CaaS provides customers with portability to easily move applications from one environment to another. 


  • Rapid application portability. The application and all its dependencies are bundled in a container, allowing customers to easily move applications from one environment to another.
  • Faster access. Currently, it is difficult for mission partners to access container platforms. CaaS provides direct pathways for customers to access platforms.
  • Faster start-up times. Containers are smaller (megabytes, instead of gigabytes), allowing a single operating system kernel to start up in a few seconds—versus the minutes required to start-up a virtual machine.
  • Direct support. HaCers partner with customers to develop container applications, providing expert support with portability, accreditation, and other requirements. This allows customers to focus their resources on application development.

Getting started.

Customers can order CaaS now. If you are interested in learning more about CaaS, use the ‘contact us’ form to connect with our team. 

 Download the Slick Sheet
Collapse All Expand All
 1. How does CaaS compare to commercial containers? 
A CaaS and commercial application deployment would be very similar and one of the benefits of containerization is the portability between environments. It is likely that if your container runs anywhere else, it runs on CaaS also. However, CaaS is on premise and may easily integrate with existing DISA hosted services to create a hybrid operating environment or transition into container based infrastructure. CaaS  inherits many DISA security controls and comes with NIPR connectivity. 
Collapse All Expand All
 1. Red hat Advanced Cluster Security 
Provides detailed CVE and vulnerable configuration detection in the hosted namespace for running containers. 
 2. Red Hat Core OS

An OS designed for hosted Cloud Based applications. 

 3. Role Based 2FA 

Integrated with GFUD, signing in to OpenShift is easy and CAC protected. 

 4. FIPS 

A high standard for cryptography, enabled at install time on the physical nodes. 

 5. Red Hat Compliance Operator 
Protects the cluster itself from misconfigurations. 
 6. SELInux

Protects against arbitrary inter-container access and access to the nodes from containers.

 7. Arbitrary IDs 

A container runs without node level root access, although it can access all of its own assigned resources and no more. 

 8. Hosted Physically Inside DISA data center