Skip to main content
Browse documentation

Fronty documentation

Understand plans, billing, allowances, and upgrades

Read the live plan catalog, understand website-level entitlements, and verify checkout, portal, coupon, refund, and usage-limit behavior.

Last verified

Availability

Available when billing is enabled

Paddle checkout, subscriptions, portal, coupons, referrals, refunds and entitlements are implemented but depend on production configuration.

Plans
The backend plan catalog is the source of truth; use the live pricing page for current availability and amounts.
Roles
Website owner or another role allowed to manage billing.
Before you start
A website, a billing-capable account, and a supported payment method when upgrading.
On this page
  1. Use the live catalog, not copied limits
  2. Upgrade and verify checkout
  3. Manage the subscription lifecycle
  4. When an allowance is reached

Use the live catalog, not copied limits #

The application requests its plan catalog from the backend. That catalog controls price, availability and entitlements such as AI usage, pages, tables, rows, collaborators, storage, custom domains, branding and export.

Do not rely on limits copied into an old article or screenshot. Open the live pricing page, select the intended website, and read the current plan and availability returned for that account.

Upgrade and verify checkout #

  1. Select the website that should receive the plan. Billing controls are tied to a concrete website context.
  2. Choose an available plan. If billing or its price identifier is not configured, the interface should show the plan as unavailable rather than inventing a checkout.
  3. Apply a coupon or referral only through the supported field and review the amount inside Paddle before paying.
  4. After checkout, return to the website and confirm its plan and entitlements, not only the payment confirmation screen.

Manage the subscription lifecycle #

Use the billing portal for supported payment-method and subscription actions. Webhook processing is idempotent so repeated provider events should not duplicate the lifecycle change. Refund and cancellation availability depends on the current subscription and policy.

A failed payment or expired subscription can change entitlements. The product should preserve content while enforcing the resulting limits, but you should review locked pages, collaborators, domains, export and AI allowances before downgrading.

When an allowance is reached #

Fronty can show upgrade prompts when a page, database, row, storage, collaborator, AI or other allowance is exhausted. Check which website owns the usage and whether an unused item can be removed safely before upgrading.

You will know billing worked when the provider shows the completed transaction, Fronty shows the expected website plan, the intended entitlement changes, the portal opens for that subscription, and retrying a webhook does not create a duplicate subscription.
Your first website Go from a new Fronty account to a checked public URL without skipping the decisions that make the result safe to share. Teams and workspaces Invite collaborators without sharing credentials, assign the smallest useful role, and verify access in both dashboard and editor. Integrations and code export Distinguish customer-configured connections from Fronty's internal infrastructure, export the site, and verify what remains functional elsewhere.