Small
249.99 PLN/ 30 days
- 1 concurrent jobs
- 4 vCPU · 8 GB RAM / VM
- 40 GB scratch storage
- 25 GB S3 cache
- 2 500 GB transfer per period
- Up to 120 minutes per job
Separate from GitLab CE hosting
AwesomeSRV VM runner service for GitLab™
Prepaid P30D runner pools use GitLab Runner docker-autoscaler and a pinned OpenStack fleeting plugin. Jobs are polled outbound and require no inbound connection.
GitLab.com / Self-ManagedHTTPS 443 · trusted CA
docker-autoscaleroutbound polling · no inbound port
OpenStack VMOne job, then guaranteed VM destruction
Fixed concurrency and infrastructure limits
Unlimited job count within the paid concurrency, transfer and cache quota. There is no rollover or postpaid usage.
Medium
599.99 PLN/ 30 days
- 3 concurrent jobs
- 4 vCPU · 8 GB RAM / VM
- 60 GB scratch storage
- 100 GB S3 cache
- 5 000 GB transfer per period
- Up to 120 minutes per job
Large
1,299.99 PLN/ 30 days
- 4 concurrent jobs
- 8 vCPU · 16 GB RAM / VM
- 100 GB scratch storage
- 250 GB S3 cache
- 10 000 GB transfer per period
- Up to 120 minutes per job
External GitLab supported
Yes — a pool can connect to another GitLab instance
After the pool is active, link it with a current runner authentication token. The control plane validates the endpoint and passes the token directly to the infrastructure agent; only an opaque reference is stored.
- Root HTTPS URL on port 443 with a publicly trusted CA and public DNS addresses
- Current glrt- runner authentication token; legacy registration tokens are rejected
- Outbound polling only; no inbound port is opened on the runner manager or job VMs
- One job per OpenStack VM and destruction immediately after the job