Pricing and Costs on Varity
Varity documentation does not maintain a price book. Per-resource prices, per-model AI rates, catalog availability, and resource profiles can change independently of this site. A copied value would become a second, discrepancy-causing owner.
Every price is charged in USD from one prepaid balance. Plans, top-ups, and the Free plan are described in Billing and Pricing.
Current Price Sources
Section titled “Current Price Sources”Use the source that matches the workload:
| Workload | Current source |
|---|---|
| Managed applications and static sites, plans, Free allowance, and top-ups | GET https://varity.app/api/pricing or the Developer Portal quote shown before deploy |
| Pre-deploy application estimate | GET https://varity.app/api/pricing?profile=<profile> (no key needed) or varity_cost_calculator. GET https://varity.app/api/pricing/estimate also works but needs your key |
| CPU VM or GPU machine | POST https://varity.app/api/pricing/machine-quote |
| AI Gateway request rates | GET https://ai.varity.app/v1/models |
| Your plan, balance, and free allowance | The billing page of the Developer Portal (GET https://varity.app/api/billing/account) |
How Billing Is Shaped
Section titled “How Billing Is Shaped”- Application pricing is tied to the selected reserved profile. Read the live response for the applicable maximum, proration, storage, replica, and billing policy.
- Machine and accelerator prices are bound by a time-limited quote. If the quote expires or the requested workload changes, request a new one.
- AI Gateway request rates come from the live model catalog. Free plan usage covers only Chat, Build, and static apps; API key requests need a paid balance from a subscription or top-up.
- A price shown when a billable action is confirmed is the transactional price for that action. Documentation never authorizes a charge.
Deletion and Billing Closure
Section titled “Deletion and Billing Closure”Deletion can be asynchronous. An accepted delete request is not proof that routing, resource release, and billing closure have all converged. Follow the returned operation or resource state until the billing state is terminal.