Predictable cost
Your bill is planned around the app profile before deploy, then stays tied to that profile as traffic changes.
Why Developers Choose Varity
Varity is built around one product property: your hosting bill is tied to the hardware your app reserves, not to traffic, bandwidth, invocations, or build minutes.
The Category Difference
Section titled “The Category Difference”Usage metered hosting charges more as more people use your app. Varity charges a fixed monthly price per app based on the hardware profile you reserve.
| Question | Usage metered hosting | Varity |
|---|---|---|
| What drives the bill? | Usage meters such as requests, bandwidth, invocations, storage, and build activity | The reserved resource profile, up to a monthly maximum prorated by running time |
| What happens during traffic spikes? | Billing follows the usage meters | An unchanged profile keeps the same monthly maximum |
| How do services affect cost? | Services are often separate products or meters | Attached services select their own preset and bill as separate reserved deployments |
| What should the builder think about? | Usage limits and add-on pricing | The workload profile and whether it fits the app |
Use Pricing and Costs for the current pricing workflow and cost calculator.
What This Means in Practice
Section titled “What This Means in Practice”Fast deploy path
Supported source projects and runnable images can deploy from the CLI, dashboard, or AI editor workflow.
Managed setup
Varity applies hosting defaults, runtime variables, credentials, and detected service wiring for the supported surface.
Clear boundaries
Unsupported source stacks, business critical data, and unreleased features are documented openly so teams can plan around the beta.
When Varity Is a Good Fit
Section titled “When Varity Is a Good Fit”- You want a live app URL without building infrastructure around a supported stack
- You are deploying an app from an AI coding tool and want the deploy flow in the same workspace
- You have a runnable Docker or OCI HTTP service image
- You want the bill to be based on the app profile instead of usage meters
- You are building with supported services such as Postgres, Redis, MongoDB, MySQL, object storage, or model runtime support
When to Pause
Section titled “When to Pause”Varity may not be the right fit yet if you need cron jobs, preview deployments, one click rollback, or a source build for Rust, Ruby, Elixir, Java, Deno, PHP, or .NET.
Those unsupported source stacks can still deploy when packaged as runnable Docker or OCI HTTP service images.