Settings › Plan is the project's commercial home, in four tabs.
Plan#
The current tier and its limits, with upgrade and cancellation through the embedded shop. Paid tiers unlock the developer features (hooks, tokens, identities, secrets), custom domains, and include a weekly allowance of AI credits.
The plan catalog takes a coupon: enter a code above the cards and the visible plans show their discounted prices; picking a plan carries the code into checkout, where it can still be changed or removed before payment.
Required plan#
When the platform team builds a project's web setup, they can mark the plan it was built against as required. Until the project subscribes to that plan (or a higher one), the plan is highlighted on the Overview, in the side pane and in the header chip, the Plan tab shows the required plan, the date to subscribe by and the coupon that applies, and the shop lists only that plan and above with the coupon already applied. The due date is informative — nothing is locked when it passes.
Granted plan#
The platform team can also grant a project a plan without a subscription — for contract clients, or as a bridge while a required plan is still to be subscribed (the required-plan editor offers the grant in the same step). A granted project runs on the higher of its subscription and the grant everywhere the plan matters: the weekly credit allowance, the developer features and custom domains, and the plan card, which then reads Granted by platform with the end date. A granted plan is the platform's arrangement: the project's members cannot change it themselves — the shop and the upgrade button are hidden and the card reads This plan is managed by the platform — and only a platform admin stops it (Stop plan). The one exception is a pending required plan, which the grant bridges: the shop stays open so the project can subscribe to it. A grant never counts as subscribing: a required plan stays highlighted until the project pays. Past its end date the grant falls away by itself.
Paying by invoice#
How a granted plan is paid is set in the same step: none (the platform invoices nothing), invoice (bank transfer) or custom (invoiced outside the platform — a note for the team). For invoice the platform team enters one or more invoice e-mail addresses, the billing address, the invoicing period — monthly or yearly — the day invoicing starts (today, or a later day) and the price, prefilled from the plan's list price for that period and editable for a contract price. Each period is invoiced in advance on its first day: the first one on the start day (right away when invoicing starts today), the next ones every month or year from that day. The project receives an e-mail with a proforma invoice (an advance document, not a tax document) — the bank account, variable symbol, due date (14 days) and a QR Platba code that any Czech banking app scans to fill in the payment. The same payment block and QR code are on the proforma itself (web and PDF). Once the transfer arrives and is paired, the order is completed, the final invoice (the tax document) is issued and e-mailed to the same addresses right away, and the plan card's list shows the invoice number with a Paid chip; until then the list shows the proforma number. The e-mails come in the language chosen on the card (Czech or English). A proforma left unpaid well past its due date is cancelled and the order closed; its row then reads Closed unpaid. The plan card reads Paid by monthly invoice; a project that still has a card subscription is not invoiced until it is cancelled. Stopping the plan drops the payment arrangement with it.
Where the platform issues its invoices through Fakturoid, the same step links the project to one contact of the platform's Fakturoid account — picked by name, or created from the company's IČO / DIČ with the name and address filled from the ARES register — so every proforma and invoice is issued on that contact, with Fakturoid's own numbers, web documents and bank pairing: a transfer paired in Fakturoid marks the period Paid in the list on the plan card, Fakturoid issues the final invoice on the proforma's payment, and the e-mails link the web documents.
Credits#
The project's AI wallet — what the Studio and the assistants debit per turn and what the gen API debits per call. Top up here (1 credit = $0.01 by convention); the balance and ledger are also readable through the Promo routes. One wallet per project, always on Production — a Demo session spends the same wallet.
Pricing#
The rate card: the fixed prices of the gen/* routes, and Assistant models — every model the Assistant offers (Gemini Flash / Pro / Argon, Claude Sonnet / Opus / Fable) with its rate in credits per 1M tokens for input, cached input and output, a second row for long prompts where a model prices them higher, the date and rates of a scheduled price change, and the per-image price of the image models. Every Assistant turn is charged by the tokens it used on the model you picked, at these rates.
Logs#
The generative request log — every metered call with its cost, model and status.
Plan is manager-only; the other tabs open to managers and to members with the generative capability.