Billing at Bookbag
Plans are bought and changed at Bookbag, once, for every Bookbag product. What Madebook reads from there, what it enforces itself, and what the Billing page shows.
Madebook does not take payments. An organization's seats, its plan for each Bookbag product, its trial and its bill live at Bookbag — one Stripe customer, one subscription, one seat number shared by every product. Madebook holds no Stripe key, no price, no subscription and no billing table. It reads the organization's entitlement from Bookbag and enforces its own limits from it.
So there is no admin page for Stripe here, no revenue page, and no "Upgrade" button that charges anything. Every upgrade link in Madebook opens the organization's Billing page at Bookbag.
The plans
| Plan | Workspaces | Repository connections | Also |
|---|---|---|---|
| Free | 1 | 1 (the bundled sample repository does not count) | Unlimited viewers |
| Pro | unlimited | unlimited | Every coding agent governed, the approval and audit record, the AI features on the included allowance |
| Business | unlimited | unlimited | Pro, plus the signed audit export and priority support |
Prices are per seat and are shown at Bookbag, never here. Viewers are free on every plan: they use no seat, and the seat count on the Billing page leaves them out.
Nothing already made is removed when a plan changes. An organization that is over a limit — two workspaces, say, after a plan ended — keeps what it has and cannot add more until it upgrades.
What Madebook enforces
The limits above are Madebook's to enforce, and it does so at the moment something would be created:
- a second workspace on Free — on New workspace, Start from a repository, and when a sibling product (CodeBook) creates the workspace here through its own link;
- a second repository connection on Free — on the workspace's Repositories page and on Start from a repository, whichever host the repository comes from. Connecting the bundled sample is always allowed;
- a signed audit export on Free or Pro — a Business feature.
The refusal says so in plain words and links to the Billing page at Bookbag:
The Free plan allows 1 repository connection (the bundled sample does not count); this organization already has 1 repository connection. Upgrade on the organization's Billing page at Bookbag.
Over the API every such refusal has one shape, the same one every Bookbag product uses, so a refusal a sibling product sends back is shown the same way:
{ "data": false, "code": "PLAN_LIMIT", "error": "…",
"gate": { "feature": "repositories", "plan": "free", "limit": 1, "used": 1, "manage_url": "https://sso.bookbag.ai/user/organizations/…/billing" } }
Nothing else in Madebook is gated by plan today. Policy packs and retention by plan are not built; when they are, they join this list.
The Billing page
Organization → Billing is read-only. It shows Bookbag's answer as it is:
- the plan, and why — Bookbag's own sentence, verbatim: "Paid subscription, renews 28 Nov 2026.", "Trial of Business, ends 2 Nov 2026.", "No subscription; the Free plan applies." It says ends when the subscription is set to end and renews otherwise, in the organization's time zone;
- seats used of seats — "5 of 7 seats used — viewers are always free." A Free organization has no seat number;
- the other Bookbag products paid for by the same seats — one bill for all of them;
- the AI allowance the seats bring, used of the month's pool, when the organization is on a paid plan;
- what each plan allows in Madebook, and which one is current;
- Change plan or seats, which opens the organization's Billing page at Bookbag. Owners and admins can read the page here; what they may change is decided at Bookbag.
Reaching the page asks Bookbag afresh, so landing back on it after buying shows the new plan at once.
When Bookbag cannot be reached
Billing reads never block a paying customer. Madebook keeps each organization's answer for an hour, and Bookbag tells it the moment anything changes — a purchase, more seats, a tier, a comp, a trial or a subscription ending — so a limit lifts within seconds of paying. If Bookbag cannot be reached, the last answer stands for up to another hour; with no answer at all, the action is allowed and the fact is logged, and the Billing page says the plan is not known right now.
A paying customer blocked by an outage is worse than one extra free workspace.
For platform administrators
There is nothing to configure in Madebook. The Stripe key, the webhook, the prices, free mode and complimentary plans are all on Bookbag's own admin billing page, once, for every product. The admin Overview counts the work this deployment holds; it no longer shows paying organizations, trials or revenue, because those are Bookbag's numbers.
Related
- Organizations — what Madebook holds about an organization, and what Bookbag holds.
- Roles and permissions — who may read the Billing page.
- The platform admin area