Glossary
These are the core terms used across the Nebari docs.
Capability
Section titled “Capability”Useful work your users can do, such as chatting with an LLM or analyzing documents. Different tools can provide the same Capability.
Learn more: Software Packs catalog
Cluster
Section titled “Cluster”One running instance of a Deploy Target, such as EKS on AWS or kind on your laptop.
Deploy Target
Section titled “Deploy Target”A kind of environment Nebari can be deployed to. Kubernetes is the only Deploy Target today. Bare metal, edge devices, and HPC clusters are possible future targets.
Learn more: NKP architecture
Ecosystem
Section titled “Ecosystem”Everything that makes up Nebari: the Deploy Targets it supports, the platforms built for them, the Software Packs that run on those platforms, and the community that builds and shares those packs.
Foundational software
Section titled “Foundational software”What Nebari installs on your cluster before any Software Pack: the shared services every pack relies on, such as login, routing, TLS, and observability. Like an operating system for packs.
Infrastructure
Section titled “Infrastructure”What your cluster runs on, plus everything around it: machines, networking, storage, and access permissions. Your Cluster Provider supplies it, for example an AWS account, a Hetzner server, or your laptop.
Landing page
Section titled “Landing page”The home page of your platform, where users sign in and open its Services.
Nebari Infrastructure Core (NIC) is the command-line tool, run as nic, that creates, updates, and removes your platform.
Learn more: Install NIC
Nebari Kubernetes Platform (NKP) is Nebari's platform for the Kubernetes Deploy Target.
Learn more: NKP architecture
Platform
Section titled “Platform”What your team builds on: the infrastructure, the cluster, and the foundational software. You install Software Packs on top of it.
Provider
Section titled “Provider”An outside service that NIC connects to while setting up your platform. There are three kinds:
- Cluster Provider: supplies your infrastructure and cluster, such as AWS, Hetzner, or your laptop.
- DNS Provider: manages the web addresses for your platform, such as Cloudflare.
- Repository Provider: hosts the Git repository your platform's setup is synced from.
Learn more: Providers
Service
Section titled “Service”What you end up with after installing a Software Pack: an app your users work in, such as JupyterHub or Grafana. Services provide Capabilities.
Software Pack
Section titled “Software Pack”What you install on your platform to add one or more Services. For example, the MLflow Pack installs the MLflow web app (a Service), which provides experiment tracking and a model registry (Capabilities).
Learn more: Pack architecture