FAQs

How to reach customer service, support hours, and methods of contact.

What do you do?


We build production containers.

Until now, developers would often justify neglecting best practices with the justification that they would make a separate container suitable for production. Armored Containers is a drop-in solution that enables developers to create new containers at any stage along the development lifecycle, but at least prior to production.

 Doesn’t everyone make production containers?

No. Making containers that are used in production is not the same as building production containers.

 What is a production container?

A production container is a container that is hardened for minimal exposure and optimized for production objectives. Production containers should only include what is necessary for production needs.

 What about my development containers?

Development containers do not belong in production. We will build your production containers based on your container definitions, but without everything you don’t need.

How do you know what our container definitions are?

Simple. You upload your Software Bill of Materials (or SBOM), Dockerfile, or your Containerfile to our system along with any custom files you wish to include in your container and we do the rest.

Is this Zero Trust?

Yes. We comply with NIST SP800-207 and all Zero Trust principles. We get software (including dependencies) directly from the Open Source publishers, MD5 checksum all files, compile files in our automated environment, CVE check all software for known vulnerabilities, and deploy directly to your registry. So, from source to registry provenance remains intact.

How can you make our development container into a Zero Trust container?

The first thing we do is eliminate any software that does not have provenance. (i.e. software not written by your organization or a trusted software provider.) The first line of every container definition file (Dockerfile or Containerfile) is “FROM.” Getting software “FROM” anywhere outside your circle of trust disqualifies software from being Zero Trust.

What is your pricing model?

We charge per build, because it takes cloud resources to build containers.

Are you Open Source?

Yes. We only use Open Source software, which is provided with sources in compliance with the OpenChain standard. Our build server code is not published in order to protect the environment from bad actors. Everything else is provided for the community to enjoy.

How do Armored Containers reduce complexity?

Our containers are single layer containers. You can run “docker history” to see how many layers your development containers have. Each layer should be secured as if it were a separate container; so we remove a lot of the complexity by removing unnecessary layers.

How big is your base image?

Our base image is a kernel with a shell and an editor but without anything unnecessary? Our base image is 3 kilobytes. Yes, 3 KB, not MB. We are preparing to publish this as its own Open Source project. To the best of our knowledge, we have the smallest base image and the next bigger ones are not even close to ours; like multiple megabytes (MB).