marimo is a reactive notebook for Python that models notebooks as dataflow graphs. When you run a cell or interact with a UI element, marimo automatically runs affected cells (or marks them as stale), keeping code and outputs consistent and preventing bugs before they happen. Every marimo notebook is stored as pure Python, executable as a script, and deployable as an app.
Key features:
To get started with marimo on Spaces, click the button below:
This will start building your Space using marimo’s Docker template. If successful, you should see a similar application to the marimo introduction notebook.
When you create a marimo Space, you’ll get a few key files to help you get started:
This is your main marimo notebook file that defines your app’s logic. marimo notebooks are pure Python files that use the @app.cell
decorator to define cells. To learn more about building notebooks and apps, see the marimo documentation. As your app grows, you can organize your code into modules and import them into your main notebook.
The Dockerfile for a marimo app is minimal since marimo has few system dependencies. The key requirements are:
requirements.txt
(using uv
)marimo run app.py
You may need to modify this file if your application requires additional system dependencies, permissions, or other CLI flags.
The Space will automatically install dependencies listed in the requirements.txt
file. At minimum, you must include marimo
in this file. You will want to add any other required packages your app needs.
The marimo Space template provides a basic setup that you can extend based on your needs. When deployed, your notebook will run in “app mode” which hides the code cells and only shows the interactive outputs - perfect for sharing with end users. You can opt to include the code cells in your app by setting adding --include-code
to the marimo run
command in the Dockerfile.
If you encounter issues:
marimo run app.py
requirements.txt
For more help, visit the marimo Discord or open an issue.
< > Update on GitHub