Multi-user environment management for Pixi
⚠️ Alpha Software: Nebi is currently in alpha. APIs, UI, CLI and available features may change without notice. Not recommended for production use.
If your Python projects need compiled libraries like GDAL or CUDA, you know pip install often isn't enough. Pixi solves that by managing both Python packages and system libraries in one lockfile.
Nebi builds on Pixi to add what teams need: version history, rollback, sharing environments through registries, and access control over who can change production dependencies.
Key features:
- Install system libraries alongside Python packages (via Pixi)
- Push, pull, and diff versioned environments across machines
- Share environments through OCI registries (Quay.io, GHCR, etc.)
- Roll back when a dependency update breaks your workflow
- Control who can modify shared environments with role-based access
- Activate any workspace by name from any directory
Linux / macOS:
curl -fsSL https://nebi.nebari.dev/install.sh | shWindows (PowerShell):
irm https://nebi.nebari.dev/install.ps1 | iexSee install.sh --help or the script source for advanced options (--version, --install-dir, --desktop).
Start a local Nebi server (set your own admin credentials):
export ADMIN_USERNAME=admin
export ADMIN_PASSWORD=your-password
nebi serveThis starts the Nebi server at http://localhost:8460.
In a new terminal, connect the CLI to the server:
nebi login http://localhost:8460Initialize nebi in your project:
cd my-project
nebi initPush your environment to the server:
nebi push myworkspaceOr tag a specific version:
nebi push myworkspace:v1.0Once pushed, your workspace appears on the server dashboard:
Pull an environment on another machine:
nebi pull myworkspace:v1.0Verify what version you're running with nebi status:
nebi statusWorkspace: myworkspace
Path: /Users/you/my-project
Server: http://localhost:8460
Origin: myworkspace:v1.0 (pull)
- CLI Guide - Full CLI usage and workflows
- CLI Reference - All commands and flags
- Server Setup - Configuration and environment variables
- Architecture - How the CLI, server, and OCI registries fit together
API documentation is available at /docs on any running Nebi server (e.g. http://localhost:8460/docs).
See CONTRIBUTING.md for development setup, build instructions, and project structure.


