Browse docs
Docs/Billing
Billing

Open Vassal Pricing

Understand hosted agent pricing, workspace add-ons, and when organization pricing makes sense.

Last updated April 9, 2026

What you are paying for

Open Vassal pricing is about hosted runtime capacity, persistent storage, and the operational layer around each agent.

You are not just paying for raw compute. You are paying for a managed hosted setup that keeps the agent usable inside a product instead of an improvised infrastructure stack.

When to stay small

Use the smaller plan when the agent handles lighter workflows, smaller workspaces, or a more focused operating scope.

This is the right default when the agent is still proving itself or when the workload is clearly bounded.

When to move up

Move up when the work is heavier, the workspace is larger, or the agent is becoming operationally important enough that more headroom is worth the cost.

It is usually better to upgrade because the workload demands it, not because the setup feels incomplete without the larger plan.

Another good signal is whether the agent is becoming part of a reliable recurring workflow. At that point, smoother operation often matters more than squeezing every dollar out of the smallest configuration.

The right plan is the one that keeps the workload moving without turning routine tasks into infrastructure babysitting.

How billing should feel

Good billing structure should make the hosted agent easier to reason about, not harder. You should be able to look at the runtime plan, workspace add-ons, and organization subscription and understand why they exist.

If a pricing choice feels arbitrary, it is usually a sign that the workflow or ownership model still needs to be clarified.

Related guides