Accounts, Licences, and Billing

Distinguish identity, website sessions, product licences, organization access, and billing state.

Overview

Identity, download access, desktop licences, organization permissions, and billing are checked separately. Signing in can succeed even when a paid feature or project action is unavailable.

State Model

State	What it allows	Checked separately
Account sign-in	The browser or desktop authorization flow recognized an identity; the signed-in website account can request current released artifacts	Paid product capabilities, product licence, organization role, credit, or API access
Active paid plan	The account has the capabilities named by that plan	A different installer, unrelated Cloud features, organization roles, or unlimited usage
Desktop machine licence	The current install can pass its local product gate while valid	Cloud project, runner, or billing permission
Organization membership	The account belongs to a customer context	Every role, project, product, or operation
Entitlement or role	A specific product or operation is allowed	Unlimited usage or unrelated permissions
Billing or credit state	The displayed account has the shown commercial state	That a particular job will be accepted or complete

The product download start page checks account sign-in before accepting a file request. Free and paid accounts receive the same signed release. Completing checkout changes the capabilities named by the purchased plan; it does not issue or refresh the separate desktop machine licence.

Desktop Licence

After desktop browser sign-in, the application checks for a valid licence on the current machine. If the account is recognized but the install holds no licence, select Request a licence once. The request can still fail after successful sign-in. Do not bypass the check. Contact support if no entitlement is accepted. See First Launch and Licence for the complete screen-by-screen flow.

Organization and Project Context

Before any shared or managed operation, confirm the organization and project in the interface. A role should authorize only the operations it needs. Project data must remain inaccessible outside the required membership and permission scope.

Pricing and Billing

The public source for currently offered plans is Altifigence Pricing. This documentation does not duplicate prices. Free and paid plans use the same product downloads; paid plans unlock the features named on the pricing page. Local and Cloud actions show their own usage or credit information where applicable.

Before starting a metered action, check the organization, runner, usage unit, available limit or credits, and the usage record shown by the product. If these details are not shown, check with support before running a large job.

Legal, payment, refund, privacy, and withdrawal terms remain owned by the Legal Center.