pricing & usage
How the planned usage model relates to beta agreements and job outcomes.
For: Teams evaluating beta costs
Sorus’s selected commercial model separates a monthly work allowance from the machine time used to perform that work. Beta agreements define the actual offer while billing implementation and public rate calibration continue.
beta terms
Beta pricing is agreed in writing. Public monthly rates, allowances and overage prices are not yet available. This website does not take payment or start a subscription.
The agreement defines the charge or sponsorship, included work, concurrency, limit behavior, support, cancellation and transition terms. View pricing.
planned usage model
The selected model provides a monthly allowance in standard units, with separate build-work and test-work components. A standard unit measures reference work rather than elapsed machine time. Sorus does not publish a per-minute rate.
This distinction matters when comparing workloads that do different amounts of compilation or testing. A shorter elapsed time does not by itself specify the customer’s charge. The beta agreement also establishes how usage is reported while the billing system is being completed.
planned treatment of job outcomes
A completed compilation or test can provide a useful result even when the code fails. The selected model therefore distinguishes a workload failure from a failure of the execution platform:
| Event | Treatment |
|---|---|
| Successful workload | Counts as verified work. |
| Compiler or test failure | Can count as verified work. |
| Platform failure | Not billable. |
| Cancelled before running | No charge. |
| Cancelled while running | Counts toward the allowance, not billed; see agreed terms. |
| Same-key duplicate delivery | Does not create another verification. |
| Deliberate new run | A new verification. |
These rules describe the selected model. The beta agreement governs charges; automated invoicing is not confirmed as live.
cost comparisons
The early benchmarks report timings only. They exclude internal machine-cost estimates because those are not customer prices. A cost comparison also needs the workload volume and the customer’s agreed pricing.