Choose the TurboCI build that fits your operator environment.

TurboCI ships as a standalone binary and a lightweight JavaScript build. Both expose the same CLI and deployment surface.

~100 MB

self-contained binary for machines without Node.js or Bun

~1 MB

JavaScript build for Node.js-first environments

install.sh

bash

# Binary
curl -L https://github.com/Moduletrace/turboci/releases/latest/download/turboci -o turboci
chmod +x ./turboci

# JavaScript
curl -L https://github.com/Moduletrace/turboci/releases/latest/download/turboci.js -o turboci.js
node ./turboci.js

Choose a build

Both distributions expose the same deployment workflow.

Pick the binary when you want zero runtime dependencies. Pick the JavaScript build when Node.js is already part of the environment.

Standalone binary

~100 MB, no runtime required

A self-contained executable for operators who want the shortest path from download to deployment.

download

bash

curl -L https://github.com/Moduletrace/turboci/releases/latest/download/turboci -o turboci
chmod +x ./turboci
./turboci

JavaScript build

~1 MB, requires Node.js

Smaller download size for environments where Node.js is already present and preferred.

download

bash

curl -L https://github.com/Moduletrace/turboci/releases/latest/download/turboci.js -o turboci.js
node ./turboci.js

Path setup

Make `turboci` available globally

Move the binary into a directory on your PATH so the command is available from any working directory.

If you rely on the JavaScript build instead, placeturboci.js somewhere stable and wrap it in a shell alias or script.

path

bash

sudo mv ./turboci /usr/local/bin/turboci
turboci --version

Quick start

Once installed, you can deploy immediately.

Boot the configuration interactively, then push the first rollout.

first-deploy

bash

turboci init
turboci up

Next step

Move from install to deployment shape

Now that the CLI is available, define the first deployment in YAML and map the services you want TurboCI to run.

Continue to configuration