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.
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 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.
The factory
fab turns an intake brief into shipped,
merge-gated software — an 80-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: IRSA,
ResourceQuota, NetworkPolicy, AppProject.
The substrate
landing-zone (OpenTofu/Terragrunt
AWS substrate), eks-gitops (the addon
catalog), and eks-fleet (the cluster
factory).
New here? Read the Overview for the mental model, then run the Quickstart to scaffold your first artifact from the catalog.