Self-hosted & Cloud runners
Choose where CI executes and how much capacity it can use. Openship checks destination capabilities and manages worker startup, cancellation, and cleanup.
Linux and native macOS are supported. Windows runner destinations are not available.
Open the guideHow it works
Select an existing server, create a dedicated managed server, or use temporary Cloud runners. Configure OS and architecture labels, execution images, per-job CPU and memory, and parallel limits.
Linux supports container or native execution; connected Macs support native jobs. Temporary jobs receive disposable Linux VMs funded from the Actions balance. Persistent destinations execute code trusted by their administrator.
What you can do
Capacity controls
Reserve parallel slots and configure job resources.
Capability checks
Match labels to the actual OS, CPU, and toolchain.
Disposable workers
Remove temporary job VMs after confirmed cleanup.
Explore more
Ship it your way.
Self-hosted and free, or managed on Openship Cloud — the same workflow either way.