Introduction

Nanokit is an agent-native infrastructure control plane. It bridges the gap between local development and multi-environment cloud deployments with a focus on determinism and developer experience: one declarative file describes the stack, and a reconcile loop makes reality match it.

Why Nanokit?

In a world of complex Kubernetes manifests and opaque cloud consoles, Nanokit provides a clear, declarative, and high-performance alternative.

• 🚀 Full Parity: Work on Local, Staging, and Production with the exact same configuration.
• 🛠️ Developer-First CLI: nkapp up for the inner loop, nkapp deploy to ship.
• 🌐 Automatic Networking: Built-in Caddy gateway with automated SSL (ACME) and local trust.
• ⚡ Resilient Telemetry: Real-time monitoring of your services across environments via the Nanokit Bridge.
• 🔐 Secure by Default: Native integration with Vault for secrets and automated SSH tunnel isolation.

Getting Started

To start your journey with Nanokit, we recommend following these steps:

1. Installation: Learn how to install the nkapp CLI on your machine.
2. First Project: Use nkapp init to scaffold your first application.
3. Local Dev: Run nkapp up -e local to see your services live with secure HTTPS.
4. Deploy: Move to a VPS or the cloud with nkapp deploy.

Core Concepts

Nanokit is built on three main pillars:

The CLI (nkapp)

A deterministic tool that reconciles the desired state defined in nanokit.yml with the actual infrastructure. nkapp up owns the service reconcile; nkapp deploy owns provisioning, code sync and shipping.

The Bridge

A background process that connects your local machine to remote environments, providing telemetry, logs, and control without exposing your servers. It is started and managed for you by nkapp up.

The Config (nanokit.yml)

A single, declarative YAML file that describes your entire application stack, from Docker images to cloud networks and database branches.