Run your GitHub Actions jobs on Sengi. Each job gets a fresh machine; your workflows, secrets and logs stay in GitHub Actions.
Quickstart
You need permission to install a GitHub App on the account or organization that owns the repository.
1. Connect your repository
Sign in to Sengi, choose Set up GitHub connection and install the Sengi GitHub App. Choose Only select repositories to limit its access. No card is needed to start.
2. Change one line
Change runs-on in a job and keep everything else:
jobs:
test:
runs-on: sengi-basic-2-ubuntu-2404
steps:
- uses: actions/checkout@v4
- run: npm ci
- run: npm testPrefer not to edit workflows by hand? Paste the Sengi prompt into your coding agent. It moves every eligible job and opens a pull request for you to review.
3. Push and check the result
Push the change and open Actions in GitHub. The job runs on Sengi and its logs appear in GitHub as usual. Your project's Job history page in Sengi shows each job's size, start delay and run time.
Sizes and prices
Put one label in runs-on. Every size is Ubuntu 24.04 x64.
| Size | Label | vCPU | RAM | Per minute |
|---|---|---|---|---|
| Basic 2 | sengi-basic-2-ubuntu-2404 | 2 | 8 GB | $0.001 |
| Basic 4 | sengi-basic-4-ubuntu-2404 | 4 | 16 GB | $0.002 |
| Basic 8 | sengi-basic-8-ubuntu-2404 | 8 | 32 GB | $0.004 |
| Premium 2 | sengi-premium-2-ubuntu-2404 | 2 | 8 GB | $0.003 |
| Premium 4 | sengi-premium-4-ubuntu-2404 | 4 | 16 GB | $0.006 |
| Premium 8 | sengi-premium-8-ubuntu-2404 | 8 | 32 GB | $0.012 |
Every account gets 3,000 free Basic minutes a month. See runner sizes to pick a size and billing for how minutes are counted.
What is preinstalled
| Area | Included |
|---|---|
| Runner | The GitHub Actions runner, on Ubuntu 24.04 x64 |
| Containers | Docker, Docker Compose and Buildx |
| Languages | The tool cache that actions/setup-node and actions/setup-python resolve from |
| Caching | actions/cache, setup-action caches and Docker type=gha layers, served by Sengi |
Pin language versions with setup actions, and install anything else your job needs in a step.
Next steps
- Runner sizes: match your current runner.
- Docker builds and services: images, Compose and service containers.
- Caching: what is cached and for how long.
- Troubleshooting: a job that stays queued or fails to start.
