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

jobs:
  test:
    runs-on: superci

Getting 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.

Running jobs

Labels and machines

How the runs-on label picks a job's machine: size, architecture, GPUs, Windows, a provider, or on-demand only.

Runner providers

What AWS, Cloudflare and Modal each run, what SuperCI creates in each account, and what each one needs from you.

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 monthly 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.

Code hosts

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.

Safety

Public repositories

Why jobs from public repositories are refused by default, how to allow one, and which runs are refused even then.

Your own network on AWS

Start AWS machines in your own subnets and security groups, so jobs reach what that network reaches.