Post

Introducing marimohub 🌊 Your team's notebooks. Your infrastructure. An open-source platform to run and share marimo notebooks with your own compute, storage, and SSO. No separate database to operate. Read @themylesfiles' announcement and get started: marimo.io/blog/introd...

marimo.ioIntroducing marimohubA self-hostable notebook platform to store, manage, and run marimo notebooks on your own infrastructure.

2/10/26, 7:53 pm3 reposts9 likes

marimo

@marimo.io

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.

marimo

@marimo.io

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.

marimo

@marimo.io

marimohub is out, free and open source under Apache 2.0. Watch Vincent's walkthrough: www.youtube.com/watch?v=1wn...

youtube.comOut now: marimohubmarimohub is out now. With it, you can create a platform for your t...

marimo

@marimo.io

marimohub announcement closes our launch week. All announcements, in one place: marimo.io/blog/launch... Head over to our Reddit and Discord and let us know, what is the most useful for your workflow: pixi, fsspec, lens, studio or the hub?

marimo.iomarimo is doing another launch weekWe're back for round two. One week, five announcements. Can you guess what's coming?

The Projekt

@wearetheprojekt.bsky.social

Self-hosting changes the product question from feature count to operational fit. Existing identity and storage reduce another migration, but restore testing still matters. Which workflow gets the first production trial?

The Projekt

@wearetheprojekt.bsky.social

Self-hosting is compelling when identity and storage fit existing systems. The cost usually appears in restore tests and permission edges. Which deployment path will teams try first?