Features
Your workflows, unchanged
The same YAML, the same actions, the same checks on the pull request. Apex Actions runs GitHub Actions workflows as GitHub would, and proves it with a conformance suite.
Drop-in means drop-in
Install the GitHub App on an organisation. That is the only change GitHub sees. Your
.github/workflows/*.yml files stay exactly as they are — the triggers, the matrices, the reusable
workflows, the expressions, the marketplace actions, the caches and the artifacts.
What that covers
| In your workflow | Runs on Apex |
|---|---|
on: push, pull_request, schedule, workflow_dispatch, workflow_run, repository_dispatch | Yes |
strategy.matrix, include/exclude, fail-fast, max-parallel | Yes |
${{ }} expressions, contexts and functions | Yes |
Reusable workflows (uses: org/repo/.github/workflows/x.yml@ref), local and remote | Yes |
| Composite, JavaScript and Docker actions from the marketplace | Yes |
actions/cache, actions/upload-artifact, actions/download-artifact | Yes |
concurrency groups and cancel-in-progress, at run and job level | Yes |
environment with required reviewers, wait timers and branch policies | Yes |
permissions and id-token: write for OIDC | Yes |
| Check runs, annotations and log output on the pull request | Yes |
How we know
Compatibility is not a promise; it is a test suite. Every documented GitHub Actions behaviour has a fixture, and a change to how Apex runs a workflow lands only with a fixture proving it matches GitHub. The compatibility matrix in the docs is generated from that suite.
Same workflows. Half the bill.
Every plan starts with a 10-day trial, without a card.