CircleCI vs GitLab.com hosted runners

CircleCI is a CI platform of its own, with jobs that run up to 1, 3 or 5 hours depending on the plan. It also has Chunk sidecars in preview, remote Linux microVMs for agent checks. GitLab.com hosted runners are the machines built into GitLab that run a GitLab project's pipelines. Each job gets a fresh VM, and GitLab stops every job at 3 hours.

The companies and products

CircleCI

CircleCI is a CI and CD platform that runs your pipeline jobs on machines it hosts, or on runners you host.

You describe jobs in a config file. Each job runs on a fresh Docker container or a machine VM (Linux, Arm, Windows, macOS on Apple M4 Pro, or GPU on Scale), and the machine ends with the job. Files move between jobs through caches, workspaces and artifacts. CircleCI also has Chunk: an agent that runs tasks from a prompt, and Chunk sidecars, remote Linux microVMs where agents run and check code. This page compares where the two products overlap: a machine where a job or an agent does its work.

GitLab.com hosted runners

GitLab.com hosted runners are the machines that run GitLab CI/CD jobs for projects on GitLab.com, paid for in compute minutes.

This is a CI service, not a sandbox API. Each job gets a new VM on Google Cloud (Linux and Windows) or on AWS Mac hardware (macOS), with passwordless sudo. GitLab deletes the VM right after the job. It is built to build, test and deploy the code in a GitLab project. GitLab's Duo Agent Platform can also run Claude Code and Codex agents as CI/CD jobs on these runners.

Which use cases each one fits

For each use case, Battleships prices every sandbox provider on the same workload and sorts them from the cheapest monthly bill up. “137th cheapest of 374” means 136 of the other 373 providers run that workload, with every feature it needs, for less. “With limits” means the provider runs it but misses something, so it is listed after every full match. Open a use case for its whole ranking and what each provider misses.

