Start with a free workflow, move to Pro for regular processing, and use Business when auditability, quotas and team operations matter.
Plan codes and monthly prices are aligned with the backend /api/v1/plans catalog.
For validating the workflow and testing media processing.
Basic quotas
Local testing, product validation and light usage.
No billing required
For creators and solo operators with regular media processing.
Higher monthly limits
Regular download, transcription and media asset workflows.
Yearly billing foundation ready
For teams that need compliance-oriented media workflows.
Team-ready limits
Audit-heavy workflows, larger quotas and team operations.
Annual contracts can be added later
These limits come from the backend plan catalog and should remain aligned with /api/v1/plans.
| Plan | Storage | Transcription | Jobs | Price |
|---|---|---|---|---|
| Freefree | 10 GB | 36,000 sec | 500 jobs | $0 / forever |
| Propro | 100 GB | 144,000 sec | 5,000 jobs | $12 / per month |
| Businessbusiness | 500 GB | 720,000 sec | 20,000 jobs | $49 / per month |
The table below explains the commercial packaging of the same technical product foundation.
| Feature | Free | Pro | Business |
|---|---|---|---|
| Media downloads | Basic | Higher quota | Team scale |
| Transcription | Limited | Regular usage | High volume |
| Media asset library | Basic | Included | Included |
| Audit logs | Security baseline | Security baseline | Audit-ready |
| Privacy requests | Included | Included | Included |
| Billing overview | Basic | Included | Included |
| Admin/team layer | No | Roadmap | Roadmap priority |
Short answers for plan selection, quotas, billing readiness and future annual pricing.
Yes. The public pricing surface is aligned with the backend plan catalog: free, pro and business.
Not yet. Stage 3.5.1 adds the UI foundation for monthly/yearly switching, but backend annual pricing should be added in a later billing stage.
The quota values shown here match the current backend plans table and /api/v1/plans response.
No. Current CTAs pass plan codes into registration or billing flows. Payment provider integration is a later stage.
Choose a plan code now. Payment provider integration can be added after the pricing surface is validated.