# nanohype > The k8s-native software factory: a template and composite catalog, a factory > client that ships merge-gated software, and the substrate it deploys onto. Everything under /catalog/, /platform/resources/ and /atlas/ is generated at build time from the org's own artifacts — the catalog manifests, the shipped CRDs, and the emitted diagrams — so this site cannot describe a template, a resource kind or a field that does not exist. The pages under /repos/ render each repo's AGENTS.md as it stands today rather than a copy of it. ## Documentation - [nanohype](https://docs.nanohype.dev/): The k8s-native software factory — a template + composite catalog, a factory client that ships merge-gated software, and the substrate it deploys onto. - [Templates & catalog](https://docs.nanohype.dev/catalog/): The template and composite catalog — the factory's vocabulary — and how the SDK and MCP server render it. - [How the factory works](https://docs.nanohype.dev/factory/): From an intake brief to merge-gated, shipped software — the fab pipeline and its phases. - [How this fails](https://docs.nanohype.dev/failure-modes/): The failure class a Kubernetes platform actually has — every object valid, every controller healthy, and the path through them dead — with the shapes it takes here, what to look at, and what healthy looks like. - [Platform tenants](https://docs.nanohype.dev/platform/): The Platform CR — the tenant boundary the eks-agent-platform operator reconciles. - [Quickstart](https://docs.nanohype.dev/quickstart/): Scaffold your first artifact from the nanohype catalog, and see how it becomes a Platform tenant. - [The substrate](https://docs.nanohype.dev/substrate/): Where cloud and cluster live — landing-zone, eks-gitops, eks-fleet — and the boundaries between them. ## Building against it - [Platform Reference](https://docs.nanohype.dev/building/platform-reference/): The agent-consumable front door: the stack, the layer boundaries, the contract repos, and the SDK and MCP entry points. - [Catalog reference](https://docs.nanohype.dev/building/catalog-reference/): Which template to reach for, how templates compose, and the module layering from a minimal API up to a full platform. - [Composites](https://docs.nanohype.dev/building/composites/): What a composite is, how one is assembled, and when to reach for it over a single template. - [Production readiness](https://docs.nanohype.dev/building/production-readiness/): The cumulative checklist a scaffolded project clears before it is deployed. - [Authoring a template](https://docs.nanohype.dev/building/authoring-a-template/): Creating a new template, from empty directory to validated and catalog-ready. - [Template contract](https://docs.nanohype.dev/building/template-contract/): The formal specification a template manifest is validated against — every field, every rule. - [Composite contract](https://docs.nanohype.dev/building/composite-contract/): The formal specification for a composite: how it names its templates and threads variables through them. - [Building a consumer](https://docs.nanohype.dev/building/consumer-guide/): How to build a scaffolding tool that renders nanohype templates — the action doc behind the two contracts. - [The Platform Reference pattern](https://docs.nanohype.dev/building/reference-pattern/): The structure generalised: how any platform can publish an agent-consumable front door of its own. ## Architecture decisions - [Architecture decisions](https://docs.nanohype.dev/decisions/): The load-bearing choices — what each one is constrained by, what was chosen, what was rejected, and what the choice costs. - [Crossplane orders the IaC](https://docs.nanohype.dev/decisions/crossplane-ordering/): Why vending a cluster is a Kubernetes object that runs the OpenTofu modules, rather than a second definition of the same infrastructure. - [Identity is bound, not annotated](https://docs.nanohype.dev/decisions/identity-binding/): Why a tenant's AWS identity comes from an EKS Pod Identity association the operator creates, and never from a role ARN in the tenant's chart. - [The kill switch changes AWS, not the cluster](https://docs.nanohype.dev/decisions/kill-switch/): Why stopping a runaway tenant detaches an IAM policy and tags a role, and leaves the operator to notice rather than to act. - [Layers are drawn by rate of change](https://docs.nanohype.dev/decisions/layer-boundaries/): Why the same change has exactly one correct repo, and how to tell which one without asking. - [One account holds a whole product](https://docs.nanohype.dev/decisions/one-account/): Why a product's network, cluster, tenants and data live in a single AWS account, and what the create/adopt modes are for. - [A tenant's substrate is a declaration](https://docs.nanohype.dev/decisions/tenant-substrate/): Why databases, buckets, queues, caches and streams are a list on the Platform CR rather than a hand-written component per app. ## Repos - [cloudgov](https://docs.nanohype.dev/repos/cloudgov/): Governance CLI — AWS security and cost posture — IAM least-privilege, spend, infrastructure hygiene, drift — plus a conformance auditor for Platform tenants. - [eks-agent-platform](https://docs.nanohype.dev/repos/eks-agent-platform/): The control plane — The CRDs a tenant is declared in — Platform, AgentFleet, ModelGateway, BudgetPolicy, EvalSuite — and the operator that reconciles them, including the per-tenant AWS identity and access it mints. - [eks-fleet](https://docs.nanohype.dev/repos/eks-fleet/): The cluster factory — Vending EKS clusters from a namespaced Cluster resource, via a Crossplane composition that runs the landing-zone modules and writes the result back to status. - [eks-gitops](https://docs.nanohype.dev/repos/eks-gitops/): Cluster addon catalog — What ArgoCD installs on a cluster once it exists: cert-manager, external-secrets, Kyverno, the observability stack. Charts, not cloud resources. - [fab](https://docs.nanohype.dev/repos/fab/): The factory client — Orchestration across the build phases, the agent roster, the merge gate, and the baseline skills. Open source, so the factory can be cloned and run rather than only described. - [kx](https://docs.nanohype.dev/repos/kx/): The local cluster — A kind workspace mirroring the eks-gitops catalog, so the same charts run locally before they run on EKS. - [landing-zone](https://docs.nanohype.dev/repos/landing-zone/): Cloud substrate — The slow-moving AWS layer — VPC, base IAM, KMS, DNS, cluster vending — as OpenTofu components driven by Terragrunt, plus the generic module that provisions a tenant's datastores from its declaration. - [nanohype](https://docs.nanohype.dev/repos/nanohype/): The factory's vocabulary — Templates, composites, standards, the SDK and the MCP server. What every other repo is described in terms of. - [portal](https://docs.nanohype.dev/repos/portal/): The operations portal — Running the substrate from one UI with one audit trail: a Go API and a React SPA over the same components the CLI drives. ## Generated reference - [Templates](https://docs.nanohype.dev/catalog/templates/): 90 templates in the catalog, each with its manifest, variables and rendered file tree. - [Composites](https://docs.nanohype.dev/catalog/composites/): 25 composites, each naming the templates it draws in and how variables thread through them. - [Standards](https://docs.nanohype.dev/catalog/standards/): 11 machine-readable standards — the production bar every deliverable is graded against. - [Platform resources](https://docs.nanohype.dev/platform/resources/): 10 custom resources the control planes ship, generated from the CRDs themselves — every field, every version. - [The atlas](https://docs.nanohype.dev/atlas/): 11 generated diagrams of the stack, each answering one question about it.