Skipbox
日本語

Skipbox Terms of Service

Effective: 9 November 2026. Last updated: 9 November 2026 (yearly billing added, every payment refunded on a request within 30 days, refunds of unused days when we end or worsen a plan or close an account, and where queued jobs are shown: Sections 3, 5, 6, 7 and 11).

These Terms are the agreement between Fluxenic Inc. and you for the use of Skipbox. The Japanese version says the same thing. If the two differ, the Japanese version prevails.

1. About these Terms

  1. Skipbox (skipbox.dev) is run by Fluxenic Inc. ("Fluxenic", "we", "us"), a company in Tokyo, Japan.
  2. You accept these Terms when you sign in to Skipbox, install a Skipbox app on a GitHub organization or personal account, start a trial, or subscribe to a plan. If you accept them for an organization, you confirm that you may bind it, and "you" means that organization.
  3. We may change these Terms where the change is in the general interest of customers, or where it doesn't go against the purpose of our agreement and is reasonable (Article 548-4 of the Civil Code of Japan). Before a change takes effect, we post the new Terms on this page, with what changes and the date it takes effect. If a change is worse for you, we also email you at least 30 days before it takes effect, and you can cancel before then.

2. Accounts and organizations

  1. You sign in with your GitHub account. You must be 18 or older and able to make a binding contract.
  2. Keep your GitHub account secure. If you think someone else has used your Skipbox account, tell us at once at hello@skipbox.dev.
  3. Skipbox serves GitHub organizations and personal GitHub accounts. An owner of an organization installs the Skipbox CI app on it; the owner of a personal account installs the Skipbox (personal) app on it. Each plan or trial covers one organization or personal account, and each can hold any number of plans. In these Terms, "your organization" also means your personal account when you use Skipbox on one, and "the Skipbox app" means whichever of the two apps you installed.

3. What Skipbox does

  1. Skipbox runs the GitHub Actions jobs of your organization's private repositories on self-hosted runners that we operate, for a flat price, billed monthly or yearly, with no charge per minute.
  2. Each job runs in a new virtual machine made for that job alone. When the job ends, the virtual machine is destroyed; nothing from it is kept for your next job or for anyone else. A job runs for at most 6 hours, counted from when its virtual machine starts; at 6 hours its virtual machine is destroyed and the job ends.
  3. Skipbox runs jobs only from repositories that GitHub marks private. It refuses a job from a public repository, because anyone can open a pull request there and run code on the runner, and shows the refusal on your organization's page on skipbox.dev.
  4. On GitHub, Skipbox registers a runner for one job at a time, with your organization or, on a personal account, with the job's repository, and removes it after the job, and it reads the status of your jobs. GitHub lets an app register a runner with a repository only with the repository permission "Administration", so the Skipbox (personal) app asks for it; Skipbox uses it only to register and remove runners. To suggest plans, it also reads the last 30 days of your organization's GitHub Actions job history (privacy policy, section 2). It never pushes to your repositories and never changes your workflow files: you choose which jobs run on Skipbox by changing runs-on: in your workflows yourself.
  5. Skipbox runs in one region, Helsinki, Finland, on servers we rent from Hetzner Online GmbH (Germany): our dedicated servers and, when they have no room for a job, a Hetzner Cloud server made for that one job and deleted after it.

4. Your workflows, code and secrets

  1. Your repositories, workflows, code and secrets, the output of your jobs, and anything else your jobs use or make are yours ("your content"). You give us only the permission we need to run your jobs and operate Skipbox.
  2. When a job runs, GitHub sends what the job needs to the runner in that job's virtual machine. As on any runner, that can include your code, the secrets your workflow passes to the job, and a GitHub token for that job. They stay in that virtual machine and are destroyed with it. We don't copy or keep them, and we don't record your job logs: GitHub keeps them.
  3. You are responsible for what your workflows do and the code and actions they run, and for your secrets and your GitHub settings, such as who can start a workflow.

