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
  •  Cumulative Quota Engine & Validity Rollover Protocol
View Categories

 Cumulative Quota Engine & Validity Rollover Protocol

1 min read

1. Overview & System Purpose #

The BEX Cumulative Quota Engine is designed to maximize bandwidth value through a flexible validity rollover architecture. Built directly into the Gigify system, each purchased bandwidth package is assigned a specific calendar validity period. While packages are subject to calendar expiration, BEX allows complete volume preservation through timely top-ups: if a user purchases a new package prior to the calendar expiration date of their active package, all remaining unused bandwidth is automatically rolled over and added to the new package, extending the expiration date for the entire cumulative balance to match the new package terms.

2. Architectural Design & Credit Preservation Logic #

The BEX control plane manages volume validity and accumulated data through a structured credit ledger system:

  • Calendar-Bound Ledger Vault: Purchased gigabytes are recorded alongside a active calendar expiration timestamp within the user’s account vault in the central control plane.
  • Accumulative Rollover Guarantee: Unused bandwidth is preserved as long as the subscription remains active. Purchasing any new package prior to the current expiration date merges the remaining volume into the new allowance and resets the validity timer for the total combined balance.
  • Infrastructure Independence: Stored volume balances and validity timers remain bound to the user’s global control plane identity rather than individual edge nodes, ensuring server maintenance or gateway shifts do not disrupt user credits.

3. Expiration, Rollover & Forfeiture Protocols #

To maintain predictable system capacity and resource management, BEX enforces clear operational rules:

  • Pre-Expiry Top-Up (Rollover): Purchasing a new Gigify package before the active calendar expiration date preserves 100% of the unconsumed bandwidth, carrying it forward into the new cycle.
  • Calendar Expiration & Forfeiture: If no new package is purchased before the current calendar validity window expires, any remaining unused data balance is permanently forfeited at the exact expiration timestamp.
  • Automated Expiry Alerts: The system dispatches automated notifications prior to the expiration date, allowing users to preserve their unused data by topping up in advance.

4. Operational Comparison: BEX Cumulative Model vs. Standard Plans #

  • Standard Plan Model: Unused monthly data expires strictly at the end of the billing cycle without any rollover mechanism, resulting in total loss of unconsumed volume regardless of future purchases.
  • BEX Cumulative Model: Dynamic volume protection. Users can protect and accumulate unused data indefinitely as long as they maintain continuity by topping up prior to package expiration dates.

5. Key Strategic Benefits #

  • Zero Data Loss via Timely Top-Ups: Eliminates wasted capital by allowing users to keep every remaining megabyte through active package renewals.
  • Scalable Bandwidth Pools: Enables users to accumulate large data reserves over time while extending overall account validity with each top-up.
  • Balanced Expense Management: Combines structured calendar cycles with volume protection, offering fairness and flexibility for all usage patterns.
Still stuck? How can we help?

How can we help?

Updated on October 4, 2026
Shared Bandwidth Pools & Multi-Device Volume Allocation in GigifyGigify Real-Time Metering Engine & Per-GB Bandwidth Accounting

Leave a Reply Cancel reply

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

Table of Contents
  • 1. Overview & System Purpose
  • 2. Architectural Design & Credit Preservation Logic
  • 3. Expiration, Rollover & Forfeiture Protocols
  • 4. Operational Comparison: BEX Cumulative Model vs. Standard Plans
  • 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