Introduction
You’re in the Running Orchestra section: standing up and operating your own Orchestra instance on Kubernetes. Most people don’t need this — if you just want to attend, contribute, or teach a workshop, use the hosted platform at orchestraplatform.org and start from the documentation home.
What self-hosting gives you
Section titled “What self-hosting gives you”A private Orchestra instance provisions isolated, time-limited workshop sessions (RStudio, JupyterLab, or any container image) on demand, with sign-in and automatic cleanup handled for you. You run it when you need your own cluster, domain, catalog, or capacity controls rather than the shared hosted platform.
What you operate
Section titled “What you operate”Orchestra is a monorepo with four components:
- Operator — Kubernetes operator managing the Workshop CRD and session lifecycle.
- API server — FastAPI backend for templates, instances, and auth helpers.
- Frontend — React web dashboard.
- Sidecar — per-pod auth/proxy fronting each session.
Sessions run in isolated namespaces, each reachable at its own subdomain. See the Platform Overview for how the pieces fit.
Start here
Section titled “Start here”- Installation — quick-start an instance (local eval or Helm).
- Deploying Orchestra — the authoritative end-to-end operator runbook.
- Contribute a workshop — add a workshop to a catalog (hosted or your own).
Orchestra is open source; report issues, request features, or contribute on GitHub.