Flirexa / Protocols / TUIC

Starter and above

Offer TUIC without operating a separate customer system

TUIC is a QUIC-based proxy option with its own client format and network behavior. Flirexa keeps its access tied to the same customer records, plan limits, server inventory, payments, and support workflows as the rest of the service.

View StarterOpen the official TUIC project

Operational fit

Another transport is valuable only when customers can actually use it

Protocol-specific delivery

A TUIC customer needs a compatible client and the correct access payload. Flirexa renders that payload from the server and customer records rather than presenting a WireGuard file.

Shared commercial model

The subscription, expiration, enabled state, plan, payment, and support context remain in one customer system even when the access protocol differs.

Network testing still matters

TUIC depends on QUIC and UDP behavior. Test the actual mobile networks, ISPs, routes, and client implementations in the market you serve.

Plan boundary

Starter adds the protocol; Business adds the network

  • Starter enables TUIC on the installation host
  • Business adds remote-node orchestration for several locations
  • customer plans determine which access is available
  • the portal and support history remain protocol-independent
  • the server record owns endpoint and health state
  • client compatibility must be validated before a public promise
TransportQUIC-based proxy maintained by the official TUIC project
Customer formatProtocol-specific URI or payload for a compatible application
Single locationStarter
Managed locationsBusiness or Enterprise

Questions

TUIC in Flirexa

Can an ordinary WireGuard client connect to TUIC?

No. TUIC uses a different protocol and requires a compatible client.

Is TUIC always faster than the other options?

No. Performance depends on the route, packet loss, UDP policy, server capacity, congestion behavior, and client implementation. Benchmark the real path.

Can I sell several protocols under one plan?

Yes, when the Flirexa licence and plan grant them. The customer and subscription model remains shared while each server delivers its own protocol format.