5. Plans, trial and queueing

  1. The plans are billed monthly or yearly, in US dollars, with no usage charges. Total minutes are unlimited on every plan (a single job's time limit is set out in Section 3.2).
    • S: US$39 a month, or US$390 a year. 4 vCPU and 8 GB of memory.
    • M: US$79 a month, or US$790 a year. 8 vCPU and 16 GB of memory.
    • L: US$149 a month, or US$1,490 a year. 16 vCPU and 32 GB of memory.

    A yearly plan is paid for the whole year in advance and costs 10 times the monthly price. You choose monthly or yearly billing when you subscribe, and every plan in your organization's subscription is billed the same way.

    Your organization can hold any number of plans, in any mix, in one subscription. Its capacity is the vCPU of those plans added together. Each job runs at one of three sizes, as its runs-on: label asks: 4 vCPU and 8 GB of memory, 8 vCPU and 16 GB, or 16 vCPU and 32 GB. A job runs at a size no larger than the largest plan you hold: with only S plans, 4 vCPU jobs; with an M, up to 8 vCPU; with an L, up to 16 vCPU. Skipbox refuses a larger job and shows why on your organization's page. A job starts when its vCPU fits in your capacity together with your organization's jobs already running.

  2. Trial. While we offer trials, each GitHub organization can have one trial, and so can each GitHub user; a trial needs an email address we can write to. The trial needs no card. It starts when your organization's first job reaches Skipbox. It runs 1 job at a time with 4 vCPU and 8 GB of memory, for 7 days or 3,000 job-minutes, whichever comes first. When our servers are busy, trial jobs can wait longer than paid jobs. When the trial ends, Skipbox stops taking your organization's jobs until you choose a plan; nothing is charged.
  3. Queueing. A job that doesn't fit in your organization's capacity together with its running jobs waits until it does. A job can also wait when our servers are full; your organization's page on skipbox.dev shows how many jobs are waiting and how long the oldest has waited. GitHub cancels a job that has been queued for 24 hours.
  4. We open payment for a plan only when our servers have room for it.

6. Payment, renewal and cancellation

  1. You pay by card through Stripe. Your card is charged the price of your plans when you subscribe, and again on the same day each month until you cancel, or, with yearly billing, the price of a year of your plans on the same day each year. If you add plans while you pay, your card is charged at once for the added plans for the rest of the current month, or of the current year with yearly billing (the amount is shown before you pay), and from the next renewal for all your plans.
  2. Prices are in US dollars. No tax or fee is added to the prices shown. If your card is in another currency, your card issuer converts the amount at its own rate and may add its own fee.
  1. Only the person who installed the Skipbox app on your organization can buy plans for it; on a personal account, that is its owner. That person opens the billing portal from the billing link on your organization's page on skipbox.dev and can cancel there at any time. Your plans run to the end of the month, or with yearly billing the year, you have paid for, and your card isn't charged again. Then Skipbox stops taking your organization's jobs. Adding plans after you cancel withdraws the cancellation: your plans renew again. To have fewer plans, cancel in the billing portal, or write to hello@skipbox.dev and we change them. To switch between monthly and yearly billing, write to hello@skipbox.dev. The switch takes effect at your next renewal: we reply with the new price and the date it is charged, and change nothing until you confirm by email. The period you have paid for isn't refunded.
  2. If a renewal payment fails, we email you on the day it fails and 3 and 6 days later, and Stripe tries the card again on its own schedule. If the payment still hasn't gone through 7 days after it first failed, Skipbox stops taking your organization's jobs. Your plans stay open while Stripe keeps trying: if a later try succeeds, your jobs run again until the end of the month (or, with yearly billing, the year) that payment covers, which began on the renewal date. Until the payment goes through or the plans end, no new plans can be bought for the organization. To avoid a later charge, cancel in the billing portal.

7. Refunds

  1. If, in the period a new subscription's first payment covers (its first month, or its first year with yearly billing), your organization's first job doesn't start within 10 minutes of its turn (time it waits behind your own running jobs doesn't count), we refund in full automatically every payment for that subscription in that period, plans added included, end all its plans at once, and email you. A job you cancel or that Skipbox refuses doesn't count; the next one does. If no job has its turn in that period, this refund doesn't apply.
  2. If you ask within 30 days of your organization's first payment for Skipbox, we refund in full that payment and every other payment for the same subscription, whether for a month or a year, and all its plans end then. Ask by email to hello@skipbox.dev.
  3. Except as paragraphs 1, 2 and 4 and Section 11.2 say, we don't refund a month or a year, or part of one, including when you cancel partway through a month or a yearly plan's year, except where the law requires it.
  4. If we end Skipbox or your plan, or make a change that reduces what your plan includes or is worse for you (Sections 1.3 and 10.2), before the end of a period you have paid for, we refund the part of the payments for that period for the days left in it. If you cancel because of such a change before it takes effect, your plans end when it takes effect and we refund the same way.
  5. A refund goes back to the card you paid with. Your bank may take 5 to 10 business days to show it.