Use case and its workloadCircleCI: price rankGitLab.com hosted runners: price rankboat: price rank
Software factory
100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month
A coding agent that builds a whole app needs one machine for hours with its files in place. CircleCI stops a job after 3 hours on Performance and GitLab after 3 hours on any plan. On both you set up carry-over through caches and artifacts. boat keeps the disk between runs; turn auto-stop off (default 1 hour) for long work.
340th of 365, with limits
$8,692 a month
348th of 365, with limits
$14,454 a month
5th cheapest of 365
$634 a month
Always-on AI employees
50 machines 24/7 · 2 vCPU / 4 GB
An assistant that runs all month does not fit jobs that end within 3 to 5 hours. You can chain scheduled jobs and carry files in a cache, but each job starts on a clean machine. On boat, turn auto-stop off on a paid plan; there is then no session cap.
343rd of 361, with limits
$13,137 a month
350th of 361, with limits
$21,858 a month
6th cheapest of 361
$657 a month
Code interpreter bursts
100 at once · 1 vCPU / 2 GB · 200,000 sessions of 1 min a month
281st of 336, with limits
$572 a month
314th of 336, with limits
$1,896 a month
189th of 336, with limits
$2,000 a month
Sandboxes for your users
300 at once · 2 vCPU / 4 GB · 30,000 sessions of 23 min a month
Neither CI service documents a URL that your users can open on a job: CircleCI documents no inbound ports, and GitLab's firewall blocks inbound traffic to hosted runners. boat gives each sandbox up to 50 HTTPS URLs, token-gated by default.
309th of 349, with limits
$3,702 a month
326th of 349, with limits
$6,133 a month
3rd cheapest of 349
$209 a month
RL rollouts
1,000 at once · 2 vCPU / 4 GB · 1,000,000 sessions of 3 min a month
303rd of 349, with limits
$17,882 a month
312th of 349, with limits
$29,762 a month
39th of 349, with limits
$2,000 a month
Agent evals
250 at once · 4 vCPU / 8 GB · 15,000 sessions of 20 min a month
317th of 359, with limits
$2,877 a month
327th of 359, with limits
$4,758 a month
10th cheapest of 359
$200 a month
CI runners
40 at once · 8 vCPU / 16 GB · 6,000 sessions of 12 min a month
Both are built for CI: CircleCI as a standalone pipeline service and GitLab's runners as the native choice for GitLab projects. boat runs CI jobs on full VMs with Docker and /dev/kvm, but has no pipeline service, and starts above the plan's included number cost extra.
137th cheapest of 374
$4,302 a month
129th cheapest of 374
$2,089 a month
2nd cheapest of 374
$86 a month
24/7 dev boxes
1 machine 24/7 · 4 vCPU / 8 GB
A dev box has to stay up and keep what you installed. Both services start each job from an image and restore only the paths you cache. A stopped boat sandbox keeps its disk for at least 14 days, and a saved snapshot keeps it longer; the IP address changes at each resume.
212th of 371, with limits
$508 a month
361st of 371, with limits
$805 a month
19th cheapest of 371
$26 a month
Computer-use agents
50 at once · 4 vCPU / 8 GB · 20,000 sessions of 15 min a month
Neither has a built-in desktop stream or computer-use API. A CircleCI machine job or a GitLab Linux job can install Xvfb and a browser, within the job time limit; GitLab blocks inbound traffic, so nobody can watch it live. boat streams a 1920x1080, 60 fps Linux desktop with Chrome and computer tools.
64th cheapest of 367
$2,589 a month
344th of 367, with limits
$4,278 a month
7th cheapest of 367
$200 a month
Browser-use agents
50 at once · 2 vCPU / 4 GB · 30,000 sessions of 10 min a month
153rd of 356, with limits
$1,293 a month
213th of 356, with limits
$2,118 a month
7th cheapest of 356
$200 a month
Scraping & bots (startup scale)
50 at once · 1 vCPU / 2 GB · 100,000 sessions of 3 min a month
75th cheapest of 343
$860 a month
218th of 343, with limits
$2,854 a month
6th cheapest of 343
$90 a month
Mass scraping & bots (undetectable)
1,000 at once · 1 vCPU / 2 GB · 3,000,000 sessions of 2 min a month
273rd of 327, with limits
$17,532 a month
314th of 327, with limits
$58,429 a month
73rd of 327, with limits
$1,800 a month
Parallel red teaming
200 at once · 2 vCPU / 4 GB · 5,000 sessions of 30 min a month
135th of 351, with limits
$852 a month
145th of 351, with limits
$1,383 a month
3rd cheapest of 351
$200 a month
GPU eval jobs
10 at once · 8 vCPU / 32 GB · 500 sessions of 30 min a month
None of the three is priced here: CircleCI's GPU classes are on its custom-priced Scale plan, GitLab has a Linux runner with an NVIDIA T4 on Premium and Ultimate, and boat has no GPU on any size.
Not ranked: misses a requirementNot ranked: misses a requirementNot ranked: misses a requirement
macOS agents
5 at once · 4 vCPU / 8 GB · 1,000 sessions of 20 min a month
Both run macOS: CircleCI on Apple M4 Pro, even on the Free plan one job at a time, and GitLab on Apple silicon in beta for Premium and Ultimate. boat runs x86 Linux only.
33rd of 35, with limits
$2,262 a month
22nd of 35, with limits
$1,069 a month
Not ranked: misses a requirement

Key features

