Credits are granted to the workspace that starts checkout, not to an individual seat.
Pricing
Subscribe for monthly Flares. Top up when a launch week burns hotter than planned.
Billing is workspace-based. Stripe handles payment, then Zingflare grants Flares to the active workspace so teams can spend one pooled balance across generation and export jobs.
Plans and top-ups are fixed products. Task pricing stays inside the app and is quoted before compute runs.
Subscriptions cover recurring usage. Top-ups absorb burst traffic without forcing an immediate plan change.
Subscriptions
Monthly plans
Start with a recurring workspace balance, then layer top-ups on top when demand spikes.
Creator
For solo workflows shipping short-form launch edits and quick concept rounds.
Monthly Flares renew automatically and land in the active workspace after payment succeeds.
Choose CreatorPro
For teams iterating on more campaigns, more revisions, and heavier generation volume.
Balanced monthly pool for recurring production without managing constant one-off purchases.
Choose ProTeam
For shared workspaces that need a pooled balance for sustained production throughput.
Large monthly allocation for multi-user teams running generation and export jobs every week.
Choose TeamTop-ups
Add more Flares without changing plans
Useful for campaign bursts, re-renders, or heavy experimentation windows.
Checkout flow
One hosted payment flow, one internal usage ledger.
The public site sends people into the authenticated app checkout route. Stripe Checkout handles payment, then the Zingflare webhook grants the purchased Flares to the active workspace wallet.
Task pricing
Compute costs stay flexible.
Generation and render jobs can cost different numbers of Flares depending on model and workload. Those prices are quoted in-app before a task starts, so the public Stripe catalog stays simple even when internal pricing changes.