Your Actions workflow
Use repository-scoped, single-use JIT runners after installing the appropriate Runzivo GitHub App for selected personal or organization repositories.
Availability
Available for personal and organization repositories on GitHub.com. The runzivo-personal GitHub App is live for personal accounts. GitHub Enterprise Server is planned separately.
GitHub Enterprise Server
Planned separately. GitHub.com support does not cover GitHub Enterprise Server. Supported versions, authorization and connectivity are unverified. No Runzivo setup or release date is announced.
Want us to prioritize this integration? Tell us what you need and vote on the public roadmap.
What this integration supports
Ephemeral Linux execution
Each approved job runs in a Firecracker microVM. Current runners use Ubuntu 24.04 on x64, with CI hosts in Ottawa (YOW) and Montréal (YUL).
Published sizes
Choose a published runner label from 2 to 16 vCPU. Custom CPU, RAM and disk profiles are a separate planned capability awaiting production activation.
GitHub Actions
How connection works
Sign in to Runzivo and open your workspace’s GitHub integration. Personal repositories use the runzivo-personal GitHub App; organizations use the organization App. Select the repositories it may access. Installation and repository changes return you to Runzivo. An organization owner may need to approve installation.
Read the GitHub setup guide →Runner sizes
Use the exact runs-on label for your chosen size and review its required plan below. Size requirements are enforced for every workspace. Eligible jobs may wait for compatible capacity; a plan-locked job is refused with plan_required and names the required plan.
| vCPU | RAM (GiB) | Equivalent minutes per running minute | GitHub runs-on label | Required plan |
|---|---|---|---|---|
| 2 | 8 | 1 | rzv-ubuntu-24.04-x64-2vcpu-8gb | Free / Developer |
| 4 | 16 | 2 | rzv-ubuntu-24.04-x64-4vcpu-16gb | Free / Developer |
| 6 | 24 | 3 | rzv-ubuntu-24.04-x64-6vcpu-24gb | Free / Developer |
| 8 | 32 | 4 | rzv-ubuntu-24.04-x64-8vcpu-32gb | Team Upgrade to Team |
| 16 | 64 | 8 | rzv-ubuntu-24.04-x64-16vcpu-64gb | Team Upgrade to Team |
Plan-size enforcement is live for all workspaces. Custom profiles are still coming soon and are not enabled in production.
Standard labels: Free and Developer allow up to 6 vCPU (2, 4 and 6); Team up to 16 vCPU (adds 8 and 16). Business allows up to 32 vCPU, with standard runners currently offered up to 16 vCPU. Enterprise is custom.
A new job requesting a locked size is refused with plan_required and names the required plan. The policy covers new and existing workspaces, with no size-admission grace period or grandfathering. Running jobs are preserved.
Runners keeps supported standard CI sizes visible with CPU, RAM, the equivalent-minute rate, the required plan and an Upgrade to Team or Upgrade to Business action. Plan eligibility is separate from regional capacity. A paid plan does not guarantee immediate capacity.
Usage and pricing
Runner execution draws on your workspace's shared equivalent-minute balance. Prepaid packs are one-time purchases; they are not per-runner subscriptions.
Developer includes 3,000 equivalent minutes per month.
A 2 vCPU GitHub runner uses one equivalent minute per running minute. Larger published sizes use the published multipliers. CI and other metered Runzivo resources share the same allowance and prepaid credit.
| Pack | Equivalent minutes | Price (CAD) |
|---|---|---|
| Starter pack | 5,000 | $28 |
| Team pack | 25,000 | $130 |
| Scale pack | 100,000 | $495 |
Review current checkout availability, other currencies and planned subscriptions on the pricing page.
See full pricing and billing rules →Pipeline example
This Node.js workflow comes directly from the existing verified template catalog. It expects a committed package-lock.json and npm test and build scripts. Adapt the project commands before use.
.github/workflows/01-nodejs.yml
name: Node.js
on:
push:
branches: [main]
pull_request:
workflow_dispatch:
permissions:
contents: read
concurrency:
group: nodejs-${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: ${{ github.event_name == 'pull_request' }}
jobs:
test:
runs-on: rzv-ubuntu-24.04-x64-2vcpu-8gb
timeout-minutes: 15
steps:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
- uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
with:
node-version: 24
cache: npm
cache-dependency-path: package-lock.json
- run: npm ci
- run: npm test
- run: npm run build
Short walkthrough
Follow the route from repository access to a completed job. This guided walkthrough describes the setup; it is not a recording of a production run.
- 01
Connect selected repositories
Install the appropriate GitHub App on your personal account or organization and confirm the repository is included in its access.
- 02
Choose a runner label
Create or update a workflow under .github/workflows and set runs-on to a published Runzivo label. Keep the workflow's existing triggers and permissions intentional.
- 03
Read the result and usage
Trigger the workflow in GitHub Actions, open the job log and verify the runner used. Then inspect the job and equivalent-minute usage in Runzivo.
Setup and troubleshooting
Repository missing
Confirm the correct App is installed on your personal account or organization, the repository is selected and any required organization approval has completed.
Job stays queued
Check the exact label, workspace credit, current concurrency and compatible capacity. Reinstalling the App does not create capacity.
Job fails after starting
Read the first failing step in the Actions log. Check the project's setup commands and required secrets. Share the job URL and visible error with support, without secret values.
Your next step
Start with one personal or organization repository and a small workflow. Verify its job log and usage before moving a larger workload.