Introduction

Slipway is a CI/CD and deployment platform. It does two jobs that are usually split across tools:

1. Pipelines build, test and package your code on runners you control.
2. Deployments take the result, an immutable release, and move it through environments with strategies, approvals, gates and verification.

It does not host source code. It connects to GitHub, GitLab, Bitbucket, Azure Repos and Gitea.

Pre-release

Slipway is pre-release software. Pages that describe features still on the roadmap are marked Planned. The pipeline reference is generated from the same JSON Schema that slipway validate uses, so it is always accurate for the build you are running.

Choose a path

I want to…	Start here
Try Slipway without installing anything	Quickstart: Slipway Cloud
Run Slipway on my own machine or server	Quickstart: self-host in 5 minutes
Write a first pipeline and deploy it	Your first pipeline and deployment
Understand the vocabulary	Concepts
Move from another tool	Migration guides

The shape of the product

 SCM ──webhook──▶  server  ──queue──▶  runner  (your network, dials out)
                      │                   │
                      ▼                   ▼
                  Postgres            build / test / package
                  NATS, S3, Valkey        │
                      ▲                   ▼
                      └────────  Release ──▶ Environments (dev → staging → prod)

• One binary, slipway, with subcommands server, scheduler, worker and runner, plus all for development.
• Runners dial out to the server, so they work behind NAT and firewalls with no inbound ports.
• Postgres holds state (with row-level security per organisation), NATS JetStream carries queues and events, S3-compatible storage holds logs and artifacts, Valkey holds sessions and rate limits.

What is free

Every tier, including Free, has unlimited users, unlimited projects and pipelines, unlimited self-hosted runner minutes, OIDC single sign-on, secrets, an audit log and signed provenance. See pricing.