Beta license handling.

The license story should stay simple for 0.1.0: one payment, beta access, clear activation, and clear recovery if a key cannot be used.

Paddle confirmation drives license delivery.

Confirmed beta purchases generate a license key in the buyer account. The desktop app can activate that key and report active devices back to the license backend.

Beta access

A purchased license unlocks the FaberPDF beta release line for the buyer.

Activated

The desktop app should recognize a valid beta license and enable the signing, annotation, and text editing workflow.

Needs recovery

Invalid, missing, or over-activated beta licenses should show a clear support path instead of a dead end.

Recommended beta license rules

These rules are intentionally narrow so the beta can ship without locking in the stable release pricing model.

Public beta policy

Buyer-facing copy that can also be reflected in the desktop app.

A paid beta purchase grants access to FaberPDF beta 0.1.0.
The purchase is not a subscription and does not define version 1.0.0 pricing.
License keys are delivered only after confirmed Paddle checkout.
The app should show recovery steps for invalid, missing, or over-activated beta keys.
Refund, tax, receipt, and payment records should be handled through Paddle once checkout is live.

Ready to buy beta access?

Pricing is the front door. Download and activation become the post-checkout route when Paddle is configured.

Buy beta access