Latest news from Flirexa

Business and Enterprise operators can maintain prepaid customer balances in the client portal. Credits can be added with an audit trail and used for renewals without forcing a customer through checkout for every transaction.

Per-device DNS protection now lets an operator offer standard resolution, ad and tracker blocking, malware protection, or a combined policy without moving the customer to another VPN server. Business includes the standard policy modes. Enterprise adds operator-defined resolver profiles and enforced policies for larger deployments.

• Customer balance history and controlled balance adjustments
• DNS mode stored per device and written into generated configurations
• Custom Enterprise resolver endpoints for operator-owned DNS infrastructure
• Current admin and client portal views for desktop and mobile

Explore the client portal and billing workflow →

The backup workflow now covers application state, database data, configuration, and the metadata required for a verified restore. Operators can keep local archives and connect supported network storage instead of treating a backup as complete simply because a file exists.

Paid licenses continue to use signed online validation with a signed offline allowance for temporary licensing-service outages. This preserves normal operation during an incident without turning a Lifetime license into a reusable static unlock.

• Scheduled backups, retention controls, and restore verification
• Local and supported network storage targets
• Signed offline continuity for legitimate paid installations
• Release verification, rollback support, and installer preflight checks

Read the security and reliability overview →

Brand settings now carry through the separate customer portal, including the operator name, logo, colors, login presentation, favicon, and customer-facing policy links where the plan allows it. Enterprise operators can also separate admin responsibilities with role-based access controls.

Checkout and support flows now return readable errors, preserve the customer context needed for replies, and protect support conversations with ticket-specific secrets instead of relying on an email address and ticket number alone.

• Brand-aware customer login and portal screens
• Operator-authored privacy and terms pages
• Provider-aware Stripe methods and corrected PayPal return handling
• Protected support replies and clearer payment recovery

See how white-label delivery works →