FeatureCircleCIGitLab.com hosted runnersboat
Kind of productStandalone CI and CD platform; jobs start from a config file. Chunk sidecars (preview) for agent checksCI runners built into GitLab; jobs run from a project's .gitlab-ci.ymlAgent sandboxes you create, stop, fork and reach by API, CLI or SDK
IsolationContainers on the Docker executor; a fresh VM per job on machine, Windows and macOS executorsA new VM per job on Google Compute Engine, deleted right after; Linux jobs run in a privileged Docker containerFull VM with its own kernel, root and systemd, on a physical host dedicated to boat; vCPUs are shared
How long a job or machine runs1 hour per job on Free, 3 on Performance, 5 on Scale3 hours per job on every plan, whatever the project settingAuto-stop defaults to 1 hour; set up to 30 days, or turn it off on a paid plan for no session cap
Files after a runCI jobs: the machine ends and you carry paths with caches, workspaces and artifacts. Chunk sidecars (preview): snapshot a set-up sidecar and boot new ones from itGitLab deletes the VM after each job. You set up carry-over: CI cache (5 GB per archive, removed after 14 days unused) or artifactsDisk saved every minute and at each stop; memory, running programs and /tmp are not saved. A stopped disk is kept at least 14 days, longer as a saved snapshot
ForkNo fork of a running job or sidecar; a Chunk sidecar snapshot (source deleted) can boot many new sidecarsNo VM fork; every job starts from a fresh VM and a container image, plus any cache or artifacts you passLive fork of a running sandbox, from its last 1-minute snapshot
Docker and nested virtualizationDocker and sudo on machine executors; nested virtualization documented on the Android machine imageDocker-in-Docker in privileged mode with passwordless sudo; nested virtualization not documentedDocker, root, systemd and /dev/kvm on every sandbox
Getting into a running jobNo documented inbound ports or URLs. SSH rerun: 10 minutes to connect, then up to 1 hour (Free) or 2 hours (paid), for the user who started it. Or chunk sidecar ssh on a Chunk sidecar (preview)GitLab's firewall blocks inbound traffic to hosted runners; you can set up an outbound tunnel from the job. The web terminal works only on runners you host yourselfSSH and up to 50 HTTPS URLs, token-gated by default; public IPv6. Raw ports on sandboxes without their own IPv4 work over IPv6 only
Desktop and computer useNo built-in desktop stream or computer-use API; you can run Xvfb and x11vnc in a machine job and connect over an SSH rerunNo desktop provided; a Linux job can install Xvfb and a browser, but inbound traffic is blocked so nobody can watch it live; macOS runners do not support UI-interaction jobsBuilt-in 1920x1080, 60 fps Linux desktop and Chrome stream, with computer tools for agents
Coding agentsChunk runs CircleCI's own agent tasks from a prompt; other agents you install in a job yourselfDuo Agent Platform runs Claude Code and Codex (plus Amazon Q and Gemini with your own credentials) from issues and merge requests, on Premium and Ultimate; GitLab support turns the feature onSeven harnesses installed, including Claude Code and Codex, driven from outside with a prompt, steer and events API
Keeping API keys outContexts inject secrets as environment variables; OIDC tokens for cloud loginsGitLab-managed credentials through an AI Gateway for its Claude and Codex agents, at no extra charge; other secrets enter as CI/CD variablesOptional AI credentials proxy ($1 per day on, plus $1 per 1,000 requests): with it on, real keys of supported providers stay out of the sandbox; other secrets still enter it
Jobs or sandboxes at once30 jobs at once on Free, 80 on Performance (macOS 1 and 15); Scale is customNo published cap on runner VMs at once; new jobs stop when the group's minutes run out100 at once on $20, up to 2,000 on $2,000. Included starts per plan ($20: 12 a minute, 200 a day); extra starts cost $0.03 to $0.07; boat never queues a start
Operating systemsLinux on x86 and Arm, Windows, and macOS on Apple M4 Pro with XcodeLinux x64 and Arm64, Windows (beta), macOS on Apple silicon (beta, Premium and Ultimate)x86 Linux only; Windows programs through Wine, no Windows VM
GPUsNvidia P4, T4, A10G and V100 classes on the Scale planA Linux runner with an NVIDIA T4 on Premium and UltimateNone on any size
Self-hostingSelf-hosted runners, and CircleCI Server on your own Kubernetes (tested on EKS, GKE and local clusters), including air-gappedOpen-source GitLab Runner (MIT) on your own machines, with no compute minutes usedNo
RegionsUS only: AWS us-east-1 and us-east-2, GCP us-east1 and us-central1US: Google Cloud us-east1 and us-east5 for Linux x86-64, us-central1 for Arm64 and GPU, AWS us-east-1 for macOSGermany, Finland and France; no US or Asia region; you cannot pick a region
Every feature Battleships tracks (43)
FeatureCircleCIGitLab.com hosted runnersboat
Full VM (own kernel)YesYesYes
Docker insideYesYesYes
Nested virtualizationYesNo documented wayYes
RootNot publishedYesYes
SystemdNo documented wayNo documented wayYes
Desktop GUIWith your own setupNo documented wayYes
BrowserYesYesYes
Computer-use APINo documented wayNo documented wayYes
SSHYesNo documented wayYes
Persistent diskNo documented wayNo documented wayYes
Pause/resumeNo documented wayNo documented wayYes
Automatic snapshotsNo documented wayNo documented wayYes
Fork/cloneNo documented wayNo documented wayYes
Live fork (no pause)No documented wayNo documented wayYes
Memory forkNo documented wayNo documented wayNo documented way
Custom image (Docker or snapshot)YesYesYes
≥24 h sessionsNo documented wayNo documented wayYes
Idle auto-stopYesYesNo documented way
Wake on requestNo documented wayNo documented wayNo documented way
HTTPS preview URLsNo documented wayNo documented wayYes
Raw TCP inboundNo documented wayNo documented wayYes
Public IPv4No documented wayNo documented wayNo documented way
Egress allowlistNo documented wayNo documented wayNo documented way
Secret proxyNo documented wayYesYes
Secret proxy for any APINo documented wayNo documented wayYes
Preinstalled agentsNo documented wayYesYes
Agent harness APIYesYesYes
MCP serverYesNo documented wayNo documented way
GPUYesYesNo documented way
WindowsYesYesNo documented way
Arm64YesYesNo documented way
Self-hostingYesYesNo documented way
BYOCNo documented wayNo documented wayNo documented way
Open sourceNo documented wayYesNo documented way
Scoped API keysNot publishedNot publishedYes
Spend limitsNot publishedNot publishedYes
Usage per sandbox (API)YesNo documented wayYes
Audit logsYesYesNo documented way
SSOYesYesNo documented way
SOC 2YesYesNo documented way
HIPAANo documented wayNo documented wayNo documented way
EU data residencyNo documented wayNo documented wayNo documented way
Zero data retentionNot publishedNot publishedYes

