team beta
For companies evaluating Sorus for their Rust CI workloads.
Monthly price by agreement
Allowance, concurrency, support and the transition from introductory terms agreed in writing.
Monthly beta pricing is agreed with each customer. Your agreement sets price, usage allowance, concurrency and support.
For companies evaluating Sorus for their Rust CI workloads.
Monthly price by agreement
Allowance, concurrency, support and the transition from introductory terms agreed in writing.
For developers evaluating cloud Rust execution on their own projects.
Request individual access
Availability and introductory terms confirmed during onboarding.
For nonprofit and independent, non-commercial projects. Funded commercial projects use the team offer.
Apply for sponsored access
A specified usage allowance and duration for each accepted project.
The planned subscription includes a monthly allowance of standard units for build and test work. Units measure reference work rather than machine minutes.
Standard-unit billing is still in development. Your written beta terms set the price and usage limits during evaluation.
read the pricing modelThe cost depends on your workload, runner, cache use, utilisation and price. We can compare your current workflow with the agreed Sorus subscription. The published benchmark records measure timing only.
Yes. Tell us about your project and budget. Access depends on workload support and available capacity; terms are agreed during onboarding.
The planned billing model counts completed execution even when a build or test fails. Platform failures are not billable. The cancellation rules and your introductory terms are explained in the billing guide.
No. Sponsorship is for independent non-commercial projects and nonprofit maintainers. Commercially funded projects use the team offer.
Apply for beta access. We'll confirm workload support and pricing before you start.