> For the complete documentation index, see [llms.txt](https://help.intangible.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.intangible.ai/teams-and-billing/plans-and-billing.md). # Plans and billing Free, Explorer, Business plans. Payment methods, multiple owners, credit packs, annual discounts. Four tiers: Free, Explorer, Business, Enterprise. Free for trial. Explorer for individual creators. Business for teams with credit pooling. Enterprise for custom-fit engagements at scale. The current pricing matrix lives at [intangible.ai/pricing](https://www.intangible.ai/pricing); this page covers the conceptual differences and how billing works. ![Subscription tab on the Team Admin page showing the four-tier comparison: Free $0, Explorer $35, Business $65 (subscribed), Enterprise Custom](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-db591116d44ebb3a2eb1acf64ddaf44737815ab9%2Fsubscription-tab-01.png?alt=media) ## Plan comparison The authoritative, up-to-date per-feature matrix lives at [intangible.ai/pricing](https://www.intangible.ai/pricing). It changes faster than these docs can, so the comparison isn't duplicated here. A few durable shape points: Free is for trial. Explorer is single-seat. Business adds multi-seat team workspaces with credit pooling. Enterprise is custom scope. Generate 3D Asset isn't available on Free; upgrading to Explorer or Business unlocks it. ## The four tiers ### Free The trial tier. Includes: * Enough credits to render a few dozen 1K image stills. * Single user, personal workspace only. * All three modes (Build, Compose, Visualize) and most features. * No Generate 3D Asset (requires Explorer or Business). * No multi-seat teams. * No team workspaces. Use Free to walk through [the first render in 20 minutes](/overview/get-started/first-render-in-20-minutes.md) and try the product before committing. ### Explorer The individual creator tier. Includes everything in Free plus: * More credits per cycle. * Full Generate 3D Asset capability. * No multi-seat teams. Right for solo agency creatives, freelancers, and creators producing client work without a team. ### Business The team tier. Includes everything in Explorer plus: * Multi-seat team workspaces with collaboration and credit pooling across the team. * [Generate 3D Asset](/build/generate-3d-asset.md) (text/image/multi-view to mesh). * Higher per-cycle credit allotments. * Multiple billing owners and payment methods. * Priority support. ### Enterprise The custom tier for teams at scale. Pricing and feature scope handled directly with the Intangible team. Adds set design support, custom configuration and development engagements, and the elastic scaling that larger production pipelines need. Contact the Intangible team via the **Contact Us** action on the in-product subscription page or through your account contact. Required for any multi-user collaboration. The pricing scales per seat. ## Billing cycles Two options: * **Monthly** – billed each month, can cancel any month. * **Annual** – billed once a year at a discount versus monthly, with a 14-day trial period. The exact discount varies; see [intangible.ai/pricing](https://www.intangible.ai/pricing) for current figures. Annual is the right call when you know you're committing to the product for a quarter or more. The 14-day trial gives you time to confirm the team workflow works for you before the annual hits. ### How the 14-day trial maps to the annual cycle The trial is **prepended** to the annual cycle, not consumed from it. Mechanics: * The 14-day countdown starts at checkout. * During the trial the subscription status is `trialing` and no invoice is generated. * On day 15 the trial ends, Stripe generates the first invoice automatically, and the paid annual year begins. Example: sign up for an annual plan with a 14-day trial on January 1st. The paid year runs from approximately January 15th to January 15th of the following year. The trial is free time before the paid year, not days deducted from 365. ## Where billing lives in the app Three tabs at the top of the **Team Admin** page (`studio.intangible.ai/team/...`): * **Team** – members, roles, invites. * **Subscription** – tier picker (Free / Explorer / Business / Enterprise) with the Monthly / Annual toggle. * **Usage** – current cycle's credit balance, Purchased Credits balance, billing entry point. The Usage tab is the in-product summary. Billing itself runs in Stripe – the page exposes a **Manage billing in Stripe** action that opens the Stripe customer portal in a new tab for invoice history, card management, and downloads. ![Team Admin Usage tab showing Monthly Credits (0 / 1000), a Purchased Credits balance of 562, and the Manage billing in Stripe action](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-eb7f498423f83caed6ab1716fc82d924a4c6db86%2Fusage-tab-02.png?alt=media) ### Monthly Credits Each cycle, the tier's allotment refills the Monthly Credits balance. **Monthly credits do not roll over.** The balance is capped at the monthly allocation, so an unspent month is not carried into the next one. The Usage tab shows current usage as a progress bar (e.g. "0/1000") and the refill date in prose ("Your monthly credit balance will refill January 9 based on your business plan."). Unspent monthly credits don't roll over – use them or lose them at the cycle boundary. ### Purchased Credits Top-ups bought via the Get Credits flow add to a separate balance. Purchased credits **expire one year after purchase**. They survive the monthly cycle, which monthly credits do not, but they are not permanent. Monthly credits draw down first; purchased credits are spent only after the monthly bucket is empty. ## Reading the Usage page The balance tells you what's left. The Usage page tells you where it went, which is the number you need when a project burns a month's credits in a week and nobody can say why. There are two of these, and which one answers your question depends on whose spend you're chasing. **Your own spend: My usage.** Open the profile menu at the top right and choose **Usage**. It shows what *you* have spent inside the team currently selected in the workspace switcher, so check the switcher first if the numbers look wrong. Every member has this. ![The profile menu at the top right, with Usage below Profile and Settings](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-7faf57b3e940b39d35065511f0f2f1144ad592ad%2Fusage-profile-menu-01.png?alt=media) **The whole team's spend: the Usage tab on Team Admin.** Open the team menu at the bottom left of the rail, then the **Usage** tab. You need to administer the team space to see it. ![Team usage: active members, projects, and credits per generation, with the By member breakdown below](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-28c93201094aa3d97f1f5b935457f1a4e4468b0e%2Fteam-usage-by-member-01.png?alt=media) The team view answers a different question from your own. Its headline cards are **Active members**, **Projects**, and **Credits / generation**, and the **By member** table shows who spent what, with a last-activity date. Click a member to open their own breakdown, the same shape as My usage but scoped to them. Across the top, four filters set the window: **7D**, **30D**, **90D**, and **All time**. Both views break the spend down the same way: * **By category.** A donut of net credits used, split across Video, Image, and 3D. This is the first place to look. Video is almost always the largest slice, and a category that's larger than you expected usually means someone is generating video where a still would have answered the question. * **By headline number.** Three cards: **Generations**, **Projects**, and **Credits / generation**. The third is the useful one over time. A rising cost-per-generation means the team has drifted to more expensive models or higher resolutions. * **By project.** Which projects consumed the credits. * **By transaction.** A **Recent activity** table listing each charge with its date, what it was used for (Image generation, Video generation, 3D generation, Image edit), the project it belongs to, the type, and the credit amount. Page through it with the Previous and Next controls. Two panels report the balances themselves: **Monthly Credits** with the refill date and the plan allowance, and **Purchased Credits**, which are bought as credit packs and expire a year after purchase. {% hint style="info" %} If your team has Enterprise terms with Intangible, those terms supersede what this panel shows. {% endhint %} {% hint style="info" %} A dash in the Project column means the charge has no project attached. That covers work done outside a project, and older charges from before spend was attributed at the point of the transaction. An unnamed project shows as "Untitled" with its project id rather than being merged with other untitled projects. {% endhint %} ## Payment methods Card management lives in Stripe via **Manage billing in Stripe** on the Usage tab. Adding or updating a card requires Owner permission; see [Permissions](/teams-and-billing/permissions.md). ## Auto top-up Credit packs can buy themselves. Turn on auto top-up and pick which pack it should buy; when the balance runs low, that pack is purchased automatically so a render doesn't fail mid-session. Two settings, both on the billing surface: **on or off**, and **which pack**. Picking a pack is required to enable it. The trigger is not configurable. Auto top-up fires when your remaining credits fall below **20% of your total ceiling**, where the ceiling is your monthly allowance multiplied by your seat count, plus any purchased credits you still hold. Counting both buckets is deliberate: a team with monthly allowance still to spend has runway that a pack-only calculation would miss. {% hint style="warning" %} After **five consecutive failed charges**, auto top-up switches itself off and the team is alerted. That is almost always an expired or declined card. Fix the card in Stripe, then turn auto top-up back on; it does not re-enable itself. {% endhint %} ## Credit packs When the monthly allotment runs short on a heavy project, a credit pack tops up without changing your tier. Purchased from the same billing settings panel: 1. **Open Get Credits** from the Usage tab. The Buy Packs modal appears with the pack tiles. 2. **Pick a pack size.** Each tile shows the credit count for one pack at its base price. 3. **Set the quantity.** Each tile has a stepper (1–10) so you can buy multiple of the same pack in a single transaction. The buy button label multiplies the credits and updates live: a quantity of 2 on a 5,000-credit pack reads **Buy 10,000 credits**. 4. **Click Buy.** Stripe Checkout opens; complete the payment. 5. **Credits land on completion.** Granted credits scale automatically with the chosen quantity. The workspace balance updates as soon as the Stripe webhook fires. Credit packs persist beyond the monthly cycle: they are not cleared when it rolls over. They do expire one year after purchase. The cycle's allotment fills up first; pack credits get used after the cycle's allotment runs out. Larger pack sizes give a discount per credit, and multiplying the quantity stacks the same per-credit rate. Useful when a campaign is about to start and you know you'll need a substantial budget over the next month. {% hint style="info" %} Credit packs are workspace-scoped. A pack purchased on a personal workspace doesn't subsidize a team workspace and vice-versa. Buy on the workspace where the spend will happen. {% endhint %} ## Upgrades and downgrades * **Upgrade**: takes effect immediately. The new tier's monthly allotment becomes available at the next cycle; new tier features unlock immediately. * **Downgrade**: takes effect at the next billing cycle. The current cycle keeps the higher tier's features until it ends. Tier-gated features stop working at the cycle change. Monthly credits don't accumulate across cycles. Whatever credit balance you have at downgrade is preserved into the new tier; only the per-cycle refill rate changes. Downgrading from Business to a lower tier with active team workspaces: the team workspaces remain accessible to existing members, but no new invites can be sent until you re-upgrade. ## Limits and known issues * **Plan changes don't refund partial cycles** for downgrades. If you downgrade mid-month, the remaining time on the higher tier is honored but no refund is issued. * **Credit-pack pricing per credit varies** by pack size. Larger packs are cheaper per credit. The bulk flow surfaces the actual rate before purchase. ## Related * [Workspaces](/teams-and-billing/workspaces.md) * [Create and invite](/teams-and-billing/create-and-invite.md) * [Permissions](/teams-and-billing/permissions.md) * [Credits and tokens](/overview/concepts/credits-and-tokens.md) * [Resolution and cost](/visualize/resolution-and-cost.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.intangible.ai/teams-and-billing/plans-and-billing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.