Flirexa / Security and reliability

Network contacts

ConnectionPurposeData boundary
Community Edition runtimeNormal panel and VPN operationNo paid licence heartbeat
Installer diagnosticsCoarse phase and failure information used to support broken installationsCan be disabled with INSTALL_TELEMETRY=off
Update serviceFetch signed channel metadata and release packagesVersion, manifest, and ordinary request metadata; package integrity is verified
Paid licence validationVerify entitlement, limits, server binding, and current statusLicence/activation identifiers, derived hardware and instance identifiers, version/status metadata, and ordinary request metadata
Payment providerCreate and settle the operator's customer invoicesInvoice and buyer fields required by the configured provider
Outbound emailActivation, account, payment, and support messagesSent through the mail service configured by the operator

Paid licences

Subscription licences validate periodically to enforce the purchased entitlement, limits, server binding, and current status. A signed cached tolerance keeps the paid installation operating for up to 72 hours during a temporary licence-service interruption.

A different machine requires an authorized licence transfer and hardware rebinding

Paid licence validationVerify entitlement, limits, server binding, and current status

Lifetime licences

A Lifetime purchase is a perpetual entitlement for the licensed installation and tier. It still validates periodically to detect copied or reused commercial builds.

Each successful validation rotates a signed offline lease bound to the licence, persistent installation instance, and hardware. Deleting a cache, restoring an old snapshot, or moving the clock does not create a fresh allowance.

LifetimePerpetual entitlement with a signed offline lease of up to 30 days after successful validation

Payments

Provider settlement is authoritative

Flirexa grants an operator licence or customer subscription only after re-reading a provider result and matching the settled invoice. A success URL, screenshot, or browser query parameter is not enough.

Retries are idempotent

Webhook delivery and provider polling can repeat. Settlement identifiers and database constraints prevent a verified payment from issuing or extending twice.

Pending recovery is conservative

The reconciliation job can re-check pending invoices after a dropped webhook. If provider connectivity fails, it alerts the operator and credits nobody.

Exact amounts are checked

The server stores and compares the expected amount and currency. Customer balance accounting uses integer minor units rather than binary floating point.