Skip to navigation Skip to main content
  • Home
  • Price
  • Docs
  • Learn
  • Contact us

Technical & Architecture

19
  • Control vs. Data Plane Architecture: Decoupling Web Dashboard from Client Engine
  • Client Core Architecture: TUN Interface & Split Tunneling Specs
  • Webhook Event Pipeline for Automation & Billing Platforms
  • BEX Reseller REST API Specification & OAuth Authentication
  • Automated Top-Up Market & Crypto Instant Settlement Architecture
  • Sub-Reseller Hierarchy & Multi-Tier Credit Allocation Engine
  • Tokenized Bandwidth Economics & Balance Solvency Architecture
  • Edge Rate-Limiting & Traffic Anti-Abuse Architecture
  • Ā Zero-Log Edge Telemetry & Real-Time Gateway Health Monitoring
  • Cryptographic Key Exchange & DNS/IPv6 Leak Prevention
  • Zero-Log Pipeline & RAM-Only Server Operating Environment
  • BEX Global Routing Infrastructure & Gateway Node Distribution
  • Shared Bandwidth Pools & Multi-Device Volume Allocation in Gigify
  • Ā Cumulative Quota Engine & Validity Rollover Protocol
  • Gigify Real-Time Metering Engine & Per-GB Bandwidth Accounting
  • Priority Routing & Dedicated Gateway Bandwidth Allocation
  • Concurrent Device Handshake & Hardware ID Allocation
  • Premiume Subscription Lifecycle & Fixed Timeframe Engine
  • Active vs. Inactive Session Detection Protocols

Legal & Transparency

8
  • Refund Eligibility & Balance Adjustment Terms
  • Cryptocurrency Billing & Wallet Top-Up Terms
  • Sub-Reseller Hierarchy Regulations & Compliance Guidelines
  • Reseller Partner Agreement & Token Ownership Rules
  • Service Availability & SLA Commitments
  • End User Lisense Agreement (EULA) & Acceptable Use Policy
  • RAM-Only Processing & Non-Retention Policy Specs
  • BEX Strict Zero-Logs Privacy Policy & Data Handling Specifications

Frequently Asked Questions

16
  • What should I do if I experience connection timeouts or speed degradation?
  • What encryption algorithms and routing protocols are implemented?
  • How does BEX prevent DNS, WebRTC, and IPv6 leaks?
  • Does BEX VPN log my browsing activity, IP address, or traffic data?
  • Can I integrate BEX services with Telegram bots or custom WHMCS platforms?
  • How does instant settlement work in the automated Top-Up market?
  • How do I configure Sub-Reseller accounts and commission tiers?
  • How do bandwidth tokens work in the BEX Reseller ecosystem?
  • What cryptocurrency payment methods are accepted for top-ups?
  • Does unused bandwidth expire in Gigify plans?
  • How is bandwidth usage calculated and tracked in Premium and Gigify plans?
  • What is the difference between Premium and Gigify plans?
  • Can I use my account across multiple devices simultaneously?
  • How do I create and secure my BEX account?
  • Do I connect to the network from the web dashboard or the client app?
  • What is BEX VPN and how does it differ from traditional VPNs?
  • Home
  • Docs
  • Technical & Architecture
  • Premiume Subscription Lifecycle & Fixed Timeframe Engine
View Categories

Premiume Subscription Lifecycle & Fixed Timeframe Engine

2 min read

1. Overview & System Purpose #

The BEX Premium Subscription Engine is engineered for users who require continuous, always-on network security and priority routing. Unlike the consumption-based Flex architecture, Premium subscriptions operate on a Fixed Timeframe Engine governed by standard calendar cycles (e.g., 30-day, 90-day, or 365-day periods). Throughout the active period, users receive unrestricted tunnel access, unlimited bandwidth throughput, and elevated routing priority across global gateway nodes.

2. Subscription Lifecycle States #

The BEX control plane manages the Premium subscription lifecycle through four distinct operational states:

  • Provisioned State: The payment is confirmed and encryption credentials are generated, but the activation countdown is held in a grace window prior to the first handshake.
  • Active State: The subscription is fully operational. The user enjoys uninterrupted connection rights, high-priority gateway routes, and multi-device concurrency without daily session limits.
  • Grace / Renewal Pending State: The exact expiration timestamp has been reached. A temporary grace period (typically 24 to 48 hours) is granted to allow seamless automated or manual renewal without dropping live connections.
  • Expired / Terminated State: The grace period has ended without renewal. Priority network routes are revoked, and tunnel creation attempts are blocked until a new plan is activated.

3. Fixed Timeframe Engine Mechanics #

  • Absolute Calendar Metering: The time counter runs continuously from the moment of activation until the expiration timestamp, regardless of whether the user is actively connected or offline.
  • UTC Synchronization: All subscription start, renewal, and expiration timestamps are synchronized against UTC atomic time across all distributed edge gateways to prevent client-side time manipulation.
  • Priority Traffic Allocation: Premium connections are flagged in the control plane to receive priority packet queuing at high-traffic gateway nodes, maintaining low latency during peak hours.

4. Renewal Pipelines & Zero-Downtime Transition #

  • Automated Expiration Webhooks: The control plane issues real-time notification events at 7 days, 3 days, and 24 hours prior to expiration.
  • Seamless Extension: When a renewal payment is processed, the system appends the new timeframe directly onto the existing expiration timestamp without forcing active VPN tunnels to disconnect or re-authenticate.

5. Key Strategic Benefits #

  • Uninterrupted Access: Ideal for daily power users, continuous remote work, and high-throughput streaming.
  • Priority Infrastructure: Direct access to dedicated premium gateway pools with reduced congestion.
  • Predictable Renewal: Clear, standardized billing cycles with automated reminders.
Still stuck? How can we help?

How can we help?

Updated on October 4, 2026
Concurrent Device Handshake & Hardware ID AllocationActive vs. Inactive Session Detection Protocols

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Table of Contents
  • 1. Overview & System Purpose
    • 2. Subscription Lifecycle States
    • 3. Fixed Timeframe Engine Mechanics
    • 4. Renewal Pipelines & Zero-Downtime Transition
    • 5. Key Strategic Benefits
Based on WoodMart theme© 2026 WooCommerce Themes.
payments
Close
  • Home
  • Price
  • Docs
  • Learn
  • Contact us
  • Languages
    • You need WPML plugin for this to work. You can remove it from Header builder.
Shop