Flirexa / White-label VPN platform

What white-label means here

White-label is not a logo pasted on a generic checkout. The customer journey needs to remain coherent from registration to connection and support.

Identity and interface

Set the product and company names, logos, primary color, favicon, and browser title from the admin panel. The customer portal loads the chosen theme before its interface mounts.

Domains and email

Use custom admin and portal domains, publish the customer portal from your website, and configure the outbound From identity through your own mail provider.

Customer terms

Provide Privacy and Terms links or publish hosted legal pages in the same portal style. The content remains your responsibility and can be updated without changing source code.

Client applications

Enterprise includes the standard Android, Windows, and Linux application package. A separately scoped project can adapt application identity and release assets for a specific brand.

Operator access

Manager RBAC creates additional admin accounts with focused permission scopes. Audit records show who changed customers, servers, support, or settings.

Infrastructure control

The brand layer does not put Flirexa between you and your customers' VPN traffic. Servers, customer data, configurations, and provider accounts stay under operator control.

Client applications

One account and device model across platforms

Android

A touch-first app for sign-in, device registration, region selection, connection state, and subscription-aware access.

Windows

A desktop app with its own Windows authentication and connection logic, registered as a separate customer device.

Linux

A terminal client for Linux users, built for console workflows instead of pretending to ship a desktop GUI.

A coherent customer path

  • customers authenticate against your installation
  • plans and exact prices come from the panel
  • provider-confirmed payment activates the subscription
  • device slots issue the right configuration for the selected server and protocol
  • support requests stay attached to the customer account
  • official apps use the same account and device model
WebsiteYour marketing site remains independent and links into the customer portal
PortalA separate customer application, not an admin-panel tab
PaymentsYour provider credentials and eligibility determine the methods available to buyers
BrandingAppearance controls are an Enterprise boundary, including logo, colors, domains, favicon, title, email identity, and legal links

Business or Enterprise

CapabilityBusinessEnterprise
Multi-server operationsUp to 10 serversUnlimited servers
Customer balance and per-device DNS modesIncludedIncluded
Built-in appearance changesNot includedFull controls
Custom admin and portal domainsNot included as a white-label controlIncluded
Custom email identity and legal pagesNot included as a white-label controlIncluded
Scoped manager accountsNot includedIncluded
Standard customer appsAvailable separatelyIncluded

Changing public open-core code does not grant a commercial feature entitlement. The official paid build and signed licence determine which protected capabilities are available.