The catalog
Templates and composites in nanohype —
the factory’s vocabulary. The SDK and MCP server render them; the standards are
the bar every output is graded against.
agent factory
nanohype
A template + composite catalog, a factory client that ships merge-gated software, and the k8s-native substrate it deploys onto — one system, from idea to running tenant.
$ npx @nanohype/sdk scaffoldnanohype is a k8s-native software factory. Every repo in the org plays one of three roles: factory context (what the factory consumes when designing work), factory output (what it produces), or the factory itself (the orchestrator). The result: an idea becomes a production tenant — chart, tenant boundary, and GitOps entry — deployed on the client’s own cloud.
The shape of it
Section titled “The shape of it”The factory
fab turns an intake brief into shipped,
merge-gated software — a 78-role roster organized by phase, four transports, and
an evidence-bound merge gate.
The platform
eks-agent-platform is the
k8s-native control plane. A Platform CR draws a tenant boundary: Pod
Identity, ResourceQuota, NetworkPolicy, AppProject.
The substrate
landing-zone (OpenTofu/Terragrunt
AWS substrate), eks-gitops (the addon
catalog), and eks-fleet (the cluster
factory).
Where to start
Section titled “Where to start”Two ways in, depending on what you came for.
Evaluating it
The atlas is ten diagrams of the whole system — the fastest way to see how the layers fit. Then how the factory works for the mental model, and repos for what each one owns.
Building against it
The Platform Reference is the front door for an agent. For hands on keyboard, the Quickstart scaffolds your first artifact, and the catalog is every template and composite with its variables and output.