Repository navigation
docs(studio-app): cloud exports come with the plan, not only an API key - #7441
Conversation
The export page said cloud renders are always paid per minute from a HeyGen API balance. The app now includes 5 cloud exports a month on Free and unlimited on Pro (plans.ts, cloudFit.mjs).
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
jrusso1020
left a comment
There was a problem hiding this comment.
Reviewed at f76d06f765a396110ec99376b4647c438311e3b9.
Looks good overall; no blocker found. The app's plan definitions specify five Free cloud exports per month and unlimited Pro cloud exports, matching the live pricing page checked on 2026-11-09. Export's plan-paid branch says “Included in your plan”; the API-key-paid branch shows per-minute pricing. The change correctly removes the claim that every cloud export requires API balance.
Nit — docs/studio-app/export.mdx:24 and :30: qualify the destination and payer wording. Export remembers a previous destination; Cloud is the Pro default when no destination was saved. Also, saving a key does not necessarily override an eligible plan: per-minute billing applies when the render actually uses the API key. Suggested wording: “On Pro, Cloud is the default unless you've previously selected another destination” and “When paid through your HeyGen API key, cloud renders are billed per minute from your API balance.”
Verification: gh pr diff 7441, complete page read, and source trace through the current app's plan definitions, Export destination/payer presentation and payer selection. No runtime render, billing transaction or UI walkthrough performed. No route, navigation or frontmatter changes.
Need: yes · Size: ok · Reuse: existing app plan and Export copy · Simpler: already minimal · Structure: fine (checked the existing cost table; no split)
Risk: low — documentation only; allowances agree with app source and public pricing.
— Rames / Codex
Verdict: COMMENT — looks good with a wording nit.
Reasoning: The corrected allowances are supported by source and public pricing; the two qualifications would make the default and API-key cases more precise.
jrusso1020
left a comment
There was a problem hiding this comment.
Reviewed at 8955fd2a084fcba11ace1e17e6fdf88be9cd8011. Looks good; no remaining blocker or wording nit.
The delta from my previous review changes only docs/studio-app/export.mdx:24–30. It now qualifies Cloud as the Pro default unless another destination was selected, and ties API-balance/per-minute billing to renders actually paid through the key. Both qualifications address my prior nit and match the destination/payer behavior traced in the first review.
Verification: GitHub compare from f76d06f7 to this head (one commit, one docs file), complete page read, and re-read of the retained destination/payer source evidence from the prior review. No runtime tests or billing actions for this text-only delta. Frontmatter, links and navigation are unchanged.
Need: yes · Size: ok · Reuse: existing Export destination/payer terminology · Simpler: already minimal · Structure: fine (checked existing paragraph and cost table; no split)
Risk: low — wording-only clarification.
— Rames / hf-review
Verdict: COMMENT — no blocker.
Reasoning: The revised wording resolves both qualifications without changing the previously verified plan allowances.
…n (upstream heygen-com#7441, heygen-com#7440) Applies upstream 756bd6b (heygen-com#7441) and b12365d (heygen-com#7440), both by Ular Kimsanov, unchanged: the Export page now says cloud exports are included in the plan (5 a month on Free, unlimited on Pro) and a saved HeyGen API key pays when billed per minute, and the Reference page says Pro credits pay for the read with a saved key as the fallback. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…nce watermark Seventeen commits, PRs 7469-7493, issues 7473 and 7486 and twelve pin moves are recorded with their evidence in the continued ledger, DECISIONS, UPSTREAM and ROADMAP. Adopted: heygen-com#7466, heygen-com#7479, heygen-com#7482, heygen-com#7490 and the heygen-com#7441 and heygen-com#7440 docs. Deferred: heygen-com#7469, heygen-com#7471, heygen-com#7476, heygen-com#7480, heygen-com#7468, heygen-com#7487, heygen-com#7491. Not applicable: heygen-com#7470, heygen-com#7351, heygen-com#7475, heygen-com#7483. The watermark moves to 61e720b, PR heygen-com#7493, issue heygen-com#7486; thirteen new PRs are pinned. FORK.md records the subComposition test differences. The core packed-size roadmap row trigger is not met. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
What
The Export page (/studio-app/export) now says cloud exports are included in your HyperFrames plan: 5 a month on Free, unlimited on Pro (where Export starts on Cloud). Paying per minute from a HeyGen API balance stays, as the option for people with a saved key.
Why
The page said every cloud render is paid per minute from an API balance. The app and the pricing page say otherwise, so the docs told Free users they'd pay for something that's included. Our new "free AI video editor" page found the clash.
How
Docs text only, one file.
Test plan
What I measured (6 Nov 2026, the Studio app's source and the live app):
What I did NOT exercise: a Free account running out of its 5 cloud exports (the copy comes from plans.ts and the e2e capture cloud-free-used-up).
How we'll know it worked: no more "do cloud exports cost money on Free?" questions in the docs assistant logs for this page.