Performance

CircleCINot measured
GitLab.com hosted runnersNot measured
boat28.06 runs/s

Neither CircleCI nor GitLab.com hosted runners are in the public benchmarks we use, so we cannot say which is faster. For reference, boat did 28.06 runs/s on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, second of 15 in StarSling's run of 3 October 2026 (run 37073680030). Every boat sandbox in this run ran on an AMD Ryzen 9 9950X host. boat also places some sandboxes on AMD Ryzen 7 9700X hosts, which this run did not measure.

V8 Web Tooling Benchmark at a 4 vCPU / 8 GB target, runs per second, higher is better. Source: StarSling's run of 3 October 2026 (run 37073680030), median of 5 sandboxes. Providers ran on different hardware in different regions. StarSling gives a shared rank when the run cannot separate two providers. Every boat sandbox in this run ran on an AMD Ryzen 9 9950X host. boat also places some sandboxes on AMD Ryzen 7 9700X hosts, which this run did not measure. CircleCI and GitLab.com hosted runners are not in the public benchmarks we use, so we cannot say which is faster.

Pricing in five scenarios

Each bill is priced from the providers' public price lists by the open Battleships engine, with the cheapest plan that runs the scenario. Start limits, per-start fees and plan minimums are in the price, boat's included.

ScenarioCircleCI, a monthGitLab.com hosted runners, a monthboat, a month
One coding agent, workdays
4 vCPU / 8 GB, 50 GB disk, 8 hours a day, 22 days a month, files kept between days
$96 · Performance · with limits$119 · Premium · with limits$20 · $20/mo
One agent that never stops
4 vCPU / 8 GB, 50 GB disk, running 24/7 all month
$508 · Performance · with limits$805 · Premium · with limits$26 · $20/mo
50 agents in parallel
50 machines of 4 vCPU / 8 GB at once, 8-hour sessions, 1,100 sessions a month, Docker inside
$5,714 · Performance · with limits$9,491 · Premium · with limits$317 · $20/mo × 3 seats
Sandboxes for your users
2 vCPU / 4 GB, 30,000 sessions of 10 minutes a month, up to 300 at once
$1,617 · Performance · with limits$2,658 · Premium · with limits$200 · $100/mo × 2 seats
1,000 short jobs at once
2 vCPU / 4 GB, 1,000 at once, 3 minutes each, 200,000 jobs a month
$3,562 · Performance · with limits$5,896 · Premium · with limits$8,800 · $2000/mo · with limits

CircleCI: CircleCI bills credits per minute for the machine class a job uses. Free costs $0 and includes 30,000 credits a month. Performance starts at $15 a month with 30,000 credits, and more cost $15 per 25,000. A 4 vCPU / 15 GB Linux machine uses 20 credits a minute, about $0.72 an hour. Scale is custom and billed annually. Chunk sidecars are free during preview.

GitLab.com hosted runners: GitLab counts compute minutes as run time times a cost factor: 1 for small Linux (2 vCPU / 8 GB), 2 for medium (4 vCPU / 16 GB), up to 12 for the biggest machines. Plans include monthly minutes per group (400 on Free, 10,000 on Premium at $29 per user a month, billed yearly). Extra minutes cost $10 per 1,000, bought ahead of time. When included minutes run out, new jobs stop until you buy more.

GitLab.com hosted runners: Plans cost $20, $100, $500 or $2,000 a month. The whole plan price comes back as VM time for that month, and it does not carry over. A 4 vCPU / 8 GB sandbox costs $0.036 an hour, billed per second while it runs. A stopped sandbox has no compute charge; saved snapshots above the plan's count and the AI credentials proxy still charge. Above the included starts (200 a day on $20), each extra start costs $0.03 to $0.07. A card is required, also for the 7-day free trial.

