Platform
Billing & Plans
Understand how Banata plans are enforced, which usage metrics matter most, and how to build customer-facing warnings and upgrade flows around them.
Banata plans are mainly about two things:
- how many sandboxes you can have active at once
- how much sandbox usage you can consume over the month
The main value metrics
The most important plan controls are:
- concurrent sandboxes
- monthly sandbox-hours
Some higher-tier features may also be gated, such as:
- browser recording
- controlled outbound routing
How limits are enforced
Limits are enforced on sandbox create and resume.
That means:
- if you are already at your concurrency cap, more active sandboxes will be rejected
- if you have already used your sandbox-hour allowance, more work will be rejected until the billing period resets or the plan changes
Usage endpoints
ts
const usage = await client.getUsage();
const billing = await client.getBilling();Use them to:
- show usage inside your app
- warn customers before they hit a limit
- explain why a request failed
Good product advice
If you are building on Banata:
- warn before the limit, not only after it
- prefer async jobs plus webhooks for long work
- end idle sandboxes when the job is complete
Checkout
If you use Banata-hosted checkout:
ts
const checkout = await client.createCheckout({ plan: "pro" });