What is an active product
A product becomes active in ProductOS once it has a live domain, backend, or app store release. Until then, it is a draft and does not count against your product allowance. A product is a digital experience for your end users. It has a name, a design system, a codebase, a backend, and one or more delivery channels.Product identity and lineage
A product retains its identity and full history across:- A fork or clone
- A new GitHub repository
- A new domain
- A transfer to another workspace
Channels
A channel is a delivery surface for your product. The same product identity can be delivered across multiple channels, all sharing the design system, backend, context, and code.
Paid plans include the web production channel. Hobby includes a branded draft preview but not a production deployment. Mobile and desktop are add-ons in most paid plans. Founder includes one mobile release channel.
Channel pricing
Channels are billed per product. If you have three active products and add a mobile channel to all three, you pay $29 times three, or $87 per month.
Adding a channel
Adding a channel updates the product entitlement after checkout confirmation. Monthly workspaces charge the prorated add-on immediately; annual workspaces record the prorated obligation for the annual true-up.Founder mobile channel
Founder includes one mobile release channel. This means you can add mobile release operations to one product without paying the add-on fee. Additional products or additional channels are billed at the standard add-on rate.Monthly billing
Published self-service plans bill monthly by default. You pay for the plan and active add-ons on the workspace billing date. Enterprise terms are defined in the executed order.Annual billing
Annual billing is priced at 10 times the monthly price and charged once per year. You pay the full annual amount upfront and receive two months included compared with paying monthly for a full year. The displayed monthly equivalent is rounded to the nearest dollar. The annual total is exact.
Annual billing is available on published paid plans. Contracted mid-year additions are tracked as true-ups under the workspace’s order terms.
License additions and reductions
Adding a license
Adding a User or Collaborator License creates a prorated obligation for the remainder of the current term. Monthly workspaces charge that addition immediately; annual workspaces record it for the annual true-up. After renewal, the license is billed for the full term.Removing a license
Removing a license takes effect at your next renewal. Your team keeps access through the end of what you already paid for. You do not lose the value of the paid term.Released licenses
A paid license released mid-term stays available for reassignment to someone else for the remainder of that term. You can reassign it without losing the billing benefit of what you already paid.Reassignment
Reassignment is audited. There is a reasonable cooldown between reassignments to prevent abuse. Concurrency and device controls enforce the named-user policy.Product additions and reductions
Published monthly add-ons for active products are:
Enterprise product volume is custom.
Activating another product
You can activate another product while the workspace remains within its included allowance. If the allowance is full, upgrade to a plan with more active products or purchase the published add-on where available. Checkout must show the price and effective date before activation.Archiving a product
Archiving stops ProductOS production operation for that product and frees its active-product slot immediately while preserving its history. A lower plan price or contracted product-pack reduction takes effect according to the change shown at checkout or the executed order.True-ups
Annual workspaces settle contracted mid-year license or product-pack additions at renewal. The true-up covers the partial period from the addition date through the end of the annual term; the renewed subscription then includes the full annual amount. For example, a User License added 60 days into a 365-day annual term produces a prorated obligation for the remaining 305 days, settled under the annual true-up.Archive and reactivation
You can archive a product at any time. Archiving frees its active-product slot while keeping its full history, design system, and code links intact. The product can be reactivated at any time without rebuilding. Archiving is useful when a product is not currently in active operation but you want to preserve its history and be able to reactivate it later.ProductOS operation vs Production Handoff
ProductOS charges for operating products in production. GitHub sync, export, and fork are portability features, not billing switches. You can connect your GitHub, fork a repository, or re-import at any time without changing your bill. When a product is fully detached from ProductOS, you have two options: Continue on ProductOS: The product remains on your plan and you pay for its active-product slot. Production Handoff: A separately priced engagement packages the code, environment, and history for independent hosting, with optional ongoing care afterward. This is for products that will no longer operate on ProductOS. Scale and Enterprise include discounted Production Handoff rates. Contact hello@productos.dev for Production Handoff pricing.Related pages
- Pricing overview: how the three commercial units fit together
- Individuals: individual plan product allowances
- Teams: team plan product allowances and add-ons
- Agencies: agency plan product allowances, white-label, and handoff
- AI credits and models: how AI capacity relates to products
- Licenses and access: license management and reassignment
- Implementation reference: developer reference for product lifecycle events and billing hooks