For GSoC, checkout our Google Summer of Code 2026 guide
Mesa: Agent-based modeling in Python
| CI/CD |   |
| Package |    |
| Meta |     |
| Chat |  |
| Cite |  |
Mesa allows users to quickly create agent-based models using built-in core components (such as spatial grids and agent schedulers) or customized implementations; visualize them using a browser-based interface; and analyze their results using Python's data analysis tools. Its goal is to be the Python-based alternative to NetLogo, Repast, or MASON.
Above: A Mesa implementation of the WolfSheep model, this can be displayed in browser windows or Jupyter. An online demo is available here.
Features
- Modular components
- Browser-based visualization
- Built-in tools for analysis
- Example model library
Using Mesa
To install our latest stable release, run:
pip install -U mesa
Starting with Mesa 3.0, we don't install all our dependencies anymore by default.
# You can customize the additional dependencies you need, if you want. Available are:
pip install -U "mesa[network,viz]"
# This is equivalent to our recommended dependencies:
pip install -U "mesa[rec]"
# To install all, including developer, dependencies:
pip install -U "mesa[all]"
You can also use pip to install the latest GitHub version:
pip install -U -e git+https://github.com/mesa/mesa@main#egg=mesa
Or any other (development) branch on this repo or your own fork:
pip install -U -e git+https://github.com/YOUR_FORK/mesa@YOUR_BRANCH#egg=mesa
Resources
For resources or help on using Mesa, check out the following:
- Getting Started (A collection of tutorials that will walk you through a basic model.)
- GSoC at Mesa — Candidates Guide (For candidates interested in participating in the Google Summer of Code at Mesa)
- Mesa Examples (A repository of seminal ABMs that are part of the Mesa[rec] install and use the most current Mesa release)
- Docs (Mesa's documentation, API and useful snippets)
- Development version docs (the latest version docs if you're using a pre-release Mesa version)
- Discussions (GitHub threaded discussions about Mesa)
- Matrix Chat (Chat Forum via Matrix to talk about Mesa)
Running Mesa in Docker
You can run Mesa in a Docker container in a few ways.
If you are a Mesa developer, first install Docker Compose and then, in the folder containing the Mesa Git repository, you run:
$ docker compose up
# If you want to make it run in the background, you instead run
$ docker compose up -d
This runs the Schelling model, as an example.
With the docker-compose.yml file in this Git repository, the docker compose up command does two important things:
- It mounts the mesa root directory (relative to the docker-compose.yml file) into /opt/mesa and runs pip install -e on that directory so your changes to mesa should be reflected in the running container.
- It binds the docker container's port 8765 to your host system's port 8765 so you can interact with the running model as usual by visiting localhost:8765 on your browser
If you are a model developer that wants to run Mesa on a model, you need to:
- make sure that your model folder is inside the folder containing the docker-compose.yml file
- change the
MODEL_DIRvariable in docker-compose.yml to point to the path of your model - make sure that the model folder contains an app.py file
Then, you just need to run docker compose up -d to have it
accessible from localhost:8765.
Contributing to Mesa
Want to join the Mesa team or just curious about what is happening with Mesa? You can...
- Join our Matrix chat room in which questions, issues, and ideas can be (informally) discussed.
- Come to a monthly dev session (you can find dev session times, agendas and notes on Mesa discussions).
- Just check out the code on GitHub.
If you run into an issue, please file a ticket for us to discuss. If possible, follow up with a pull request.
If you would like to add a feature, please reach out via ticket or join a dev session (see Mesa discussions). A feature is most likely to be added if you build it!
Don't forget to checkout the Contributors guide.
Citing Mesa
To cite Mesa in your publication, you can refer to our peer-reviewed article in the Journal of Open Source Software (JOSS):
- ter Hoeven, E., Kwakkel, J., Hess, V., Pike, T., Wang, B., rht, & Kazil, J. (2025). Mesa 3: Agent-based modeling with Python in 2025. Journal of Open Source Software, 10(107), 7668. https://doi.org/10.21105/joss.07668
Our CITATION.cff can be used to generate APA, BibTeX and other citation formats.
Release files for Mesa 3.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mesa-3.5.1.tar.gz | 673.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mesa-3.5.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 948.3 kB
Release files / mesa-3.5.1.tar.gz
| Download URL | mesa-3.5.1.tar.gz |
|---|---|
| Size | 673.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3f2dce3b8cbe2d89e0ec29e843176788b8cb170413c2cc7def9dbc6339752d78
|
|
BLAKE2b-256 checksum How to use checksums |
53e9f92b5cd00b4768bcc3d3d81ebbafc78b3ffc74296b9440cf2a6370a3840a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 15, 2026.
Transparency logRelease files / mesa-3.5.1-py3-none-any.whl
| Download URL | mesa-3.5.1-py3-none-any.whl |
|---|---|
| Size | 275.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
528f14add1b13f86f4780cf2cf067aea019885b2628720e352447cd0571234f7
|
|
BLAKE2b-256 checksum How to use checksums |
3f3424061ef597ed3bd11048580a41b58fd05fdd645e074e2575784a548b097c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 15, 2026.
Transparency log