8. Acceptable use

  1. Don't use Skipbox, or let your workflows use it, to:
    • mine cryptocurrency;
    • scan or probe networks or systems that you don't own or aren't allowed to test;
    • send spam or bulk email;
    • host or send phishing pages or malware;
    • attack any system or service, for example by denial of service or by breaking into accounts or systems;
    • run a proxy, VPN or relay for other people;
    • break the law or infringe anyone's rights;
    • get around Skipbox's limits, for example by starting more than one trial for an organization or a person, or by sharing one plan among organizations;
    • interfere with Skipbox, our servers or other customers, for example by trying to leave your virtual machine or reach our hosts.
  2. One customer's abuse can get our servers or our hosting account blocked for every customer. Each job runs in a new virtual machine of its own, which is deleted after the job, and we may stop a job that we reasonably believe breaks Section 8.1 (Section 11.1).
  3. Report abuse to hello@skipbox.dev.

9. (Deleted)

10. Availability and changes to Skipbox

  1. At launch Skipbox has no service level agreement and no service credits. Jobs may wait, fail or stop, for example when our server is full or fails, during maintenance, or when GitHub or one of our providers has a problem. A job that ends this way can be re-run from GitHub.
  2. We may change Skipbox's features. We email you at least 30 days before a change that reduces what your plan includes, and before we end Skipbox or your plan. From the day we tell you that Skipbox or your plan will end, we stop renewing it, so you aren't charged for a period we won't serve.

11. Suspension and closing accounts

  1. We may stop a job, or suspend your organization's use of Skipbox, without notice when we reasonably believe it breaks Section 8 or puts our servers, our network address or other customers at risk. We tell you why by email, and we restore it once the problem is solved, unless the breach is serious or repeated.
  2. We may close your account for a serious or repeated breach of these Terms, after telling you by email. In that case, we refund the part of the payments for the current period for the days left in it, less the loss the breach actually caused us.
  3. You can ask us to delete your account at any time by emailing hello@skipbox.dev from the address we hold, and we delete it within 7 days. Deleting it doesn't cancel your plans by itself: cancel them in the billing portal first.

12. Deleting data

  1. Each job's virtual machine, and everything in it, is destroyed when the job ends, and in any case 6 hours after its virtual machine starts.
  2. When your plan or trial ends, or you uninstall the Skipbox app, we stop taking your organization's jobs and remove our runners from it.
  3. When we delete your account at your request, we delete its data, except the records our privacy policy (section 7) says we keep.
  4. Your code and job logs stay in GitHub. Skipbox keeps no copy of them, so there is nothing for us to export.

13. GitHub

  1. Skipbox isn't made, run or endorsed by GitHub. Your use of GitHub and GitHub Actions is under your own agreement with GitHub. GitHub may limit or turn off Actions for your organization, and a problem at GitHub can stop your jobs.
  2. GitHub doesn't charge for jobs on self-hosted runners today: its billing documentation lists "Self-hosted runners" under usage that "remains free" (read 8 November 2026). GitHub announced a charge of US$0.002 per minute for self-hosted runners on 16 December 2025, then postponed it. If GitHub ever charges for jobs that run on Skipbox, GitHub bills your GitHub account under its own terms. Skipbox's prices don't include that charge, and we don't pay it.

14. Disclaimer

Except as Section 15 says, Skipbox is provided as it is and as it is available. We don't promise that it will run without interruption or error, or that it suits a particular purpose.

15. Liability

  1. If our intent or gross negligence causes you a loss, we compensate you for it, and we don't limit that liability.
  2. If our ordinary negligence (negligence that isn't gross negligence) causes you a loss, through a breach of our obligations or a tort, we compensate only the direct loss that would ordinarily result, up to the total of the fees you paid for Skipbox in the 12 months before your claim, or US$100, whichever is greater. These limits apply only to our ordinary negligence.
  3. Section 14 and the other provisions of these Terms don't exclude or limit our liability under this section.
  4. In this section, our intent, gross negligence and ordinary negligence include those of our representatives and of anyone we employ or engage.

16. Governing law and court

These Terms are governed by the laws of Japan. The Tokyo District Court has exclusive jurisdiction as the court of first instance over any dispute arising from them.

17. Contact

Fluxenic Inc., Shibuya Dogenzaka Tokyu Building 2F-C, 1-10-8 Dogenzaka, Shibuya-ku, Tokyo, Japan. Email: hello@skipbox.dev.