For SD-WAN · SASE · NGFW · Commercial DPI & Router Vendors
Identify 467,520 Mobile Apps & 15 Embedded SDKs Without TLS Decryption or Payload Inspection
Modern mobile applications enforce TLS 1.3 ECH, QUIC (UDP 443), and certificate pinning. JanusFlow (ClawBox B-Line) classifies encrypted flows using a compact <15 Bytes/flow Zero-PII statistical envelope—backed by 730,254 Android package-to-app mappings, 467,520 Cloud Indexed APKs, and 16,265 Honeytrap decoy guards—delivering sub-millisecond pure-CPU Cloud Recognition API lookup without touching payload contents or subscriber identities.
467,520
Cloud Indexed Apps
730,254 package mappings & 16,265 honeytrap decoys
2,000
Edge Core Apps
edge_2000.cbx (64 KB) + 5,006 profiles / 5,105 domain rules
<15 Bytes/flow
Zero-PII Envelope
Packet-length & IAT moments only; zero payload PII
<1ms
Pure-CPU Cloud API
Single lookup <1 ms on pure-CPU node (<45 MB RSS)
15
Authoritative SDK Profiles
18 legal entities across Push, Ad, Crash & Analytics
How Zero-PII Encrypted Traffic Recognition Works
Your data-plane forwarder (DPDK / VPP / eBPF / OpenWrt Linux Netfilter) extracts a compact statistical feature sketch locally and queries the Cloud Recognition API over TLS 1.3 with HMAC-SHA256 v2 authentication.
Stage-1 · Data-Plane Pre-Extraction
1. Edge Feature Sketch (<15 Bytes/flow)
Lightweight statistical extraction directly on CPE, SD-WAN branch appliances, or optical TAP nodes without breaking encryption.
- Captures only first-packet directional lengths, inter-arrival time (IAT) log-histograms, and burst timing statistics.
- Zero MITM Decryption: Never installs root certificates or breaks TLS 1.3 / QUIC handshakes.
- Zero PII Transmission: Subscriber IPs, MAC addresses, DNS queries, and raw packet payloads never leave your gateway.
Stage-2 · Dual-Tower Cloud Inference
2. Dual-Tower Attribution & OOD Guard (<1ms CPU)
High-precision attribution separating host applications from embedded third-party advertising, push, and analytics SDKs.
- Matches statistical sketches against 467,520 Cloud Indexed APKs (
clawbox_cloud_catalog_v3.json.gz), 730,254 package-to-app mappings (app_cn_names.json), and 15 embedded third-party SDK profiles (18 legal entities).
- Two-stage Out-of-Distribution (OOD) rejection and 16,265 Honeytrap decoy domains prevent false-positive attribution and block oracle probing.
- Supports SD-WAN application-aware QoS steering, SASE zero-trust policy enforcement, and enterprise shadow-app auditing.
Verified Empirical Benchmark Summary (v1.0)
All benchmark metrics below are 100% reproducible via reproduce_bline_coverage_benchmark.py across physical cellular devices and multi-app encrypted streams, with explicit sample sizes (N) disclosed for every evaluation suite.
Export Compliance & Dual-Track Delivery Boundary
To ensure strict adherence to international data privacy standards and dual-use technology export regulations, JanusFlow enforces a clear geographic delivery boundary:
Cloud Recognition API Only
Global / Overseas Customers
Sub-millisecond cloud lookup for international SD-WAN, SASE, NGFW, and DPI vendors.
- Global / Overseas Customers are served exclusively via Cloud Recognition API (
POST /api/v2/traffic/profile-period).
- Zero-PII, No MITM Decryption: Only
<15 Bytes/flow statistical sketches are transmitted; raw PCAPs and subscriber identifiers remain 100% on-premises.
- Offline
.cvault / .cbx feature packs and orthogonal transformation keys are never exported outside Mainland China.
- Includes 14-Day Technical POC API credentials (
cnx_live_* + HMAC-SHA256 v2 secret) for commercial SD-WAN, SASE, NGFW, and enterprise security vendors.
Compliance-Cleared Mainland China Only
Domestic Deployments (Mainland China)
Hardware-locked offline vaults for compliance-cleared domestic telecom and enterprise gateways.
- 6-Layer Hardware-Bound Offline
.cvault Feature Packs are restricted to compliance-cleared domestic deployments (sample_1000: 14d / 0d grace; commercial: 30d / 7d grace).
- Protected by per-customer
512-dim dual-tower orthogonal rotation matrices Q_L / Q_R (measured unpaired cross-customer cosine 0.06467, max orthogonality deviation 6e-07), HKDF-SHA256 hardware fingerprint (HWID) key derivation, AES-256-GCM encryption, Ed25519 signature verification, and 8 per-customer Canary/Honeytrap fingerprints.
- Requires corporate KYC verification, 5-step compliance screening, and a signed Civilian Network Security & QoS End-User Statement (EUS) prior to issuance.
Request 14-Day Technical POC (Cloud Recognition API)
Apply with your corporate email domain to evaluate JanusFlow Cloud Recognition API against your live SD-WAN, SASE, NGFW, or DPI testbed. Free personal email providers (gmail.com, outlook.com, qq.com, etc.) are automatically rejected.