Skip to content

Included in every plan

Enzonic CI

Hosted pipelines for your GitHub repositories on Enzonic runners: tests and builds on every push and pull request, with caches, live logs and artifacts. CI minutes, parallel jobs and retention come with your plan.

A console built for pipelines

Runs, jobs and steps with their logs, on the same account as Deploy and Databases. Screens from the console with sample data.

Enzonic CI: the runs of a pipeline with their status, branch and duration
Enzonic CI: every pipeline with its latest runs and status

What it does

  • Runs on every push and pull request

    Connect a GitHub repository and pipelines run on pushes, tags and pull requests, on a schedule, or when you start them from the console or the API.

  • Matrix builds and job dependencies

    Split work into jobs, fan out over a matrix and order them with needs. Service containers such as Postgres join the job's network.

  • Dependency caches

    npm, pnpm, Yarn, Bun, pip, Go, Cargo, Maven and Gradle caches are kept per repository within your plan's cache size, so repeat runs skip most of the install.

  • Isolated sandboxes

    Each job runs in its own gVisor sandbox on its own network, with no access to private networks or the host.

  • Live logs and artifacts

    Follow each step as it runs, re-run failed jobs, and download artifacts while your plan keeps them.

  • Fixes for failed jobs

    Enzica, Enzonic's assistant, can read a failed job's logs and propose a code fix you review before anything changes.

Measured against GitHub Actions

The same workflow file on both platforms, in a private benchmark repository. Medians in seconds; lower is faster.

Enzonic CI and GitHub Actions run times
StepEnzonic CIGitHub Actions
Whole run, from push to every job done22 s37 s
Queue to start6 s9–10 s
Checkout0.06 s1 s
npm ci with an unchanged lockfile0.09 s3 s
go test with empty caches2.8 s20 s
Go job, wall time2 s11 s
npm ci, first install of a new lockfile6.8 s4 s

Where we are slower: the first install of a new lockfile, because every file passes through the job sandbox. Every later run with the same lockfile takes 0.09 s. Method: medians of three runs with warm caches (the cold rows use empty caches; GitHub cold is one run), GitHub on ubuntu-latest, measured on 1 November 2026.

Configuration you already know

Write .enzonic/ci.yml, or keep the GitHub Actions workflows you have: Enzonic CI runs the supported subset and tells you about the rest.

.enzonic/ci.yml
name: CI

on:
  push:
    branches: [main]
  pull_request:

jobs:
  test:
    image: node:22-bookworm-slim
    services:
      postgres:
        image: postgres:17-alpine
        env:
          POSTGRES_PASSWORD: postgres
    env:
      DATABASE_URL: postgres://postgres:postgres@postgres:5432/postgres
    steps:
      - name: Install
        run: npm ci
      - name: Test
        run: npm test

An example. The CI reference in the docs lists every supported key and action.

CI limits per plan

CI minutes reset every month. Paid plans add more minutes, parallel jobs and longer retention.

Enzonic CI limits of every plan
FeatureFree freeStarter $5/moPro $10/moGrowth $19/moBusiness $29/mo
Enzonic CI
CI minutes3,000/mo5,000/mo6,000/mo15,000/mo60,000/mo
Concurrent jobs2461020
Job timeout360 min360 min360 min480 min720 min
Dependency cache2 GB5 GB10 GB20 GB50 GB
Artifacts / logs kept90 / 14 days90 / 30 days90 / 30 days180 / 60 days400 / 90 days

Questions

Is Enzonic CI included in my plan?

Yes. Every plan, Free included, comes with CI minutes and parallel jobs at no extra cost. The table on this page shows the limits of each plan.

Do I have to rewrite my GitHub Actions workflows?

Often not. Enzonic CI reads .enzonic/ci.yml, or a supported subset of .github/workflows. Steps it cannot run, such as Windows or macOS runners and reusable workflows, are reported with a clear message instead of failing silently.

How are CI minutes counted?

Per finished job, against the monthly allowance of your plan. The console shows how many minutes each run used.

Are secrets safe on pull requests from forks?

By default, runs for pull requests from forks get no secrets. You can also turn fork pull requests off for a pipeline.

Run your first pipeline

Connect a GitHub repository on the Free plan. No card.

Open Enzonic CI