Infrastructure

How Nanokit provisions and operates the substrate your services run on.

Pages

Page	What it covers
Fleet Provisioning	Declaring instances, roles and scaling in infra.instances
Kubernetes	Live cluster deploys (infra.target: kubernetes) vs. the offline export k8s / export helm escape hatches
Persistent Storage & Volumes	Named volumes locally, EFS on AWS, block storage on DigitalOcean
Mail & SMTP	Self-hosted mail vs. managed providers (SES, ACS, plain SMTP)

Related

• Providers — the capability matrix: Docker, AWS, Azure, GCP, DigitalOcean (plus Cloudflare for DNS only).
• infra configuration — the nanokit.yml block.
• nkapp infra — apply, inspect live resources, destroy, unlock.
• Edge Networking — the Caddy gateway, TLS and DNS sync.

Keeping a host healthy

Infrastructure that is never cleaned up eventually fails a deploy. Detection is automatic in nkapp doctor (Container Hygiene and Image Space); removal is explicit and guarded:

• nkapp volumes prune — orphaned volumes
• nkapp containers prune — stale containers
• nkapp images prune — unused images
• nkapp infra resources --orphans — cloud resources not declared in nanokit.yml