Accounts and billing
Faster, or your money back
How Skipbox measures whether your jobs are faster than on GitHub-hosted runners, and how to get every payment back when they aren't.
If, within 30 days after a new subscription's first payment, your jobs aren't faster on Skipbox than on GitHub-hosted runners, you get every payment for that subscription back in full. Monthly and yearly billing alike. This page is the method that decides "faster".
Ask for it
The person who bought the plans presses Request refund on your account's Plans and billing page on skipbox.dev. Requests are taken until exactly 30 days after the moment of the first payment, to the second; the page and the email confirming your plans show that moment with its time zone. The page also shows the comparison as it stands.
Every payment made for that subscription by then comes back in full, added plans included, and its plans end at once. You're emailed when it's done.
What's compared
- On GitHub: each job in the GitHub Actions history Skipbox reads when you install the app (the last 30 days), for jobs that ran mostly on GitHub-hosted runners: the median time of its successful runs. Skipbox copies these medians at your first payment and compares with that copy, so uninstalling the app doesn't change them.
- On Skipbox: the same job's median over its successful runs that reached Skipbox in those 30 days and finished.
How a job is timed
Both sides on GitHub's own clock: from when GitHub queued the job until GitHub completed it, by the times GitHub records for each job. Time a job waits counts on both sides: in GitHub's queue on GitHub, in your account's queue on Skipbox. A job that was held and put back in line (after plans were added, say) counts from when it was put back.
The same job
A job is a job name in a repository with its steps: the names of the job's steps, in order. The steps the runner adds itself don't count: "Set up job", "Set up runner", "Complete runner", "Complete job", and an action's clean-up step (named "Post" and the name of an earlier step). On GitHub, of the step lists the job succeeded with at least 3 times, Skipbox uses the one it succeeded with most recently.
Moving a job to Skipbox changes only its runs-on: line, so a job you moved unchanged keeps its steps. If you change a job's steps after moving it, its runs after the change don't count.
Which runs and jobs count
- Only successful runs, those GitHub reports as succeeded. A run that failed, was cancelled or timed out doesn't count, and nor does a run whose steps or times Skipbox couldn't read.
- A job counts once it has succeeded at least 3 times with those steps on each side.
- A job name that two workflows of one repository share in the GitHub history doesn't count: Skipbox can't tell them apart.
The verdict
Each job is weighted by how many times it succeeded with its steps in the GitHub history, so your usual mix of jobs decides it and runs added after paying don't move the weights. Skipbox is faster when the weighted total of the jobs' medians on Skipbox is less than the weighted total of their medians on GitHub. If no job counts, there is nothing to compare and this refund doesn't apply.
Once
Each account, and each person, gets this refund once. A subscription already being refunded another way (a second subscription by mistake, or a first job that didn't start in time) isn't refunded twice. See Billing, invoices and refunds for those refunds.
If you started before 19 November 2026 (Japan time)
This applies if, before that date, the app was installed on your account, the person who installed it or the person who bought the plans first signed in to Skipbox, or your subscription was first paid. A job's time on Skipbox then runs from when it reaches Skipbox until it finishes, and is compared with its time on GitHub from when it started on a GitHub-hosted runner until it completed. If any of these was before 18 November 2026, a job is also matched by its name alone, whatever its steps, and every run counts, successful or not.
Questions
Write to hello@skipbox.dev.
Updated November 18, 2026