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
  • Shared Bandwidth Pools & Multi-Device Volume Allocation in Gigify
View Categories

Shared Bandwidth Pools & Multi-Device Volume Allocation in Gigify

1 min read

1. Overview & Architectural Purpose #

The Gigify Shared Bandwidth Pool architecture allows a single primary master account to maintain a central, unified volume vault (such as 500 GB) that is concurrently accessible across multiple authorized devices, family members, or team sub-accounts. Instead of purchasing separate, isolated volume packages for phones, laptops, and tablets, all active TUN sessions draw byte consumption directly from one central data pool in real time.

2. Unified Volume Pool Mechanics #

  • Master Vault Single Source of Truth: The central control plane maintains the primary volume balance as a single immutable ledger entry. All bound devices reference this master pool during session authorization.
  • Seamless Hardware Allocation: Master accounts can bind multiple cryptographic Hardware IDs (HWIDs) or issue sub-account credentials to share volume without requiring individual wallet setups for secondary users.
  • Zero Cross-Device Waste: Unused bandwidth allocated to a mobile device remains fully accessible to desktop clients or secondary users, eliminating isolated, unconsumed data pockets.

3. Real-Time Multi-Device Metering & Concurrency #

When multiple authorized devices connected to the same shared pool operate simultaneously, the BEX metering engine manages concurrency through a distributed sync protocol:

  • Concurrent eBPF Delta Aggregation: Each edge gateway node measures raw byte throughput for individual active Hardware IDs using kernel-level eBPF probes.
  • Central Delta Synchronization: Every 30 seconds (or upon accumulating 10 MB of transferred data), edge gateways submit signed delta reports to the central master vault.
  • Concurrent Deduction Logic: The control plane deducts byte consumption from the shared pool in real time. If Device A downloads 2 GB while Device B uploads 1 GB concurrently, the master pool accurately decreases by 3 GB without session locking or throughput throttling.

4. Device-Level Controls & Allocation Quotas #

To prevent a single device or sub-account from unexpectedly depleting the central volume pool, BEX provides granular administrative controls:

  • Per-Device Volume Caps: The master account can assign hard or soft volume limits (e.g., capping a specific smartphone at 50 GB per month) directly from the control dashboard.
  • Instant Device Revocation: Master administrators can unbind specific Hardware IDs or pause sub-account access instantly, revoking tunnel creation rights across all global edge nodes.
  • Device Usage Visibility: Clear administrative telemetry displays total gigabytes consumed per bound device without inspecting packet contents or recording destination IP addresses.

5. Key Strategic Benefits #

  • Cost Consolidation: Single-point purchasing for households, small businesses, and multi-device power users.
  • Maximum Volume Utility: Every single megabyte purchased is utilized across the device ecosystem without per-device expiration or isolation.
  • Granular Consumption Oversight: Complete administrative management over multi-device bandwidth usage from a single dashboard.
Still stuck? How can we help?

How can we help?

Updated on October 4, 2026
BEX Global Routing Infrastructure & Gateway Node Distribution Cumulative Quota Engine & Validity Rollover Protocol

Leave a Reply Cancel reply

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

Table of Contents
  • 1. Overview & Architectural Purpose
    • 2. Unified Volume Pool Mechanics
    • 3. Real-Time Multi-Device Metering & Concurrency
    • 4. Device-Level Controls & Allocation Quotas
    • 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