Plans, credits and billing
Customers buy credits. Every job reserves an estimate when it is queued and is charged what it really cost when it finishes — model calls and GPU seconds at cost, times the plan's markup. A held episode, or a failure on ChannelForge's side, is never charged. Plans add monthly credits and unlock limits and features; packs top up.
| Plan | Monthly | Yearly | Credits / month | Channels | Seats | Highlights |
|---|---|---|---|---|---|---|
| Trial | free | — | 400 (trial) | 2 | 1 | the basics |
| Creator | $49 | $490 | 600 | 6 | 2 | Studio, long-form |
| Pro | $149 | $1,490 | 2,000 | 24 | 6 | API, Studio, long-form |
| Agency | $449 | $4,490 | 6,500 | 100 | 20 | API, Studio, long-form, white label |
| Enterprise | custom | custom | custom | unlimited | unlimited | API, Studio, long-form, white label |
| Credit pack | Price | Per 100 credits |
|---|---|---|
| 500 credits | $55 | $11.00 |
| 1,500 credits | $150 | $10.00 |
| 5,000 credits | $450 | $9.00 |
| 15,000 credits | $1,200 | $8.00 |
Billing machinery#
Stripe (subscriptions, checkout, a customer portal of its own, upgrades charged pro rata, downgrades at the period end) and PayPal (subscriptions, refunds and disputes) are built in. Stripe's events are reconciled by polling its Events API, and a returning customer's checkout is applied at once, so a lost webhook can never lose a payment. Selling is behind a switch the owner turns on at launch; until then the free trial is open and the plan and pack catalogue waits in Stripe.
Since the first edition the plans and prices are unchanged, and the money tools around them have grown: credit codes, a time-boxed trial of a paid plan's tools, low-credit and expiry notices, a monthly credit budget per member, and for the operator finance and revenue pages, unit economics, the margin of every job kind and a worst-case break-even per plan. Receipts, promotions, local-currency prices, add-ons and automatic top-ups are built and wait for the launch of selling.