<div align="center" <img width="142" height="142" src="https://download.next-hat.com/ressources/images/logo.png" <h2Nanocl</h2 <h4Just Develop, Deploy.</h4 <h6Orchestrate like never before. K8s reimagined.</h6 <p align="center" <a href="https://next-hat.com/nanocl"<bWhy</b</a • <a href="https://docs.next-hat.com/manuals/nanocl/install/overview"<bInstall</b</a • <a href="https://discord.gg/WV4Aac8uZg" target="blank"<bDiscord</b</a • <a href="https://x.com/nexthat" target="blank"<b𝕏</b</a </p <p
</p </div
Quick install (requires Docker)
curl -fsSL https://download.next-hat.com/scripts/get-nanocl.sh | shThen complete the required [Post‑installation steps][postinstall].
Nanocl is an open‑source distributed system that reimagines cloud‑native orchestration from the ground up.
It gives developers a frictionless local to production workflow while hiding multi‑service complexity (no more ad‑hoc scripts, CORS hacks, or brittle docker‑compose sprawl). The same declarative model powers both dev and prod.
You could rebuild a K8s inside Nanocl… but you probably won't want to.
Built in 🦀 Rust for efficiency & security, Nanocl targets platform engineers who need strong isolation, predictable performance, and simpler operations—without the cognitive overhead of a full Kubernetes distribution.
Table of Contents
- Why Nanocl
- Key Features
- Installation
- Quick Start
- Latest news
- Usage
- Architecture
- Demo
- Roadmap
- Security
- Contribute
- Support & Community
- Sponsors
- License
- Star History
Why Nanocl
Modern teams need faster iteration loops, secure multi‑tenant isolation, and a production‑grade transition path—without operating a heavyweight control plane on day one. Nanocl focuses on:
- Dev→Prod symmetry: declarative Statefiles (YAML/TOML/JSON) stay identical across environments.
- Low operational overhead: minimal moving parts; opinionated defaults.
- Security & efficiency: memory‑safe implementation, reduced footprint versus scripting stacks.
- Extensibility: resources & rules let you model networking, routes, TLS, jobs, and more.
- Pragmatic scope: not a Kubernetes clone—lean where K8s is heavy, expressive where docker‑compose is limiting.
Key Features
- Declarative Statefiles for cargoes (containers), resources, jobs & virtual machines.
- End‑to‑end TLS (including internal mesh primitives in progress).
- Dynamic routing & DNS propagation (ncproxy, ncdns).
- Resource abstraction layer for pluggable kinds (e.g. proxy rules).
- Jobs & cron style automation.
- Backup & orphan cleanup tooling.