Skip to main content
  • How do I switch from GitHub-hosted runners? Install the GitHub App, then change runs-on on a job to the label we send you. Jobs you don’t change keep running where they ran before.
  • How do I switch from Blacksmith? Change runs-on from your Blacksmith label to the label we send you, matching sizes by vCPU; new organizations start at 2 vCPU. Install the GitHub App first, then follow the migration guide.
  • What is a vCPU on Coreload? One CPU of the job’s VM, on an AMD Zen 5 desktop machine.
  • Which sizes are there? The sizes in the size table. New organizations start at 2 vCPU.
  • Where do my jobs run? On bare-metal machines, each job in a fresh VM that is deleted when the job ends.
  • Personal accounts? Not yet: organizations only, private repositories only.
  • What does it cost? A per-minute price for each size, on the pricing page.
  • Is my code safe? Each job runs in a fresh VM that never serves a second job or a second customer, and it is destroyed when the job ends; on a machine shared with other organizations, their jobs are separated from yours by that VM. What the GitHub App can do, and how your secrets are handled, is on the security page.
  • How long do you keep logs? Operational records (job and runner ids, timings, organization and repository names, error codes) are kept in our service logs for 30 days; billing usage records are kept longer.
  • Does actions/cache work? A job’s artifact and cache calls may go to a Coreload relay on the machine, or straight to GitHub. Through the relay, artifact calls go on to GitHub with the job’s own token, and cache calls go to a Coreload service on the machine without it and miss, since there is no Coreload cache yet. See caching.
  • Does Docker work? Not yet: container: and services: can’t start (limits).
  • What is preinstalled? A Debian (bookworm) image with Node.js, npm, Python and git; install anything else in the job. Setup actions that download Ubuntu-only builds may fail (actions/setup-python does) (limits).