OctoPrint source repository: Python 3.11 to 3.15, 2.0.0 release candidates, and no install command
OctoPrint is the snappy web interface for your 3D printer!
At a glance
- What is it?
- This repository is OctoPrint application source rather than an install guide. It caps Python at 3.15, bundles three plugins from the same date floor, and leaves every setup step to docs.octoprint.org or the OctoPi Raspberry Pi distribution.
- Who is it for?
- The judgment: OctoPrint fits a user who wants a browser interface to a consumer printer and is willing to send setup questions to docs.octoprint.org, the forum, or the FAQ, because this repository deliberately keeps none of that. It does not fit someone who wants to pick a version by tag tonight: the three most recent tags are all 2.0.0 release candidates, and the 3.15 ceiling rules out newer interpreters outright.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 3 days ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- OctoPrint/OctoPrint9,198 ★ · +92
| Repository | 2026-09-22 | 2026-11-15 |
|---|---|---|
| OctoPrint/OctoPrint | 9.1k | 9.2k |
92 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The repository README is a pointer to docs.octoprint.org, not an install guide
The first thing the README does is tell you what you are looking at: you are currently looking at the source code repository of OctoPrint, and if you already installed it and only want to find out how to use it, the documentation might be more interesting. There is no install command in it anywhere.
What the README gives instead is a list of destinations. octoprint.org is the website. community.octoprint.org is the community forum, and it also serves as a central knowledge base. discord.octoprint.org is where the Discord invite lives. faq.octoprint.org holds the FAQ, docs.octoprint.org holds the documentation, and plugins.octoprint.org is the official plugin repository.
The consequence for a reader is direct: cloning this repository gets you source code, not a running instance, and every practical step of setup lives one hop away. Raspberry Pi users are pointed at a separate project, OctoPi, described as the Raspberry Pi targeted distribution of OctoPrint. A reader who opens this README expecting install instructions finds a list of links to the project's own websites instead.
requires-python reads >=3.10, <3.15, and only CPython is listed
The package metadata in pyproject.toml carries the hard constraint on where OctoPrint can run:
requires-python = ">=3.11, <3.16"The classifier list spells the same range out one minor at a time, from Python 3.11 through 3.15, and adds Programming Language :: Python :: 3 :: Only plus Programming Language :: Python :: Implementation :: CPython. So PyPy is not on the declared support list, and a 3.16 interpreter sits outside the range.
The build side is equally explicit: the build system requires setuptools>=80 and wheel through the setuptools.build_meta backend. The web layer is declared as Framework :: Flask and Environment :: Web Environment, and the operating system line reads OS Independent.
What this means in practice is that an install on a newer Python is a metadata failure rather than a subtle runtime bug, and an alternative interpreter is undocumented territory. The core dependencies include argon2-cffi at 25.1.0 or newer, and pin Babel to >=2.18,<2.19 with an inline comment flagging a breaking change.
Two 2.0.0 release candidates sit beside stable 1.11.8, so the newest tag is not stable
The release list is the part that decides what you pin. The most recent tag is 2.0.0rc7, published 2026-10-20. Before it came 2.0.0rc6 on 2026-10-07 and 2.0.0rc5 on 2026-08-24.
Three consequences follow. First, sorting by date hands you a release candidate, not a stable release, so a script that grabs the newest tag gets 2.0.0rc7. Second, the three most recent tags are all release candidates, and choosing an rc means the interface and plugin expectations may still move between rc6 and rc7.
Third, the default branch is dev rather than master or main, and the README links its contribution guide from blob/dev/CONTRIBUTING.md. A fresh clone is therefore development state, not a released state. The dev branch last moved on 2026-10-30, ten days after the newest release candidate was tagged. The README does not say which release matches a given plugin.
FileCheck, FirmwareCheck and PiSupport are bundled, and they share one date floor
The dependency list opens with a comment marking bundled plugins, and three entries follow it:
# bundled plugins
"OctoPrint-FileCheck>=2025.7.23",
"OctoPrint-FirmwareCheck>=2025.7.23",
"OctoPrint-PiSupport>=2025.7.23",These are not optional extras. All three are version-constrained to the same calendar date, 2025.7.23, so installing OctoPrint means satisfying three plugin floors at once, and nothing in the list will accept an older copy left over from a previous setup.
The naming also tells you where the platform support lives. PiSupport is a required dependency rather than an optional extra, so it is installed alongside OctoPrint on every platform. If you maintain a printer farm on Pi hardware, that floor is the version to check first when a plugin behaves differently than expected.
The rest of the dependencies are grouped separately under a core deps comment, so the plugin trio is visually and logically distinct from the libraries OctoPrint itself needs.
setup.py pulls the version from _version.py and copies AUTHORS.md into the templates tree
The build is not a plain setuptools build. setup.py defines get_version_and_cmdclass, which loads a version module from the package path with spec_from_file_location, executes it, and pulls two things out of it: data["version"] and module.get_cmdclass(pkg_path).
It also defines copy_files_build_py_factory, a wrapper around setuptools' build_py command that copies files into the build directory before calling the base class's run. The mapping it registers targets octoprint/templates/_data and lists files such as AUTHORS.md, so project credits end up inside the installed package templates rather than only in the repository.
Two consequences for anyone packaging or vendoring this. The metadata is declared as dynamic for both version and license in pyproject.toml, so a source build has to execute code to learn what version it is, which rules out a purely static parse. And a packager who reads only pyproject.toml will miss the build_py override and the file copies entirely, so the resulting wheel can differ from what the pyproject block implies.
requirements.txt is a stub whose one job is making an editable install resolve
requirements.txt is not a dependency list, and the file says so in its own first comment block. Its stated purpose is to make sure that something like this works as expected:
pip install -e .[develop]It then points elsewhere for the actual requirements, naming two variables in setup.py: INSTALL_REQUIRES and EXTRA_REQUIRES. The body of the file is short. One comment explains that the regular PyPI URL is being forced over https to be safe, and the next line is the option itself:
-i https://pypi.python.org/simple
.The trailing dot is the project itself. So the practical effect of running pip install against this file is to install the project from the working tree, with its dependencies coming from the project's own metadata rather than from this file. Anyone scanning a repository for a dependency list and finding requirements.txt will find a redirect; the dependencies themselves are declared in the dependencies list of pyproject.toml.
AGPL-3.0 comes with a per-file exception note that lives inside the files
OctoPrint is released under the GNU Affero General Public License V3, and the README attaches a footnote to that statement that changes how you should read it.
The footnote says that where another license applies to a specific file or folder, that is noted inside the file itself or in a folder README. Vendored and linked third party dependencies are handled separately, in THIRDPARTYLICENSES.md, which exists at the top level of the repository alongside LICENSE.txt.
The consequence is that the top-level license file is not a complete answer to a license question. Anyone building a distribution has to walk the tree to find which folders carry a different notice, and anyone redistributing dependencies has a second file to consult for the ones that came in from elsewhere. The README does not summarize which directories hold exceptions, so that inspection cannot be skipped on the assumption that everything inherits AGPL-3.0.
For anyone running a modified deployment that stays reachable over a network, the AGPL is the part of this that matters most, and the per-file note is where the actual obligations get decided.
BrowserStack, PyVmMonitor and Sentry are named as part of the toolchain
The Special Thanks section credits three services by name and by role. Cross-browser testing services are kindly provided by BrowserStack. Profiling is done with the help of PyVmMonitor. Error tracking is powered and sponsored by Sentry.
That is a short list. The consequence for a reader is that the project's development and operation depend on hosted third parties, and the README does not say how any of them are switched off or what they receive. An operator who cannot send logs and error data outside the building has no answer here and has to settle it in the configuration documentation. It is also worth separating the three roles: browser testing and profiling are development aids, while error tracking is the one most likely to involve data leaving a deployment.
None of this tells you how the defaults behave. It tells you which vendors to look for in a configuration before deploying.
Editorial conclusion
The judgment: OctoPrint fits a user who wants a browser interface to a consumer printer and is willing to send setup questions to docs.octoprint.org, the forum, or the FAQ, because this repository deliberately keeps none of that. It does not fit someone who wants to pick a version by tag tonight: the three most recent tags are all 2.0.0 release candidates, and the 3.15 ceiling rules out newer interpreters outright. Before deploying, check the interpreter version, read the license note about per-file exceptions, and confirm which plugin set matches the release you install.
Frequently asked questions
What is an OctoPrint?
It is a snappy web interface for controlling consumer 3D printers, released under the GNU Affero General Public License V3. Its documentation lives at docs.octoprint.org and the official plugin repository is plugins.octoprint.org.
Do you need a Raspberry Pi for OctoPrint?
The package metadata does not require one: it lists Operating System :: OS Independent and ships OctoPrint-PiSupport as a bundled plugin. A Raspberry Pi targeted distribution called OctoPi exists, but it is a separate project from this repository.
What do I need to run OctoPrint?
Python from 3.11 up to but not including 3.16, CPython only, with Flask as the declared web framework. The README carries no setup procedure of its own and sends readers to docs.octoprint.org, the forum at community.octoprint.org, or faq.octoprint.org.
How do I install OctoPrint from this repository?
The repository shows no install command in its README. The only install line anywhere is the editable install quoted inside requirements.txt, pip install -e .[develop], and that file exists to make that command resolve; its comment points to INSTALL_REQUIRES and EXTRA_REQUIRES in setup.py, while pyproject.toml lists the dependencies.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/octoprint-octoprint)Star history chart for your README
[](https://hysenlabs.com/projects/octoprint-octoprint)Was this useful?