Plans & Usage
Azent uses a usage-based billing model with plan-based limits on concurrent runs and agent hours.
SaaS plans
| Plan | Price | Agent hours | Concurrent runs |
|---|---|---|---|
| Starter | $49/mo | 10 hours | 1 |
| Team | $199/mo | 50 hours | 3 |
| Business | $599/mo | 200 hours | 8 |
| Enterprise | Custom | Custom | Custom |
Self-hosted plans
| Plan | Price | Agent hours | Concurrent runs |
|---|---|---|---|
| Standard | $9,990/yr | Unlimited | 3 |
| Enterprise | Custom | Unlimited | Custom |
How agent hours are counted
Agent hours are measured from when the worker starts processing a request to when it completes. Queue wait time is not counted. The billing period resets monthly based on your subscription anniversary date.
Viewing usage
Reached via the Plan OK badge in the Dashboard header. Shows your subscription, plan limits, and current usage in detail.
- •Subscription — plan name, billing contact, validity dates, and a Manage subscription link to the billing portal.
- •Plan limits — the hard caps that apply to this workspace.
- •Concurrent runs — how many agents are working right now versus the cap. When you hit the cap, new runs queue instead of starting.
- •Agent hours — billable processing time used this period (queue wait isn't counted). The period resets on your billing anniversary.
Limits enforcement
When limits are reached:
- •Concurrent runs limit: New requests are queued and will start when a running slot becomes available
- •Agent hours exhausted: New requests are blocked until the billing period resets (SaaS only — self-hosted has unlimited hours)