Products
Spec9 is for planning software when coding agents are part of the team. Kube9 is for running that software on Kubernetes once it ships. Different jobs, same people, same habit of writing things down before we build them.
Where product and engineering meet.
Product and engineering already work closer than most org charts admit. The trouble is that the feature lives in one place, the architecture lives in another, and the agent writing the code sees neither.
Spec9 puts both in one collection. Product writes what the software should do. Engineering draws how it fits together. Then the same coding agent you already use reads that collection, builds from it, and checks its work against it.
Write behavior as Given, When, Then steps in a feature tree. Tag scenarios with the personas they serve, and see the Gherkin update as you type.
Draw the architecture in C4. Double-click a system to drop into its containers, then again to reach the components inside.
Point Cursor, Claude, or Copilot at your collection over MCP. It pulls the slice it needs, builds from it, and validates the result.
Kubernetes tools for the people who actually run the clusters.
The VS Code extension works on its own. Add the operator for scheduled health checks, or try the desktop app if you'd rather have a dedicated IDE.
Your cluster, inside your editor
Browse every cluster in your kubeconfig, edit resources, tail logs, and manage Argo CD apps without leaving VS Code.
Health checks that run on their own
An open-source operator that runs Well-Architected Framework checks on a schedule and reports what it finds to the tools you already use.
An IDE built just for Kubernetes
A cross-platform desktop app with cluster management, Helm, Argo CD, a built-in terminal, and a Pro tier with AI that knows your cluster history.
Want the architecture and the privacy details? Read the Kube9 overview.
We build client products the same way we built these. Tell us what you have in mind.