Limits in those scenarios

The limit on both is the job itself. CircleCI stops it after 3 hours on Performance and GitLab after 3 hours on every plan, and on both the machine ends with the job. So the workday agent, the agent that never stops and the 50-agent fleet do not fit as priced. CircleCI Performance runs at most 80 jobs at once, and GitLab publishes no cap on runner VMs at once, so 300 user sandboxes and 1,000 short jobs are not confirmed on either. GitLab's included minutes are a hard quota: when they run out, new jobs stop until you buy more. boat has its own limits. Auto-stop defaults to 1 hour, and a stopped disk is kept at least 14 days unless you save a snapshot. The 1,000-job burst does not fit as priced on boat either: the $2,000 plan includes 90 starts a minute and 2,400 a day, extra starts cost $0.03 to $0.07, and starts above 270 a minute fail with 429. boat never queues a start.

ScenarioCircleCIGitLab.com hosted runnersboat
One coding agent, workdays
  • Performance: sessions capped at 3 h
  • missing persistent disk
  • different kind of product: CI runner
  • Premium: sessions capped at 3 h
  • missing persistent disk
  • different kind of product: CI runner
  • no persistent disk: files lost when it stops or sleeps
None for this scenario
One agent that never stops
  • Performance: sessions capped at 3 h
  • missing persistent disk
  • different kind of product: CI runner
  • Premium: sessions capped at 3 h
  • missing persistent disk
  • different kind of product: CI runner
  • no persistent disk: files lost when it stops or sleeps
None for this scenario
50 agents in parallel
  • Performance: sessions capped at 3 h
  • missing persistent disk
  • different kind of product: CI runner
  • Premium: sessions capped at 3 h
  • missing persistent disk
  • different kind of product: CI runner
  • no persistent disk: files lost when it stops or sleeps
None for this scenario
Sandboxes for your users
  • Performance: max 80 concurrent
  • different kind of product: CI runner
  • different kind of product: CI runner
  • not confirmed: how many machines can run at once (you need 300; the typical published limit is 50)
  • egress price not published
None for this scenario
1,000 short jobs at once
  • Performance: max 80 concurrent
  • different kind of product: CI runner
  • different kind of product: CI runner
  • not confirmed: how many machines can run at once (you need 1,000; the typical published limit is 50)
  • egress price not published
  • 2,400 starts/day included, paid above that (needs ~6,667)
  • 600 starts/hour included, paid above that (needs ~1,000)
  • starts above 90/min are paid, and starts above 270/min fail with 429

Which one should you use?

Use CircleCI when

you want CI as its own service, need macOS on Apple M4 Pro, jobs longer than 3 hours on Scale, GPU classes such as the V100, the whole platform on your own Kubernetes, or free agent checks on Chunk sidecars while they are in preview.

  • macOS on Apple M4 Pro, even on Free. For iOS and Mac builds, CircleCI runs macOS on Apple M4 Pro with Xcode, one job at a time even on Free.
  • Longer jobs on Scale. If a job needs more than 3 hours, CircleCI's Scale plan allows 5, where GitLab's hosted runners stop every job at 3.
  • A CI service for any team. Teams that want CI as its own service get pipelines, caches, test splitting, orbs, and CircleCI Server on their own Kubernetes.

Use GitLab.com hosted runners when

your code lives on GitLab.com, you want pipelines with no extra service, runners you host free of minutes, or Claude Code and Codex working on your issues.

  • Native CI for GitLab projects. If your code lives on GitLab.com, hosted runners are on by default and run pipelines with no extra service to wire up.
  • Your own runners, free of minutes. The open-source GitLab Runner runs on your own machines, and those jobs use none of your compute minutes.
  • Agents on issues and merge requests. On Premium and Ultimate, Claude Code and Codex can work on GitLab issues and merge requests as CI jobs, once GitLab support turns the feature on.

Where boat fits

CircleCI and GitLab's runners are CI services, and for pipelines either one is a sound choice. If what you run is agents that work for hours on one machine, both make you fit that work into a job of a few hours on a machine that ends with it. boat gives each agent a full Linux VM that keeps its disk between runs, runs as long as you set and can be reached from outside.

A disk that stays

