Drake
SoftwareC++ and Python toolbox for multibody dynamics, mathematical optimization and model-based robot control, with installation choices tied to platform and solver requirements. [5] [6] [7]
Installation & first result →Official websiteGetting started
- For
- Robotics researchers and developers working with mathematical models and optimization [1]
- Source rights
- Some licenses are unresolved. Review licenses
- Unknowns
- compute requirements not fully established. Review gaps
Source researched · Not tested by us
Sources checked · Research details
Licenses & related hardware
- License
- BSD-3-Clause · license not fully assessed for documentation · Details by part
Overview
Drake is a C++ toolbox with Python bindings for robot dynamics, mathematical optimization and model-based control. It exposes mathematical structure for planning and analysis as well as simulating motion. The reviewed v1.57.0 source is useful to developers who want to construct those models and algorithms; it is not a ready-made controller for a particular physical robot. [2] [5]
Is this for you?
- Workflows
- Construct dynamical-system models
- Build multibody models and simulation diagrams
- Formulate and solve mathematical programs
- Prototype control and planning algorithms through Python
- Known limitations
- Python bindings cover a substantial subset of C++ functionality, not every API
- Gurobi is unavailable in binary releases and requires a source build
- Anaconda is not regularly tested upstream
- C++ consumers of precompiled binaries must match the documented compiler configuration
What you need
- Operating system
- v1.57.0: Ubuntu 24.04/26.04 with architecture and Python version matched to installation method
- macOS 15/26 arm64 with supported Python version
- Amazon Linux 2023 x86-64/arm64 via pip
See the pinned installation matrix for exact combinations; no Windows support established here.
Installation & first result
Open the upstream getting-started guide [6] · Project documentation [4] [5]
- Choose the language, supported platform and required solver
- Install the corresponding stable distribution
- For Python, check import of pydrake.all
- Follow the documented pendulum model/diagram example before adding a custom robot
Editorial sequence; import and example have not been executed.
Hardware, models & data
Project notes
Python and C++ have different entry routes
For Python, the upstream starting route is a virtual environment and the drake wheel package. The import namespace is pydrake: the binding guide checks installation by importing pydrake.all and printing the module location. That distinction avoids confusing the package to install with the module to import. The Python bindings expose a substantial subset of C++ functionality, so check the Python API for the functions your experiment needs. [7] [8]
Choose the operating system, architecture and Python version together. The v1.57.0 installation matrix includes Ubuntu 24.04/26.04, Apple Silicon macOS 15/26 and Amazon Linux 2023, with different installation methods and Python versions in different rows. For example, Ubuntu 24.04 lists Python 3.12 for pip, binary and APT installations, while its Python 3.13–3.14 support is pip-only. CPython is the supported implementation, and Anaconda is not regularly tested. The pip guide calls for pip 20.3 or newer and Homebrew Python on macOS. [6] [7]
C++ users need a different check. Code linked against a precompiled Drake library must use the compiler configuration in the release's matrix, including C++23; on Ubuntu 24.04 the listed compiler is GCC 13. An arbitrary compiler that accepts the source is not enough to establish binary compatibility. The project also offers a source-build route. [6]
Check solver availability before committing to a package
Gurobi is not supported by Drake's binary releases. A project that needs it must follow the source-build instructions; selecting a wheel and adding an import later does not provide that integration. Solver installation and rights remain separate checks from Drake's own license. Image rendering, including simulated cameras, can also need additional setup. [3] [6] [7]
For an initial model, the Python binding guide shows how to create a diagram builder, add a multibody plant and scene graph, parse a pendulum URDF, finalize the plant and construct a simulator. This is a concrete path from a model file to a simulation object. Start with that documented example and inspect the relevant API before expanding to a custom robot or optimization problem. This suggested sequence has not been executed by this publication, and constructing a simulator alone does not validate a robot model or a control result. [8]
What we checked
Source research only; no installation, physical build or performance test performed. No affiliate links added.
Not yet established
- Requirements: host computer
- Version-specific hardware compatibility (ecosystem tags alone do not establish it)
Updates
Source files and licenses
Open toolbox source with documented setup; external solvers/assets and documentation-wide terms require separate assessment.
| Layer | Availability / license |
|---|---|
| software | available · BSD-3-Clause Root license notes portions with other permissive licenses. External dependencies and solvers retain their own terms; no blanket solver licensing claim. [3] |
| documentation | available · License not fully assessed Documentation available in the archive; separate documentation-wide license not established by this review. [4] [5] [6] |
Toolbox profile selects no trained policy or dataset.
Source rights and experiment limits
Drake's root license is BSD-3-Clause and explicitly notes portions under other permissive licenses. It does not replace the terms for separately selected dependencies, solvers or robot assets. This profile covers the toolbox and its documented setup choices; it includes no measured solve times, contact-accuracy benchmark, installation test or hardware-transfer result. [3]
References
Each source links to the exact revision we read. “Used for” shows where this page relies on it.
Project sources
- S001 RobotLocomotion/drake: README.md
Revision, date & where cited
github.com · revision
1e1466b· Accessed Oct 1, 2026 - S002 RobotLocomotion/drake: commit 1e1466b
- S003 RobotLocomotion/drake: LICENSE.TXT
Revision, date & where cited
github.com · revision
1e1466b· Accessed Oct 1, 2026
Used for: Check solver availability before committing to a package, Source files and licenses - S004 RobotLocomotion/drake: files
Revision, date & where cited
github.com · revision
1e1466b· archive file inventory · Accessed Oct 1, 2026
Used for: Installation & first result, Source files and licenses - S005 Drake v1.57.0: doc/index.md
Revision, date & where cited
github.com · revision
1e1466b· Accessed Oct 1, 2026
Used for: Overview, Is this for you?, What you need, Installation & first result and 2 more - S006 Drake v1.57.0: doc/_pages/installation.md
Revision, date & where cited
github.com · revision
1e1466b· Accessed Oct 1, 2026
Used for: Is this for you?, What you need, Installation & first result, Python and C++ have different entry routes and 2 more - S007 Drake v1.57.0: doc/_pages/pip.md
Revision, date & where cited
github.com · revision
1e1466b· Accessed Oct 1, 2026
Used for: Is this for you?, What you need, Installation & first result, Python and C++ have different entry routes and 1 more - S008 Drake v1.57.0: doc/_pages/python_bindings.md
Revision, date & where cited
github.com · revision
1e1466b· Accessed Oct 1, 2026
Used for: Is this for you?, What you need, Installation & first result, Hardware, models & data and 2 more
Videos
- S009 Periscope Tutorial Kuka Simulation via pydrake + meshcat (YouTube video)
Video from the project’s own channel (Russ Tedrake), linked from the project’s own documentation. Not reviewed by us for accuracy.Revision, date & where cited
YouTube video Russ Tedrake · youtube.com · Accessed Oct 4, 2026
Correction guidance · Discussion is not enabled · Profile format 0.6.0-draft.1
Change history
2026-10-04 — Added 1 YouTube reference(s) (S009): official channel or videos linked from the pinned upstream sources. Existing claims, source-check dates and evidence are unchanged.