Post

Use the infrastructure that fits your team. Docker on a VM or Kubernetes. S3-compatible storage or a filesystem. Your existing identity provider. Notebook files, versions, and metadata live in your storage backend. The notebooks stay ordinary Python files.

Organize notebooks into projects, share data connections, and choose who can edit, view, or use an app. Publish interactive apps for teammates, schedule notebook jobs, and review or restore earlier versions—all from the same hub.

The deployment choice is the feature: teams can keep storage and identity where they already operate. The unglamorous test is version restore when a scheduled job fails.