Getting started

Set up the first TurboCI deployment without leaving the docs.

Start with the quick install path, add one provider key, model the deployment in YAML, and let TurboCI provision the fleet and perform the rollout.

Download binary

10 min

Enough time to go from blank project to the first rollout-safe deployment.

1 YAML

The same configuration can describe services in multiple clouds.

quick-start.sh

bash

curl -L https://github.com/Moduletrace/turboci/releases/latest/download/turboci -o turboci
chmod +x turboci
export TURBOCI_HETZNER_API_KEY=your-hetzner-api-key
turboci init
turboci up

Quick start

Download TurboCI

Use the binary for the fastest path, or grab the JavaScript build if you prefer Node.js.

Export one API key

env

bash

export TURBOCI_HETZNER_API_KEY=your-key

Create the deployment file

bootstrap

bash

turboci init

Push the rollout

deploy

bash

turboci up

Installation

Pull the binary or JS build onto the machine you deploy from.

Configuration

Model providers, services, runtime hooks, and health checks in YAML.

Update Strategy

See how clusters are staged, checked, and promoted without downtime.

Admin Panel

Browser-based service management and terminals, secured behind an SSH tunnel on the relay server.

Auto-Healing

How the relay server monitors every service and recovers failing servers automatically.

Examples

Browse deployment shapes for common application and service layouts.

Why start here?

TurboCI replaces multi-tool deployment drift with one operational surface. The docs follow that same idea: download, configure, deploy, then go deeper only where needed.

One YAML file for provider, service, and rollout shape
Cluster-based updates with health-check promotion
Private networking and relay setup handled automatically
Browser-based admin panel with service management and terminal access
Auto-healing daemon that recovers failing servers without intervention
Multi-cloud duplication without rewriting the stack