← Back to docs

Sense each account's quota in real time and route by remaining quota, rate and priority (quota balancing), with seamless failover before limits hit.

Quota balancing — smart routing that dodges rate limits

Quota balancing makes every credit in your account pool count. Dawvia senses each account's remaining quota in real time, routes requests by remaining quota, rate and priority, and switches to a standby account seamlessly before a limit is hit — turning "rate limit means outage" into "rate limit means switch".

What does balancing solve?

Single-account AI coding fears two things: rate-limit outages and wasted quota. Balancing solves both:

  • Dodge rate limits: switch away before quota runs out, so requests don't fail when one

account is throttled.

  • Use every credit: send load to accounts with headroom, avoiding "one maxed, the rest idle".
  • Protect accounts: threshold alerts and cooldown policies keep any single account from

being overrun.

How does routing decide?

Once a request enters the unified entry, the balancer scores accounts on several signals:

  1. Remaining quota: prefer accounts with more headroom.
  2. Rate & latency: avoid accounts that are throttled or slowing down.
  3. Priority: bias resources by team or task priority.
  4. Cooldown: recently limited accounts cool down and sit out routing.
# Set a policy: quota-first, cool down under 15% remaining
dawvia balance policy set --strategy quota-first --cooldown-threshold 15

# Watch routing and switches live
dawvia balance watch

How does seamless failover work?

When an account hits a limit or errors, the balancer switches to a standby account with no caller-visible interruption:

  • The hand-off completes within the request lifecycle — no manual intervention.
  • Every switch is audited, replayable and reviewable (see Remote console).
  • Paired with Autopilot orchestration, the whole pipeline self-heals.
Tip: balancing works over accounts in your account pool, so connect accounts first.

What does the full orchestration picture look like?

A call's lifecycle is "trigger → smart routing → failover → audit". The four stages are detailed on the features overview and in Autopilot orchestration.

Which plans include quota balancing?

Smart quota balancing starts on Pro; enterprise governance and usage insights start on Team. Compare on the features overview and the pricing page.