MarimoHub
Running one marimo notebook is easy; running a team's worth of them, with storage, sign-on, versions, and somewhere for the results to live, is the job MarimoHub takes on. Notebooks gather in a searchable gallery organized by project, where every edit session leaves a version you can compare side by side, inspect, and restore when an experiment takes a wrong turn. Projects connect their data sources once through a versioned integration catalog, with sensitive values encrypted or pulled from external secret stores, and every new session receives the configuration automatically. When a notebook is ready for people who should never see its code, publish it as an interactive app: viewers get the controls and outputs while rollouts shift versions underneath them. Scheduled jobs rerun notebooks on a clock, GitHub sync keeps repository-backed notebooks current, and an assistant can work inside the notebook context with managed AI keys that never reach the sandbox. Underneath, you pick the object storage, the compute, and the identity provider, and back up one bucket to back up the whole hub. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.
Deploy