Nanocl is an open source distributed system designed to revolutionize cloud native from the ground up.
The developing ecosystem provides an easy solution for local development, avoiding common issues like CORS & cookies when working with complex microservices.
The architecture of Nanocl enables a seamless deployment to production among other innovations.
You could build a K8s within Nanocl. But we are quite sure you wouldn't want to..
Nanocl will introduce the next paradigm for Platform Engineers by providing ground breaking cloud-native architectural innovations, best-in-class security, while reducing operational costs with e.g. 🦀 Rust based efficiency.
Who said that K8s is more than a perfect platform for application workloads?
We are already compatible with Linux, MacOS & Windows, just jump to Installation guide.
Please bare with us, Nanocl is currently more than just on the cutting edge..
- Blog: Automating deployment with GitHub Actions on 24.11.2024
- Release: End to End TLS encryption and first step for network meshing on 01.11.2024
- Release: Man page, Backup, Remove Orphans and more on 11.06.2024
- Event: We are invited to the Merge Berlin 2024 on 01.06.2024
- Release: Context, SubState and more on 07.05.2024
Nanocl is designed to be easy to setup, use & maintain by mostly using Statefiles (yaml
, toml
or json
).
Below is an example which is used to deploy our own Documentation.
• Apply
a state to the cluster via nanocl state apply -s path|url
• Remove
it by executing nanocl state rm -s path|url
ApiVersion: v0.16
# Options: https://docs.next-hat.com/references/nanocl/objects/cargo
Cargoes:
- Name: doc
Container:
Image: ghcr.io/next-hat/documentation:0.16.0
# Options: https://docs.next-hat.com/references/nanocl/objects/resource
Resources:
- Name: docs.next-hat.com
Kind: ncproxy.io/rule
Data:
Rules:
- Domain: docs.next-hat.com
Network: Public
Locations:
- Path: /
Target:
Key: doc.global.c
Port: 80
Nanocl is designed as a microservice architecture, consisting of multiple components running as containers, including the Nanocl Daemon itself.
The following components will be installed during nanocl install
and are required to ensure full Nanocl functionalities:
nstore
to save cluster statendaemon
as REST API to manage everythingnmetrics
to monitor CPU, Memory and Network usagenproxy
proxy to redirect traffic to our containers and virtual machines (optional)ncproxy
to update proxy configuration based on the current state (optional)ndns
to manage the dns entries for the containers and virtual machines (optional)ncdns
to update dns entries based on the current state (optional)
To learn more about Nanocl, take a look at the following resources:
Simplified version of Nanocl architecture for a single node:
Little by little, a little becomes a lot.
Join our Discord the be part of NextHat's journey to shape the future of planet-scale infrastructure management.
Every contribution is welcomed.
➡️ Bug reports, feature requests, and pull requests are the most common ways to contribute.
For example if you're not a developer yourself you could help us by improving the Documentation, too.
Learn how to setup a development environment via the Contribution Guide.
Please don't hesitate to join our team on Discord if you have any questions! 🤗
GitHub ⭐️ helps us a lot to further grow our open-source ecosystem for & with our community.
Sponsors are the ones who make this project possible.
They help us to have the necessary resources for Nanocl to keep it alive and to improve it further.
If you want to become a sponsor, please use the GitHub Sponsor button.
People that sponsor us will have their name or logo displayed here, and will have access to a special role on our Discord.
Our very kind sponsors:
mamaicode |
xf10w |
Rembo1510 |
We are just at the beginning of a new paradigm shift..