Terms

1. What this is

cas.run runs your container on one small machine and gives it a hostname. It is an alpha run by one person as a hobby. There is no uptime promise, no support contract, and no warranty of any kind: it is offered as is, and you use it at your own risk. It may change, pause or stop; where that can be announced in advance, the notice goes on the front page.

2. Your account

Your account is your GitHub login, and the keys on your GitHub profile are what let you in. Keep them yours: what is done with your account is done by you. You must be allowed to agree to terms where you live, and you may have one account.

3. Acceptable use

Run your own small services. Every container shares this machine and its one address with everyone else's, so what one does to the outside world lands on all of them. Do not use it for:

• sending unsolicited mail, or relaying mail for others
• scanning, probing, flooding or attacking any network or host, including this one and the other containers on it
• mining cryptocurrency, or any other way of burning the CPU for its own sake
• open proxies, VPN or Tor exits, or otherwise hiding other people's traffic behind this address
• anything unlawful where you are or where the machine is (Australia), or that infringes someone else's rights, including the licences of the images you run
• working around the limits (memory, processes, disk, the number of services) or the isolation between accounts

If you are not sure whether something is fine, ask first.

4. Limits and enforcement

Every account has units: one service, 64 MB of memory and 1024 MB of disk each, the first unit free. A service over its memory or process limit is contained by the kernel; an account over its disk allowance has its largest running service stopped, and the service's page says why. A service or account that breaks section 3 may be stopped, removed or disabled without notice; where there is time and a way to reach you, you will hear first.

5. Your data

What a container writes inside itself is gone when the container is recreated, which every restart does. There is no backup of this machine you may rely on; keep anything you care about somewhere else. To run the service the operator can see what your containers hold, their logs and their environment, and will look only to keep things running or to act on section 3. The site keeps your login, your services and their settings, a hash of your tokens, your sponsorship amount as GitHub reports it, and ordinary server logs for a short time. Nothing is sold or shared.

6. Paying for units

Units beyond the free one come from sponsoring the operator on GitHub from the account you log in with; cas.run never sees a card. GitHub's own terms apply to the payment. A unit lasts as long as the sponsorship, to the end of the period already paid for; a one-time sponsorship counts for a year. When units lapse, services beyond what is left are not removed, but a custom domain is detached and nothing new can be created until you are within your units again. Refunds are GitHub's to give, and there are none for time already used.

7. Ending it

You can delete your services and stop sponsoring at any time. The operator may end the service for everyone with notice on the front page, and for one account at once under section 4. These terms may change; the date below says when they last did, and continuing to use the service after a change is agreeing to it.

Last changed 20 October 2026. Run by prologic. Questions and reports: the issue tracker.