For engineering teams

The afternoon problem

A team of ten pushes a lot. On GitHub-hosted runners, that means a queue at the busiest hour, a bill that grows with the team, and a slow conversation every quarter about whether the bigger runners are worth it. Apex Actions replaces all three with one decision: pick a plan.

What changes for the team

• Nothing in the workflow files. Once the App is installed and the trial started, the next push runs on Apex. Checks and annotations land on the pull request; the logs are on the run screen in the Apex dashboard. Each check run is named <workflow> / <job> (<workflow> / <caller> / <called job> for a reusable workflow's jobs), so re-select any required status check.
• Jobs start in seconds on a warm runner, and in about a minute when a machine has to start. Capacity scales with your queue, up to your plan's concurrency.
• Larger runners are included. runs-on: apex-4core-x64 is a one-line change, not a budget request; a minute on it draws two standard minutes.
• Flaky tests are named. One warning on the pull request, never a second failure, and the matrix leg is part of the name.
• Slow steps are called out. Every step is timed against its own history; nobody reads a log to find the gap.

What changes for whoever pays

One subscription with included minutes, overage at half GitHub's rate, and no charge per person — and typically about half the cost of the GitHub-hosted runner minutes you pay for today, at the usage each plan is sized for (how we compare). Your GitHub seats are unchanged; the repositories stay where they are. Every plan starts with a 10-day trial, without a card.