slipway.yaml, and slipway builds the images, gives each service its own URL, and tears everything down on its own when the PR closes or the TTL expires. It’s the same environment your team reviews in, and one your AI agents can drive over MCP.
Quickstart
Install the GitHub App, add a
slipway.yaml, and get a live preview URL in under five minutes.Core concepts
Deployments, services, ephemeral previews, supersession. The shape of how slipway thinks.
Slipway spec
Every shipped field of the manifest, with worked examples and a full field index.
AI agents
Hand Claude, Cursor, or your own agent a real place to run. Slipway ships a first-party MCP server.
Deployments
Triggers, manual deploys, and what happens at each step of the lifecycle.
Environments
Multi-repo stacks, PR previews, and the lifecycle from create to teardown.

What it’s for
- PR previews. Every pull request gets its own live environment at a stable URL (
<env-name>-<service>-<id>.<your-apps-domain>). Teardown is automatic on PR close. - Default-branch previews. Every push to
mainrebuilds and supersedes the previous environment. - Ephemeral one-offs. Spin up any ref as its own isolated instance with
sw dev up, on its own URL, reaped automatically once you’re done. - Built for AI agents. slipway ships a first-party MCP server. Point Claude, Cursor, or your own agent at it and it drives the whole lifecycle: bring a branch up to a live URL, read the logs, exec into a container to verify a fix, then tear it down. The verification loop agents otherwise lack. See AI agents.