Skip to content

rackctl

One command takes an empty AWS account to a running, self-reconciling nanohype platform — then hands off to the portal for day-2.

rackctl is the OSS bootstrapper for nanohype — the agent-native platform. It automates the entire first-deploy-aws runbook: cloud substrate, EKS cluster, GitOps, controllers, and the operator portal, provisioned from zero and left reconciling on its own.

from empty account to running platform
# dry-run plan (default)
rackctl init -c rackctl.yaml
# provision for real
rackctl init -c rackctl.yaml --apply

Full provision

Cloud, cluster, IAM/Identity Center, GitOps, CRDs, operator, and optional portal — all from an empty AWS account. Not attach-to-existing; the whole stack, from scratch.

Dry-run by default

Every init is a plan until you pass --apply. Review exactly what will be created before a single cloud resource exists.

Orchestrates, doesn't rewrite

A thin engine over tofu, terragrunt, kubectl, helm, aws, git, and gh. It drives the real nanohype repos — landing-zone, eks-gitops, eks-agent-platform — it doesn’t reimplement them.

Reversible

A phase that fails rolls back in reverse. rackctl destroy tears the whole platform down in the opposite order it was built.

rackctl init walks an ordered pipeline. Phases 0–6 are the core 0→running path; 7–9 are opt-in layers you enable in rackctl.yaml.

# Phase What happens
0 Preflight Tools, AWS identity, and service quotas
1 Acquire Clone + fork the platform repos
2 Identity Identity Center and the Terraform state backend
3 Cluster Network and the EKS cluster
4 GitOps Secrets and the ArgoCD bootstrap
5 Addons Addon convergence and IRSA account-id writeback
6 Platform Agent-platform substrate, CRDs, and the operator
7 Fleet (opt-in) Crossplane cluster control plane
8 Portal (opt-in) The day-2 operator UI
9 Smoke (opt-in) A first-tenant smoke test

See the pipeline for the full detail, or jump to the quickstart.


Built on nanohype. Apache-2.0.