Choosing the right license tier

The most common support question we get is not about code. It is "which license do I actually need?" The tiers exist to map cleanly onto what you plan to build, and once you see them side by side the answer is usually obvious.

## Standard: one product, one customer

The Standard tier covers a single end product for a single client or for yourself. You get full source, you can modify freely, and you can ship it as part of one delivered project.

If you are a freelancer building one site for one client, this is almost always the right choice. It is the cheapest tier because it carries the narrowest grant.

## Extended: charge your users

Extended adds the right to build a product that your own end users pay to access. The moment money flows from your users into your product, you have crossed from Standard into Extended territory.

A common trigger is a paywalled dashboard or a paid mobile app built on top of a starter. The starter is an ingredient, and Extended licenses the ingredient for commercial resale in a single product.

## White-Label: sell it as yours

White-Label lets you strip attribution and present the product under your own brand across multiple client engagements. Agencies delivering the same solution to many clients live here.

This tier is about repetition. If you plan to deploy the same product shape for client after client, buying it once under White-Label is dramatically cheaper than buying Standard many times over.

## SaaS Multi-Tenant: one deployment, many tenants

The top tier covers a single hosted deployment serving many paying tenants from shared infrastructure. This is the model behind most modern software businesses, and it carries the broadest grant.

Upgrade-in-place pricing means you only pay the difference when you move up a tier. Start on Standard for a prototype, then upgrade to SaaS Multi-Tenant when the prototype becomes a company, without repurchasing.