Pricing

No. Graph editing, local nodes, palette work, masks, the compositor, cached results and ordinary project work do not spend Oro Balance.

Personal supported provider keys are available only on Oro API or custom Enterprise plans. Starter, Base, Pro and Team do not permit personal provider keys.

The canvas and local tools keep working, and BYOK remains available for select plans. Only a managed run that needs more Oro Balance is paused. Starter waits for its next monthly reset before another managed run can use included Balance. Starter has no top-ups and no personal provider-key fallback.

Oro API and Base reset each month with no rollover. Each Pro included-credit grant expires three calendar months after its own grant date. Pro has no separate included-credit balance cap. Existing grants keep their original expiry dates. Team credits roll over for up to three months, capped at three times the plan’s monthly credits. If a renewal payment is missed, paid-plan access continues for seven days. After that, unused included credits are frozen until you renew, while their original expiry dates continue to apply. A confirmed paid renewal makes only unexpired included credits available again. Unfreezing those credits does not extend their expiry, restore expired credits or add a second grant. Purchased credits stay separate, keep their original twelve-calendar-month expiry and survive plan changes. Credits reserved for active runs remain protected.

Our top-up is $10 for 1,000 purchased credits on Oro API, Base, Pro and Team. Purchased credits remain distinct from monthly credits, survive plan changes and expire 12 months after purchase.

Each Team seat contributes 1,500 monthly credits to one shared organization pool. Administrators can set default and member-specific spending limits against that pool. Those limits do not transfer credits into personal wallets.