Creative teams often press Generate on several SKUs back-to-back. Rhinobird supports parallel work only up to the concurrency limit associated with your membership and the platform’s live rules. Unlike credit cost—which appears on each Generate click—concurrency is a plan attribute disclosed on the purchase page and preserved in your Order Snapshot when you buy Standard VIP or Premium VIP. Help center articles do not publish a universal number because tiers differ and limits may change with product updates.
What concurrency means here
Concurrency is how many AI generation tasks may execute at the same time for your account—not how many rows appear in History, and not how many browser tabs you open. Additional submissions beyond the limit may queue, fail fast with a message, or wait until an active job completes, depending on implementation. The authoritative cap for your account is whatever you agreed to at purchase, plus any platform-wide fairness controls applied for security or cost (Membership Services Agreement account management section).
Where to read your limit
- Open Pricing while signed in and compare Standard VIP versus Premium VIP feature lists.
- Review the membership purchase page text before checkout—concurrency appears alongside monthly Subscription Credits and Basic Benefits.
- Locate the Order Snapshot stored for your paid order if the membership center surfaces it.
- If tiers look identical on marketing copy but behavior differs, trust the Order Snapshot and purchase page over informal estimates.
Premium VIP is the advanced individual plan; Standard VIP is the basic individual plan. Enterprise workspaces, shared enterprise credits, and organization-wide licenses are not included in individual memberships unless the purchase page expressly says otherwise—teams should not infer higher concurrency from headcount alone.
Interaction with credits and devices
Concurrency does not multiply your monthly Subscription Credits. Five parallel video jobs each showing a large cost on Generate can exhaust a monthly allowance in hours. Monitor balance in signed-in account views and track completions in History.
Separately, the platform allows login on a reasonable number of personal devices and may set a maximum number of simultaneous device logins under published rules. That device policy protects accounts; it is related to—but not identical to—generation concurrency. Unusual login patterns may trigger verification or restriction measures.
Planning team workflows
Individual memberships are for one person or sole proprietor use—not centralized multi-user sharing. Agencies with parallel operators should assign separate accounts and plans or purchase enterprise offerings if listed on the purchase page. Sharing one login to bypass concurrency defeats audit trails and violates membership use restrictions.
Operational pattern: stagger heavy video renders, use smaller proof jobs to fill gaps while large jobs run, and upgrade tier at the next service cycle if Pricing shows a higher concurrency on Premium VIP that matches your throughput needs. Mid-cycle upgrades typically do not instantly rewrite current-cycle limits unless the purchase page promises immediate changes.
When jobs stall
If Generate spins without a new History row, check active jobs already processing. If nothing is running but submissions still block, sign out and back in via Login / Sign up, verify network stability, then contact support with timestamps if platform error is suspected. System-side failures may return credits under failed-task rules; queue saturation alone is not a billing error.
Concurrency is a plan feature—find yours on the purchase page and Order Snapshot, respect device and account-sharing rules, and scale official membership tier rather than sharing logins when producers routinely wait on the queue.