By Large-scale EKS deployments using the AWS Well-Architected Framework create complex multi-tenant account structures where each tenant requires isolated accounts for application clusters and data services. Giving developers on-demand self-service access across that structure while enforcing centralized governance is an unsolved operational problem for most platform teams. Without a dedicated control plane, provisioning data services into the correct tenant account becomes a manual, error-prone process that breaks at scale.
In this interview on TFiR, Julian Fischer, CEO at anynines, walks through how Klutch is maturing into an enterprise-grade control plane for Kubernetes orchestration and governance, covering the new a9s Hub for AWS, the a9s Hub for on-premises deployments, and how Klutch handles per-tenant data service provisioning automatically.
Guest: Julian Fischer, CEO at anynines
Show: TFiR
Here is what every platform engineer and EKS operator needs to know.
Technical Deep Dive
Q: What is Klutch and what problem does it solve for Kubernetes operators?
Julian Fischer, CEO at anynines, describes Klutch as a central control plane for Kubernetes orchestration and governance. It addresses the core tension platform teams face at scale: enabling developer self-service on-demand while maintaining centralized policy enforcement across many clusters and tenants. Klutch acts as the coordination layer that makes both possible simultaneously.
“If you run a lot of Kubernetes clusters on AWS and you are an EKS user using the Well-Architected Framework, how do you enable your users to get on-demand self-service while providing that central governance using Klutch as a central control plane for orchestration and governance.” — Julian Fischer, CEO, anynines
Q: What is the a9s Hub for AWS and how does it align with the AWS Well-Architected Framework?
The a9s Hub for AWS is a purpose-built configuration of Klutch designed to operate within the account structure prescribed by the AWS Well-Architected Framework. Fischer explains that the Well-Architected Framework defines a specific layout for how AWS accounts are organized, and the Hub is built to operate natively within that structure. This allows large EKS deployments to use Klutch for governance without fighting against the account model AWS recommends.
“The Well-Architected Framework uses a particular layout and how AWS accounts are set out.” — Julian Fischer, CEO, anynines
Q: How does the AWS Well-Architected Framework structure accounts in a multi-tenant EKS deployment?
Fischer describes the Well-Architected Framework pattern as assigning two AWS accounts per tenant: one dedicated EKS account for the application cluster and one separate account for services. With many tenants running across this structure, the total number of accounts grows significantly, and the relationship between application clusters and their corresponding service accounts must be tracked and enforced consistently. This account isolation model is foundational to how the a9s Hub for AWS operates.
“You have per tenant your own EKS account and your own account for services. So you have two accounts per tenant and you have potentially many tenants.” — Julian Fischer, CEO, anynines
Q: How does Klutch provision data services into the correct tenant account automatically?
When a new application cluster is provisioned on EKS, the Klutch client is installed onto that cluster. Fischer explains that once the Klutch client is present, it is able to provision data services directly into the AWS account that corresponds to the correct tenant, rather than requiring manual routing or operator intervention. This automatic account-to-tenant mapping is what makes large-scale self-service provisioning governable.
“When application clusters provision and the Klutch client is installed, it should be able to provision data services in the corresponding account that corresponds to the tenant.” — Julian Fischer, CEO, anynines
Q: What is the a9s Hub for on-premises and what use case does it address?
Alongside the AWS Hub, Fischer confirms anynines is building a Klutch hub for on-premises Kubernetes deployments. While the clip focuses primarily on the AWS architecture, the on-premises Hub represents the second major enterprise use case anynines is targeting as Klutch moves toward enterprise-grade maturity. Organizations running large Kubernetes footprints outside of public cloud will be the primary audience for this offering.
“Building a9s Hub in the two major use cases, which is a9s Hub for AWS and a9s Hub for on premises. That’s basically the idea.” — Julian Fischer, CEO, anynines
Q: What does it mean for Klutch to become enterprise grade and what has changed?
Fischer describes Klutch’s enterprise-grade evolution as a maturation process happening behind the scenes, involving additional integrations and the specific Hub configurations for AWS and on-premises. The core shift is moving from a capable platform into one that handles the large-scale, multi-tenant, governance-heavy use cases that enterprise customers require. The work has been ongoing and is now reaching the point of release-readiness.
“We’ve been building Klutch to maturity, we’ve been adding more integrations. So we are about to take Klutch and add what is necessary to become enterprise grade.” — Julian Fischer, CEO, anynines
Resources & Documentation
- anynines, company behind Klutch, building enterprise Kubernetes orchestration and governance tooling
- AWS Well-Architected Framework, AWS reference architecture used as the account structure foundation for the a9s Hub for AWS
- Amazon EKS, managed Kubernetes service referenced as the primary deployment target for the a9s Hub for AWS
***
👇 Click to Read Full Raw Transcript
Swapnil Bhartiya: Let’s talk about anynines and Klutch. What’s going on with anynines and where is Klutch heading?
Julian Fischer: Well, interesting question. Klutch is maturing. A lot has been happening behind the scenes. We’ve been building Klutch to maturity, we’ve been adding more integrations. So we are about to take Klutch and add what is necessary to become enterprise grade. Which means building a9s hub in the two major use cases which is any 9’s hub for AWS and a9s hub for on premises. That’s basically the idea. If you run a lot of kubernetes clusters let’s say on AWS and you are an EKS user using the well architected framework, how do you enable your users to get on demand self service while providing that central governance using Klutch as a central control plane for orchestration and governance. So if you do that then you will see that the well architected framework uses a particular layout and how AWS accounts are set out. For example, you have per tenant your own EKS account and your own account for services. So you have two accounts per tenant and you have potentially many tenants. When NIKS application clusters provision and the Klutch client is installed, it should be able to provision data services in the corresponding account that corresponds to the tenant. So those are features we’ve been adding behind the scenes making Klutch applicable to large scale use cases of the well architected framework.
