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
  • Legal & Transparency
  • RAM-Only Processing & Non-Retention Policy Specs
View Categories

RAM-Only Processing & Non-Retention Policy Specs

1 min read

1. Overview & Diskless Operating Philosophy #

The BEX routing infrastructure enforces a strict RAM-only execution policy across all global gateway nodes. Under this operational spec, physical server nodes are deployed completely diskless, removing all hard disk drives (HDDs), solid-state drives (SSDs), and persistent NVMe storage media from edge hardware. By operating entirely within volatile Random Access Memory (RAM), BEX guarantees legally and technically that data persistence is impossible, as all server state vanishes permanently upon power loss, reboot, or connection termination.

2. Technical Architecture of Diskless Edge Nodes #

To eliminate persistent storage vectors and enforce zero-data-retention at the hardware layer:

  • PXE Network Bootstrapping: Gateway nodes boot directly over encrypted PXE (Preboot Execution Environment) streams, loading a read-only, cryptographically signed minimal Linux operating system image directly into system RAM.
  • Kernel-Enforced Swap Disabling: Kernel swap partitions, page files, and crash dump storage mechanisms are permanently disabled at compile time. Memory pages can never be written to non-volatile storage.
  • Blacklisted Storage Controllers: Kernel drivers for SATA, SAS, and NVMe controllers are removed from the OS image, rendering connected persistent hardware inaccessible to system processes.

3. Ephemeral Session Lifecycle & Automated Memory Scrubbing #

Data handling during active network sessions adheres to strict ephemeral boundaries:

  • In-Memory Ephemeral Keys: Cryptographic session keys and handshake material exist exclusively within volatile kernel memory and are bound strictly to active socket lifetimes.
  • Microsecond Memory Scrubbing: Upon socket teardown, the system executes explicit memory zeroing routines (explicit_bzero / secure memory wipes) to prevent residual state leakage in RAM buffer pools.
  • Cold-Boot & Intrusion Defenses: Edge servers implement physical intrusion detection. Any physical tamper event or power interruption triggers an instantaneous hardware reset, wiping all RAM contents within milliseconds via hardware decay.

4. Non-Retention Legal Guarantees #

From a legal and compliance standpoint, the RAM-only processing specification establishes that:

  • Absence of Stored Evidence: BEX cannot be compelled to disclose historical traffic logs or user metadata because such data literally does not exist in any physical storage medium.
  • Real-Time Data Ephemerality: Transient packets passing through volatile memory are processed strictly in transit without creating temporary cache files or disk buffers.

5. Key Strategic Benefits #

  • Absolute Physical Security: Server seizure or physical theft yields zero data, as powering down the unit permanently destroys all operational memory.
  • Elimination of Data Leakage: Microsecond RAM scrubbing prevents cross-session side-channel memory leaks.
  • Verifiable Compliance: Simplifies auditing for B2B partners by providing cryptographic proof of diskless operation.

Still stuck? How can we help?

How can we help?

Updated on September 29, 2026
End User Lisense Agreement (EULA) & Acceptable Use PolicyBEX Strict Zero-Logs Privacy Policy & Data Handling Specifications

Leave a Reply Cancel reply

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

Table of Contents
  • 1. Overview & Diskless Operating Philosophy
    • 2. Technical Architecture of Diskless Edge Nodes
    • 3. Ephemeral Session Lifecycle & Automated Memory Scrubbing
    • 4. Non-Retention Legal Guarantees
    • 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