mctl.ai
AI-native platform for Kubernetes and cloud ops
Start new thread
Dmitrii Mashkov

mctl.ai - AI-native platform for Kubernetes and cloud ops

by•
MCTL is an AI-native platform for Kubernetes and cloud infrastructure. It gives growing teams GitOps, secrets, team isolation, and AI-assisted workflows out of the box, so they can operate like a mature platform team without building one first.

Add a comment

Replies

Best
Dmitrii Mashkov
Maker
📌
Hey Product Hunt! 👋 We built MCTL because too many teams want the benefits of Kubernetes, but end up paying for it with platform overhead. In practice, “adopting Kubernetes” often means assembling GitOps, secrets, access control, deployment workflows, internal tooling, and team isolation from scratch — then hiring people to keep it all running. We wanted a simpler path. MCTL is an AI-native Kubernetes platform for growing product teams. It brings GitOps, secrets management, team isolation, and self-service workflows into one stack, with multiple ways to operate it: portal, API, CLI, or even natural language. The goal is straightforward: help teams ship on Kubernetes without waiting on tickets or building a dedicated platform team first. We’re especially interested in feedback from founders, product teams, and engineers who felt Kubernetes was “too much” for their stage. Where does the friction still show up for you?
Mykola Kondratiuk

The "operate like a mature platform team without building one first" pitch resonates. A lot of growing teams hit this wall around 15-20 engineers where Kubernetes complexity outpaces their ops capacity. Curious how you handle the handoff when they actually do want to build a custom internal platform - does MCTL export configs cleanly or is there some lock-in?

Dmitrii Mashkov
Maker

@mykola_kondratiuk 
Our goal with mctl.ai is to accelerate teams, not lock them in. Everything we generate — infrastructure configs, workflows, and policies — is designed to be transparent, portable, and exportable (standard Kubernetes manifests, Terraform, etc.). So when a team is ready to evolve into a fully custom internal platform, they can take what they’ve built with MCTL and extend it without starting from scratch.

In a way, we see MCTL as a bridge to a mature platform team, not a replacement for one

Mykola Kondratiuk

Kubernetes manifests + Terraform as output is the right call. Standard tooling means the configs stay yours - you can take them into any pipeline without being tied to how they were generated. Makes adoption smoother too when teams don't need to learn a new abstraction layer on top of infra they already own.