A CircleCI job stops at 3 hours on Performance and a GitLab job at 3 hours on any plan, and the machine ends with it. To skip reinstalls, you set up caches yourself; GitLab caps each cache archive at 5 GB. boat saves the disk every minute and at each stop, and keeps a stopped disk for at least 14 days. Memory and running programs restart, like after a reboot. With auto-stop off on a paid plan, there is no session cap.

Reach it from outside

GitLab's firewall blocks inbound traffic to hosted runners, and CircleCI documents no inbound ports, only an SSH rerun or chunk sidecar ssh. A preview server or webhook needs a tunnel that you set up inside the job. boat gives up to 50 token-gated HTTPS URLs, SSH and a 60 fps desktop.

Agents you drive from any program

Chunk runs CircleCI's own agent tasks, and GitLab's Duo agents start from issues and merge requests. GitLab keeps model keys out for its managed Claude and Codex agents; other secrets enter the job as variables on both. boat lets you drive seven installed harnesses through one API. With the optional AI credentials proxy on, real keys of supported providers stay outside the sandbox.

Use boat when your agents work on Linux for hours or days: one VM that keeps its disk between runs, Docker and /dev/kvm, a 60 fps desktop, HTTPS URLs, and coding agents you drive by API. Compare it one to one: boat vs CircleCI and boat vs GitLab.com hosted runners.

boat's own limits
  • Plans start at $20 a month. The plan price comes back as VM time for that month. Unused time does not carry over. Source
  • Starts (create, fork, resume): the $20 plan includes 12 a minute, 60 an hour and 200 a day. The $2,000 plan includes 90 a minute, 600 an hour and 2,400 a day. Extra starts cost $0.03 to $0.07. A start fails with 429 above 3 times the included starts per minute, or 6 times per hour or per day. Source
  • A stopped sandbox has no compute charge. boat keeps its disk for at least 14 days. A saved snapshot keeps it longer; extra saved snapshots and the AI credentials proxy are paid. Source
  • Auto-stop defaults to 1 hour. You can turn it off on a paid plan. The trial allows 2 hours at most. Source
  • boat saves the disk every minute and at each stop. Memory, running programs and /tmp are not saved: a resume is like a reboot. A machine failure loses writes after the last good snapshot. Source
  • Machines run in Germany, Finland and France only. Snapshot copies can be stored outside the EU. Source
  • Public IPv6 and outbound IPv4. No dedicated IPv4. The IP changes at each resume. Source
  • Hosts are AMD Ryzen 7 9700X and Ryzen 9 9950X. vCPUs are shared. No GPU. You cannot boot your own Docker image. Source

Questions people ask

Is CircleCI cheaper than GitLab.com hosted runners?

In our CI runners use case CircleCI comes to $4,302 a month and GitLab's hosted runners to $2,089, so GitLab is cheaper there. For one coding agent on workdays, CircleCI is lower, at $96 against $119, but neither fits, because jobs stop after 3 hours. Your own self-hosted GitLab runners use no compute minutes at all.

Which is faster, CircleCI or GitLab runners?

Neither is in the public benchmarks we use, so we cannot say which is faster. For reference, boat did 28.06 runs/s on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB in StarSling's run of 3 October 2026, on an AMD Ryzen 9 9950X host.

How long can a job run on CircleCI and on GitLab?

CircleCI allows 1 hour on Free, 3 hours on Performance and 5 hours on Scale. GitLab.com hosted runners stop every job at 3 hours, whatever the project sets. On boat, auto-stop defaults to 1 hour. You can set up to 30 days, or turn it off on a paid plan for no session cap.

Can I SSH into a CircleCI or GitLab job?

On CircleCI you can rerun a job with SSH: you have 10 minutes to connect, for the user who started the rerun. GitLab's firewall blocks inbound traffic to hosted runners, and the web terminal works only on runners you host yourself. You can SSH into a boat sandbox and open up to 50 HTTPS URLs, token-gated by default.

Can I run Claude Code on CircleCI or GitLab?

On CircleCI you install it as a step in a job and pass your key as a secret. On GitLab Premium and Ultimate, the Duo Agent Platform runs Claude Code and Codex as CI jobs from issues and merge requests, once GitLab support turns the feature on. On boat, Claude Code is installed and you prompt and steer it through an API.

Do CircleCI and GitLab run macOS?

Yes. CircleCI runs macOS on Apple M4 Pro with Xcode, even on the Free plan one job at a time. GitLab has macOS runners on Apple silicon in beta for Premium and Ultimate. boat runs x86 Linux only.

Try boat

Install the CLI, then run boat new.

7-day free trial

More comparisons