SuperCI documentation
Run GitHub Actions and GitLab CI jobs on machines in your own cloud. Start with the first guide; the rest are for when you need them.
Try it
Start the dashboard:
npx @superci/cli dashboardSign in with your cloud, put a control plane there, and connect a repository. Then change one line in a workflow:
jobs:
test:
runs-on: superciGetting started goes through each step.
Start
Getting started
Start the dashboard, put a control plane in your cloud, connect a repository and run your first job on your own machines.
How it works
The three parts of SuperCI (a dashboard, a control plane in your cloud, a machine per job) and what happens from a push to a finished job.
Commands and coding agents
Run everything the dashboard does from a terminal or a coding agent: sign in once, then status, runners, repositories and updates as commands with JSON output.
Workspaces
Look after several CIs from one computer: each workspace has its own sign-ins, control plane and runners, a switcher in the dashboard, and --workspace in commands.
Running jobs
Labels and machines
How the runs-on label picks a job's machine, as key=value pairs after its name: size, architecture, GPUs, Windows, the disk, a provider, or no spot machines.
Runner providers
What AWS, Cloudflare and Modal each run, what SuperCI creates in each account, and what each one needs from you.
What your AWS account allows
How SuperCI looks at an AWS account and works with what it allows: its regions, spot machines, CPUs at once and the runner image, and a project from AWS's new sign-up.
Order and limits
How jobs are placed across your providers, what happens when one cannot start a job, and how to cap jobs at once and spending by month and by day, in SuperCI and in AWS itself.
Several accounts
Run one CI's jobs in several AWS accounts, Cloudflare accounts or Modal workspaces, each with its own limits and spend
Spot machines
How SuperCI uses AWS spot machines, what happens when AWS takes one back mid-job, and how to keep a job off spot.
Runs from a computer
Run a workflow's jobs on your own machines from your computer or a coding agent, with the working tree as it is and nothing pushed.
Cache
GitHub's cache, and Turbo's, Nx's, Bazel's and GitLab's, kept in a bucket in your own AWS account: who may read what, what it keeps, and how to set it.
Faster tests
Make a test job finish sooner on SuperCI: a bigger machine with every CPU in use, a matrix for tests that cannot share one, and less setup, all measured.
Machines
GPU runners
Run GitHub Actions jobs on an NVIDIA GPU in your own AWS or Modal account: the labels, what each GPU costs, and the quota AWS starts you at.
Windows runners
Run GitHub Actions jobs on Windows Server 2025 machines in your own AWS account: the label, the sizes, prices beside GitHub's, and what differs from Linux.
macOS runners
Coming soon: macOS jobs on Apple Macs in your own AWS account, each Mac rented for 24 hours, reused with a clean disk for every job.
Arm runners
Run GitHub Actions and GitLab CI jobs on Arm (AWS Graviton) machines in your own account: the label, the prices, and building for two architectures.
Larger runners
Move jobs from GitHub's larger runners to machines of the same size in your own cloud: which label replaces which runner, what each costs, and what changes.
Code hosts
GitHub
Connect an organization or your own account on GitHub: the GitHub App SuperCI creates for you, what it may do, choosing repositories, and what to check when a job never starts.
GitLab CI
Connect GitLab.com or a self-managed GitLab with an access token, turn projects on, and run jobs by tag.
GitHub Enterprise
Use SuperCI with GitHub Enterprise Server or GitHub Enterprise Cloud with data residency, and what your server has to allow.