Home / Compute
Quansight
github.com/Quansight/open-gpu-serverCI runnercompute/quansightJSONcomparereport an errorprovider JSON
- Free allowance
- This was the clearest free-GPU-CI offer in the open-source ecosystem and it is gone.
- Verdict
- deadthe offer or the service no longer exists
- Cost
- no price stated
- Identity
- institutionno card, no phone
- Binding limit
- write-gatedTwo things failed, in order: access required a conda-forge feedstock and a maintainer listed in the project's access file, which is an institutional affiliation a user does not hold, and then the hardware was decommissioned on...
- Evidence
- documented4 sources; a first-party page was read and the sentence quoted
- Freshness
- checked 2026-10-22checked 2026-10-22 (live)
| Free tier | This was the clearest free-GPU-CI offer in the open-source ecosystem and it is gone. Quoted at the top of the repository: 'The server will be decommissioned as of 2026-03-13 and the service will not be available from then on.' What it offered while alive: an OpenStack host with '48 Cores', '~500 GB Memory' and '6x NVIDIA Tesla V100', spinning up runners from gpu_tiny at 4 vCPU / 2 GB / 20 GB / 1x V100 up to gpu_4xlarge at 8 vCPU / 64 GB / 100 GB / 1x V100, free to conda-forge feedstocks that needed GPU CI. Quoted limitation: 'Only 4 GPUs can be exposed to the VMs at a time; expect queues. This is not per repository, but a server-wide limitation.' unit GiB; metered on wall-clock; sponsored-community-service |
|---|
| Price | none stated |
|---|
| Limits | - write-gated (binding) Two things failed, in order: access required a conda-forge feedstock and a maintainer listed in the project's access file, which is an institutional affiliation a user does not hold, and then the hardware was decommissioned on 2026-03-13, so the capacity is now zero on both counts. source
|
|---|
| Identity | institution not published |
|---|
| Egress | not stated |
|---|
| Interface | unknown inferred from the tooling the provider documents; not probed |
|---|
| Tooling | not stated |
|---|
| Composes with | Nothing to chain now. The structural lesson is that the free-GPU-CI lane existed as one sponsored host with six GPUs, four of them exposed at a time, and it went away with one colocation decision. |
|---|
| Reliability | no reliability event recorded |
|---|
| Notes | The free GPU CI lane is not a category with several providers in it; it was one sponsored OpenStack host for one package ecosystem, gated on being a conda-forge maintainer, and it is decommissioned. The nearest live substitute is GitLab's OSS programme with its T4 runner, recorded separately, and the nearest paid substitutes are GitHub's GPU larger runner at USD 0.052 a minute and external runner vendors. |
|---|
| Parsed numbers | |
|---|
Evidence 4
| date | source | what it proved |
|---|
| 2026-10-22 | github.com/Quansight/open-gpu-server | 'The server will be decommissioned as of 2026-03-13 and the service will not be available from then on.'; base host 48 cores, ~500 GB memory, 6x NVIDIA Tesla V100; the six gpu_* and five ci_* runner shapes; 'Only 4 GPUs can be exposed to the VMs at a time ... a server-wide limitation'; 'We have not yet implemented a time limit per job' |
| 2026-10-22 | raw.githubusercontent.com/Quansight/open-gpu-server/main/REA | the same text from the repository's own main branch, confirming the decommission notice is not a rendering artefact |
| 2026-10-22 | github.com/stumpy-dev/stumpy/issues/1005 | reported origin: at SciPy 2024 the project learned that 'free GPU runners are available via the Quansight's/MetroStar's Open GPU Server', which fixes roughly when was known and how it was described to outsiders |
| 2026-10-22 | conda-forge.org/blog/2026/06/17/large-runners-gha/ | the successor did not restore GPU: conda-forge moved to GitHub Actions large runners and states 'Sadly, we don't have GPU CI jobs yet.' |
More fields 1
| facets | {"class": "ci-runner-capacity","free_tier_kind": "sponsored-community-service","shape": {"vcpu": 4,"ram_gib": 8,"gpu_class": "V100","gpu_count": 1}} |
|---|
Unknown values 7
- egress metered: egress metering was not published
- egress terms: a source was read and is silent on this field
- interface: the access interface was not established
- per object cap stated: the field does not apply to this kind of offer
- reliability note: nothing of this kind was observed
- retention stated: the field does not apply to this kind of offer
- tooling: a source was read and is silent on this field