Credit System: Difference between revisions
| Line 67: | Line 67: | ||
=== See Also === | === See Also === | ||
[[ | [[Billing Model|Billing Model]] – architecture of subscriptions, payments, and invoices | ||
[[Subscription_Plans|Subscription Plans]] – price tiers, seat limits, and storage quotas | [[Subscription_Plans|Subscription Plans]] – price tiers, seat limits, and storage quotas | ||
Revision as of 12:12, 30 July 2025
Credit System
The ACT 3 Credit System lets every Template:ACT3 customer predict costs precisely and scale usage from a single test scene to a full-length series. Credits work like an in-app currency: each time you ask the platform to do heavy lifting—AI script generation, text-to-video rendering, 3-D set creation, text-to-speech, or up-scaling—the required number of Credits is debited from your organisation’s pooled balance.
Why Credits?
Transparent value – the exact Credit cost of an action is displayed on the button before you click Generate [40 Credits], so there are no billing surprises.
Granular control – teams can budget by task (e.g., draft-quality animatic vs. 4 K final render) instead of buying open-ended “minutes” or “tokens.”
Metered fairness – higher workloads simply consume more Credits; light users stay on lower plans without penalty.
Monthly Credit Allocation
Your active Subscription Plan loads a fresh bucket of Credits into the organisation on the renewal date:
| Plan !,! Monthly Credits !,! Rollover Bank Cap!
Free - Community - Standard - Business - Enterprise & above } † Enterprise-grade plans provide custom Credit ceilings negotiated with sales. Rollover & Bank RulesAuto-save: Unused Credits at month-end move into your Rollover Bank. Caps: Each plan’s bank holds up to its cap; excess Credits beyond that threshold expire. Spending order: Current-month Credits are consumed first; rollover Credits are tapped only when the fresh bucket hits zero. Consuming Credits
|
|---|