# SuperCI documentation

- [Getting started](https://superci.dev/docs/getting-started.md): 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](https://superci.dev/docs/how-it-works.md): 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](https://superci.dev/docs/commands.md): 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](https://superci.dev/docs/workspaces.md): 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.
- [Labels and machines](https://superci.dev/docs/labels.md): 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](https://superci.dev/docs/providers.md): 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](https://superci.dev/docs/aws-accounts.md): 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](https://superci.dev/docs/order-and-limits.md): 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](https://superci.dev/docs/several-accounts.md): Run one CI's jobs in several AWS accounts, Cloudflare accounts or Modal workspaces, each with its own limits and spend
- [Spot machines](https://superci.dev/docs/spot-machines.md): 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](https://superci.dev/docs/runs-from-a-computer.md): 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](https://superci.dev/docs/cache.md): 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](https://superci.dev/docs/faster-tests.md): 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.
- [GPU runners](https://superci.dev/docs/gpu.md): 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](https://superci.dev/docs/windows.md): 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](https://superci.dev/docs/macos.md): 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](https://superci.dev/docs/arm64.md): 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](https://superci.dev/docs/larger-runners.md): 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.
- [GitHub](https://superci.dev/docs/github.md): 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](https://superci.dev/docs/gitlab.md): Connect GitLab.com or a self-managed GitLab with an access token, turn projects on, and run jobs by tag.
- [GitHub Enterprise](https://superci.dev/docs/github-enterprise.md): Use SuperCI with GitHub Enterprise Server or GitHub Enterprise Cloud with data residency, and what your server has to allow.
- [Public repositories](https://superci.dev/docs/public-repositories.md): 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](https://superci.dev/docs/private-networks.md): Start AWS machines in your own subnets and security groups, so jobs reach what that network reaches.
- [Troubleshooting](https://superci.dev/docs/troubleshooting.md): What to check when a job waits, fails at once or is refused, and where SuperCI says why.
