supported workloads
Cargo operations, toolchains, machine classes and restrictions.
For: Rust developers checking workload compatibility
beta support matrix
As of 6 October 2026, all nine entries in the source support manifest are candidate: they are undergoing release qualification. Onboarding confirms which workloads your beta release supports.
| Dimension | Candidate scope |
|---|---|
| Operations | Cargo check, build, test |
| Platform stable | Rust 1.98.0 |
| Other exact toolchains | 1.97.1, 1.91.1, nightly-2026-08-15 |
| Dependencies | Locked crates.io inputs through the per-job dependency gateway |
| Git dependencies | HTTPS Git under the documented snapshot and gateway rules |
| Source links | Relative links confined within the captured source tree |
| Build inputs | Declared inputs and accepted environment under the release’s policy |
Download the support manifest for the constraints on each entry.
unsupported workloads
The candidate scope excludes:
- Private or alternative registries.
- Public internet egress, containers and external services.
- SSH Git dependencies and Git submodules.
- Absolute symlinks and links that escape the captured source tree.
- Unlisted toolchains and arbitrary extra targets or components.
Some registry credential operations appear in the API reference, but private registry execution remains outside the candidate scope.
machine classes
The generated CLI reference lists sorus-4cpu, sorus-8cpu and sorus-16cpu, with 8 as the default. Source also includes a 2-vCPU class; the reference and release support still need reconciliation.
Use the classes and architecture confirmed during onboarding. Concurrency and capacity follow your beta terms.
requesting support
If your workload needs something outside this scope, contact us. Retain your existing CI until you have verified the workload on the release you will use.