Last regenerated: 2026-07-03T16:07:25Z. Trigger a refresh via the Refresh pack dashboard workflow.
- 0 GA · 8 Beta · 5 Alpha · 4 Experimental · 0 Deprecated
- 0 packs flagged
| Pack | Description | Level | Owner | NebariApp | Standalone | Last release | Last commit | Flags | Notes |
|---|---|---|---|---|---|---|---|---|---|
| Data Science Pack | Multi-user JupyterHub with Nebari's data science images and jhub-apps for publishing notebooks, dashboards, and apps from the browser. | Beta | @aktech | N/A | – | nebari-data-science-pack-0.1.0 (Jun 19) | Jul 03 | – | – |
| LLM Serving Pack | Self-hosted LLM serving via llm-d. Includes per-model OIDC access control, API key management, and Envoy AI Gateway token counting and rate limiting. | Beta | @dcmcand | Full | Yes | v0.1.0-alpha.9 (Jun 16) | Jul 03 | – | – |
| Chat Pack | A drop-in chat application wired into Keycloak SSO, with a React frontend and a Ravnar/AG-UI backend. | Alpha | @pmeier | N/A | – | v0.0.13 (Jun 18) | Jul 03 | – | – |
| Nebi Pack | Nebi environment management for teams: versioned, shareable Pixi environments with rollback, backed by Keycloak SSO and PostgreSQL. | Beta | @aktech | N/A | – | nebari-nebi-pack-0.1.1 (Jul 02) | Jul 03 | – | – |
| Capability Pack | Deploy Python services from a pixi manifest with one CRD. The capability operator wires each service with routing, TLS, and Keycloak OIDC on a shared hostname. | Experimental | @nenb | N/A | – | – | Jul 03 | – | – |
| LGTM Pack | Cluster observability with the Grafana LGTM stack: Loki logs, Tempo traces, Mimir metrics, and Grafana dashboards. | Beta | @tylerpotts | N/A | – | nebari-lgtm-pack-0.1.4 (Jun 19) | Jul 03 | – | – |
| Superset Pack | Apache Superset dashboards and SQL exploration with Keycloak OAuth and NebariApp routing. Also installs standalone on non-Nebari clusters. | Beta | @dcmcand | Full | Yes | v0.3.1 (Apr 09) | Jul 03 | – | – |
| Rayserve Pack | Scalable model serving with Ray Serve through the RayService CRD, with optional routing, TLS, and OIDC via the nebari-operator. | Beta | @oren-openteams | Full | Yes | v0.3.1 (Jun 19) | Jul 03 | – | – |
| MLflow Pack | MLflow experiment tracking and model registry with Keycloak authentication, a PostgreSQL backend, and automatic TLS. | Alpha | @tylerpotts | N/A | – | v0.1.0-alpha.1 (Jun 18) | Jul 03 | – | – |
| Data Engineering Pack | Airflow orchestration and Marquez lineage tracking with OpenLineage defaults, wired into Nebari routing, TLS, and Keycloak auth. Modular components with demo-to-production deployment profiles. | Experimental | @ns-mkusper | Full | Yes | v0.1.0-alpha.0 (Jun 18) | Jul 03 | – | – |
| External Auth Pack | Connects users' external accounts (GitHub and other providers) and delivers their credentials into Nebari-launched notebooks, IDEs, and apps. | Experimental | @ns-mkusper | Full | Yes | – | Jul 03 | – | – |
| Longhorn Backup Pack | Hourly Longhorn snapshots and daily S3 backups for every volume on the cluster's default StorageClass. | Alpha | @tylerpotts | N/A | – | v0.3.0 (Jun 18) | Jul 03 | – | – |
| Provenance Collector | Scheduled supply-chain provenance reports: discovers running images and Helm releases, resolves digests, verifies signatures, and checks SLSA/SBOM attestations. | Alpha | @viniciusdc | Full | Yes | v0.1.0-alpha.4 (May 14) | Jul 03 | – | – |
| Pi Coding Agent Pack | Extends Nebari's JupyterHub with a Pi coding-agent workflow: named-server profiles, session sharing, and optional relay adapters. | Experimental | @nenb | N/A | – | – | Jul 03 | – | – |
| skillsctl | CLI and registry server for discovering, installing, and publishing Claude Code skills | Beta | @dcmcand | Full | Yes | v0.2.0 (Apr 15) | May 15 | – | – |
| Langfuse Pack | Langfuse LLM observability: tracing, evals, prompt management, and metrics for debugging and improving LLM apps. | Alpha | @dcmcand | Full | Yes | nebari-langfuse-0.1.0 (Jun 11) | Jul 03 | – | App-native Keycloak SSO; set the Keycloak issuer and hostname in values. Bundled datastores use fro… |
| Nebari Frames | Nebari Frames is the registry and exchange for Frames: scoped, text-based artifacts that carry organizational context into AI conversations. | Beta | @dcmcand | Full | Yes | v0.1.5 (Jul 03) | Jul 03 | – | MCP/Claude requires manual realm config (enable DCR + default-scope audience mapper); see docs/conn… |
- Pack - Pack name (from
display_name), linked to its GitHub repo. - Description - One-line summary of what the pack does. Sourced from the GitHub repo description (set via repo settings or
gh repo edit -d). - Level - Maturity level: Experimental, Alpha, Beta, or GA. Definitions and promotion criteria live in the release readiness checklist. Sourced from
levelin pack-metadata.yaml. - Owner - GitHub handle of the engineer accountable for the pack. From
ownerin pack-metadata.yaml. - NebariApp - How the pack integrates with the NebariApp CRD: Full, Partial, None, or N/A. From
nebariapp_integration. - Standalone - Whether the pack installs without the Nebari operator. From
scope.standalone-supported. - Last release - Most recent published release tag (including prereleases). Falls back to the latest git tag if no GitHub Release records exist. Sourced from the GitHub API.
- Last commit - Date of the most recent commit on the default branch. Sourced from the GitHub API.
- Flags - Auto-computed status flags. See the Flag reference below.
- Notes - Free-form
demo_notesfrom pack-metadata.yaml (truncated at 100 chars). For packs with validation errors, the error message appears here instead.
- 🆘 metadata-missing - Pack repo has no
pack-metadata.yamlfile. Pack-author fields show–. ⚠️ metadata-invalid -pack-metadata.yamlexists but failed validation. The specific error appears in the Notes column.- 🆘 repo-not-found - Pack repo could not be reached. Check the
tracked-packs.yamlentry. ⚠️ stale - Default branch has had no commits in the last 90 days.⚠️ no-product-owner - Pack is GA butproduct_owneris null in its metadata.- 🚫 deprecated - Pack is marked
deprecated: true. See the Deprecated packs table for sunset details.
Each row is built from two sources: a pack-metadata.yaml file at the root of each pack repo (edited by the pack's owner) and a small set of GitHub API fields (latest release, last commit, open issues).
To add a pack to this dashboard:
- Copy
schema/pack-metadata.example.yamlinto your pack repo aspack-metadata.yaml, fill in the required fields, and merge to your default branch. - Open a PR against this repo adding your pack to
tracked-packs.yaml.
See CONTRIBUTING.md for the full walkthrough.
Generated: 2026-07-03T16:07:25Z