Dedicated runners
Each host serves exactly one runner.
GitHub Actions runnerGA
Fast CI, inside your network
Run runners on your servers or dedicated whycloud hosts; builds sit next to your registry and internal services.
- 1:1
- dedicated host
- 0
- stored credentials
- Buildx
- cache
Live
HOW IT WORKS
How it works
- 1
Choose a host
Your server or a cloud group.
- 2
Connect the repo
owner/repo and a registration token.
- 3
Run
Workflows with runs-on: self-hosted.
Capabilities
GitHub Actions runner
No stored credentials
Registration tokens live only in memory, only at registration.
Registry cache
Buildx cache-from/cache-to on the whycloud registry.
Your server or whycloud
On-prem or cloud runner groups.
FAQ
Frequently asked questions
Is my GitHub token stored?
No; it is handed to the runner only during registration.
Related services
Cloud Servers & VMswhycloud cloud servers: connect Linux hosts with one command, web term…PaaS container appswhycloud PaaS: give a Compose file or a docker run command and the app…GPU & parallel computeManage GPUs for AI training and inference on your own hardware: usage …Container registrywhycloud registry: on-prem on your server or cloud, proxy cache for Do…
Turn on your own cloud today
Create an account and connect your first server in under five minutes.