Table of Contents


Michael Delzer Updated by Michael Delzer

Agile Stacks Automation Platform makes it easier and faster to deploy your applications and machine learning models at scale on Kubernetes.

Agile Stacks SuperHub helps you fast-track your organization into best practices for Infrastructure-as-code and GitOps. It generates scripts from a library of reusable infrastructure code, written in Terraform, CloudFormation, Go, Bash, Helm, and then delivers those artifacts as git repositories which can be immediately deployed into Kubernetes.

Agile Stacks platform empowers your developers, DevOps engineers, and data scientists to deploy and manage any application stack or ML pipelines in a self-service manner, without creating IT tickets. Stack templates auto-configure connectivity between systems of applications common to any Kubernetes ecosystem such as: Prometheus, Postgres, GitLab, Clair, Sysdig, ElasticSearch, Kibana, Traefik, Istio, Kubeflow, Minio, Ceph, and many others. The SuperHub also empowers you to incorporate your own applications by providing tools to wrap those applications as components and leverage them within reproducible stacks.

Agile Stacks Automation Platform provides:


The SuperHub is the lifecycle management and stack composition tool. It provides auto-generated infrastructure code for stack lifecycle management: the User may change stacks configurations, add, move, replace components, deploy, backup, restore, rollback and clone. SuperHub command line utility and API can be used to deploy the software components automatically onto Amazon AWS cloud account or on-prem private cloud. SuperHub Toolbox image allows to simplify and standardize the deployment of infrastructure as code automation tools on developer workstations and on management hosts.

SuperHub Web UI

This is the primary AgileStacks web console that simplifies stack configuration, deployment, update and governance. The SuperHub WebUI allows IT teams to define a standardized set of cloud-based environments and manage stack instances. The Control Plane also improves visibility into cloud costs. Deploy and easily manage Kubernetes clusters from a single pane of glass using Infrastructure as Code approach.


Components are the Building Blocks of Stacks. These are the key pieces of functionality that your software environment must have in order to function. This could be databases, telemetry system, load-balancers, KMS, etc. Components are bundled into Stack Templates which then can be deployed to multiple environments at the click of a button (or in the shell using our CLI tool)

Stack Templates

Stack templates are the bundling of systems of inter-operating, and automatically integrated components. You build templates by selecting components from our menu of curated components which are either managed by AgileStacks or your own organization. Once you create a Stack Template, you may deploy it to as many environments on as many platforms as you like.

Stack Instances (AKA Kubernetes Clusters)

Provides turnkey solutions to deploy Kubernetes on the AWS, GCP, Azure, on-prem bare metal, or virtual machines, with regular patches and updates. Kubernetes Stack Template contains everything needed to secure and run a container-based set of services in a sound architectural way.

Kubernetes stack services are available via simple catalog selection and provide plug-and-play support for monitoring, logging, analytics, and testing tools. The composability problem is addressed by providing a single, unified tool for running deploying and configuring components. The Agile Stacks Control Plane allows developers and DevOps engineers to select Kubernetes services, define high-level parameters via easy to use UI, and generates composable automation templates using popular Infrastructure as Code tools such as Helm, Terraform, CloudFormation, Ksonnet and others.


Environments are a logical seperation of clusters and the metadata required to configure them. An environment is typically used to create delineations such as "Dev" and "Prod" or organizational separations, such as "Marketing" and "Operations". Environments are key collectors of configuration information, they keep track of which "services" are being provided into an environment. These could be things like encryption keys or database passwords, or even data services such as S3 style bucket storage.

Like what you see? Request a demo today!

How did we do?

Control Plane Tour