Deploying

marimohub ships as a single container image (apps/server/Dockerfile) that serves both the API and the web UI. Pick a platform below; each guide covers the image, configuration, the three backends (storage / compute / auth), and background maintenance.

• Helm — install/upgrade any cluster from the published, versioned marimohub chart (single-tenant).
• CoreWeave (CKS) — CAIOS + CoreWeave Sandboxes + OIDC.
• Kubernetes — any cluster (EKS/GKE/AKS/self-managed) with native Pod kernels via the kubernetes compute backend.
• GCP — GKE or Cloud Run + GCS.
• AWS — EKS or ECS/Fargate + native S3.
• Cloudflare — Workers + R2 + Containers + Access (serverless).

After deploy, validate the same core flow on every platform:

1. Check /healthz.
2. Sign in through the configured auth backend.
3. Create a project and notebook.
4. Start a kernel.
5. Save the notebook and confirm it survives a server restart.

See Configuration for every variable and Troubleshooting for common startup, login, and kernel failures.