Nyl

[ DOCUMENTATION ]

Configuration in Git,
turned into deployed systems.

Render Kubernetes manifests, publish them for Argo CD or Flux, and orchestrate beyond Kubernetes. Adopt one layer at a time, from one config.

Get started →Read the introduction

~/platform

$ nyl init platform --minimal
$ cd platform
$ nyl create component v1.example.io MyApp

platform/
├── nyl.toml        project configuration
├── components/     reusable components
├── applications/   application sources
└── config/         clusters, targets, repositories

FIND YOUR WAY

Adopt it one layer at a time.

Take what you need. If Kubernetes is all you deploy, you never need Orchestration.

1

START HERE

Kubernetes Rendering

Helm charts and reusable components, rendered from one config.

BEST FOR

Testing, small teams, bootstrapping, break-glass.

2

Kubernetes GitOps

Rendered manifests committed to Git: full history, faster reconciliation.

BEST FOR

Argo CD and Flux users.

3

IN DEVELOPMENT

Orchestration

GitOps reconciliation beyond Kubernetes.

BEST FOR

Systems that span more than Kubernetes.

4

PLANNED

Domain modeling

A foundation for building your internal developer platform on the layers above.

BEST FOR

Platform teams building self-service for their developers.

4

Domain modelingPLANNED

A foundation for building your internal developer platform on the layers above.

BEST FOR

Platform teams building self-service for their developers.

ReferenceEvery command, resource, and nyl.toml setting.Open reference →