⚡ Provider-agnostic CI/CD · GitHub · GitLab · Bitbucket · Gitworld

CI/CD that sets itself up.

Connect any repo and CIRunnerMax detects your stack, suggests the right steps, and an AI copilot wires the whole pipeline for you — no YAML required. Every job runs in a real sandbox.

Start free See how it works

Kernel-isolated builds · hosted & self-hosted runners · works from mainland China.

Pipeline GUI builder Ask AI

# .cirunnermax.yml — generated for you, editable by hand
on: [push, pull_request]
jobs:
  test:
    runs-on: [linux]
    container: { image: node:20 }
    steps:
      - uses: typecheck.tsc
      - uses: unit.vitest
      - uses: e2e.cypress
      - uses: quality.sonarqube

Why CIRunnerMax

Everything CI should be — without the setup tax.

Most runners hand you a blank YAML file. CIRunnerMax hands you a working pipeline.

✦

Guided GUI setup

Configure your entire pipeline in the browser. Connect a repo, we scan it, and prefill the steps that fit — you never have to touch YAML.

✿

AI copilot, confirm-first

Describe what you want in plain language. The assistant proposes real steps and shows a preview — nothing changes until you approve.

▤

Batteries-included catalog

Type-checking, unit tests, Cypress/Playwright e2e, SonarQube, coverage gates, security scans, container builds, deploys — parameterized and ready.

🛡

Real sandbox isolation

Every job runs under a gVisor kernel boundary — no host access, no shared docker socket. Untrusted code stays contained.

⇄

Bring any git host

GitHub, GitLab, Bitbucket, and self-hosted Gitworld through one interface. The same pipeline runs everywhere.

☁

Hosted or self-hosted

Use our runner pool, or drop a runner inside your own network so code and secrets never leave your perimeter. Works from mainland China.

Guided setup

Green on the first try.

Point CIRunnerMax at a repository. It reads your package.json, go.mod, Dockerfile, Sonar config and more — then suggests a ranked, prefilled set of steps from the catalog.

✓ Auto-detects your stack and test tooling
✓ One-click add from a curated step catalog
✓ Secrets referenced by name — the AI never sees their values
✓ Export to .cirunnermax.yml anytime for GitOps

tsc · type check Vitest · unit Jest · unit pytest · unit go test ESLint · lint golangci-lint Cypress · e2e Playwright · e2e SonarQube · quality coverage · gate Trivy · security kaniko · build deploy · with approvals

# inside a job — the kernel is not the host's
$ uname -r
4.19.0-gvisor
$ ls /var/run/docker.sock
No such file or directory
$ whoami
runner  # curated env — no runner creds leak

Security by default

Untrusted code, contained.

CIRunnerMax was multi-tenant from day one. Jobs get a real kernel boundary, per-tenant encrypted secrets, and least-privilege, short-lived checkout tokens.

✓ gVisor sandbox — works even on KVM-less hosts
✓ No host docker socket, ever; daemonless image builds
✓ Per-tenant envelope-encrypted secrets, masked in logs
✓ Per-runner revocable tokens; tenant-scoped dispatch

How it works

Three steps to a pipeline.

Connect a repo

Install the app on your GitHub org (or GitLab/Bitbucket/Gitworld). Pick the repos to watch.

Review the suggestions

We detect your stack and propose steps. Tweak in the GUI or ask the AI copilot to adjust.

Push & go green

Every push runs in a sandbox with live logs, and a status check lands right back on your PR.

Pricing

Start free. Scale when you do.

Free

$0 / month

For personal projects and trying it out.

✓ Hosted runner pool
✓ Unlimited public repos
✓ Guided setup + AI copilot
✓ Community support

Get started

Team

$29 / month

For teams shipping every day.

✓ Private repos & org connections
✓ Concurrent builds & caching
✓ SonarQube + coverage gates
✓ Deploy pipelines with approvals

Start free trial

Enterprise

Custom

Self-hosted, on-prem, or air-gapped.

✓ Self-hosted runners in your network
✓ China / on-prem deployment
✓ SSO, audit, dedicated pools
✓ Priority support & SLAs

Talk to us

Pricing shown is illustrative — billing is not enabled yet during preview.