Introduction

Peak runs each GitHub Actions job in a fresh microVM. Change one line to move a job.

.github/workflows/ci.yml

runs-on: ubuntu-latest
runs-on: peak-ubuntu-24.04-4

Products

Product	What it does	Status
Runners	Ubuntu 24.04 runners for x64 and ARM64, 4 to 16 vCPUs	Available
Caching	Keeps dependencies, Docker layers, and Git objects between jobs	Available
Shadow mode	Runs a copy of your CI on Peak before you move	Available
Runs and Insights	Run timelines, job search, and job minutes	Available
CLI	Run and step timings in your terminal	Available
API	Scoped tokens for scripts and agents	Available
peak run	Runs a workflow on your uncommitted code	Available
Connect GitLab	Runs GitLab CI jobs on Peak runners	Beta
SSH into jobs	Connects you to a running or failed job	Beta
Test analytics	Finds failing, flaky, and slow tests	Beta
Notifications	Alerts Slack or a webhook about failures, slow jobs, and queues	Beta
MCP server	Gives coding agents read access to your CI	Beta
Peakviews	Runs a live preview of your whole stack for each pull request	Beta
Self-healing CI	Fixes failing pull request CI with a verified commit, on Peak’s own repositories for now	Beta
Agent sandboxes	Isolated microVMs for coding agents	Coming soon

Ask your Peak contact to turn on a Beta product for your workspace. Or email hi@peak.inc.

Move your first job to Peak.

Compare Peak with your current CI first.

Choose a label, size, and architecture.

Connect organizations and choose repositories.