Predictable cost
Your bill is planned around the app profile before deploy, then stays tied to that profile as traffic changes.
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.
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? | Requests, bandwidth, invocations, storage, add ons, and build activity | Reserved hardware profile |
| What happens during traffic spikes? | The bill can grow with usage | The app keeps the same monthly profile |
| How do services affect cost? | Services are often separate products or meters | Supported services are attached as part of the deployment profile |
| What should the builder think about? | Usage limits, surprise overages, 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.
Predictable cost
Your bill is planned around the app profile before deploy, then stays tied to that profile as traffic changes.
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.
Varity may not be the right fit yet if you need external custom domains today, cron jobs, preview deployments, one click rollback, dedicated GPUs for your own containers, 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.