To enable Runway to conform to our users’ varying use cases, we have made it available via three different install methods - cURL, npm, and pip.


Arguably the easiest way to install Runway is by using curl. Use one of the endpoints below to download a single-binary executable version of Runway based on your operating system.

Operating System





$ curl -L -o runway


To install a specific version of Runway, you can replace latest with a version number.


To use the single-binary, run it directly as shown below. Please note that after download, you may need to adjust the permissions before it can be executed. (eg. macOS/Ubuntu:chmod +x runway)

$ ./runway deploy

Suggested use: CloudFormation or Terraform projects


Runway is published on npm as @onica/runway. It currently contains binaries to support macOS, Ubuntu, and Windows.

While Runway can be installed globally like any other npm package, we strongly recommend using it per-project as a dev dependency. See Why Version Lock Per-Project for more info regarding this suggestion.

$ npm i -D @onica/runway


$ npx runway deploy

Suggested use: Serverless or AWS CDK projects


Runway runs on Python 2.7 and Python 3.5+.

Runway is hosted on PyPI as the package named runway. It can be installed like any other Python package, but we instead strongly recommend using it per-project with pipenv. See Why Version Lock Per-Project for more info regarding this suggestion.

Suggested use: Python projects

Version Locking with Pipenv

In your project’s directory, execute pipenv install runway. This will:

  1. Update (creating if missing) a Pipfile file with your project’s Runway dependency

  2. Create a Python virtual environment (hidden in your user profile folder) dedicated to your project, with Runway installed in it

  3. Update (creating if missing) a Pipfile.lock file containing the exact versions/crypto-hashes of Runway (and dependencies) installed in your python virtual environment

Now Runway can be used in the project via pipenv run runway ... (e.g. pipenv run runway takeoff).

To ensure future users of the project use the same version of Runway, direct them (e.g. via a Makefile) to invoke it via pipenv sync; pipenv run Runway ... – this will ensure the version in their virtual environment is kept in sync with the project’s lock file.


Pipenv Not Found

If pipenv isn’t available after installation (via pip install --user pipenv, see the Python Setup guide.

Why Version Lock Per-Project

Locking the version of Runway per-project will allow you to:

  • Specify the version(s) of Runway compatible with your deployments config

  • Ensure Runway executions are performed with the same version (regardless of where/when they occur – avoids the dreaded “works on my machine”)