雅努斯流 · 双面守护门神 janusflow.cn 双塔加密流量识别平台 | PCDN · 反诈 · SDPI · OpenWrt 路由产品合作
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.

Suite ID & Dimension Sample Size (N) & Testbed Scope Verified Result & Latency / Resource Footprint
Index & Rule Coverage app_cn_names.json · clawbox_cloud_catalog_v3.json.gz · edge_2000.cbx 730,254 package mappings · 467,520 Cloud Indexed APKs · 2,000 Edge Core Apps (64 KB) · 5,006 Profiles / 5,105 Domain Rules · 16,265 Honeytrap Decoys · 15 SDKs (18 Legal Entities)
EMP-01: 3 Physical Phones × 4 Rounds Blind Test N = 12 device-round tasks (351 live flows across 3 heterogeneous physical Android phones) 100.0% (12/12, mean conf 0.8901) · Stage-2 GPU kNN mean 22.61 ms (58.13–192.00 ms total per window)
EMP-02: Multi-Granularity Cellular rmnet_data N_15s = 4 · N_10m = 9 · N_1h = 14 live cellular windows on physical Xiaomi MI 6X 15s: 100.0% (4/4) · 10m: 100.0% (9/9) · 1h: 100.0% (14/14) · Total window latency 56.87–367.52 ms
EMP-03: 3-App Mixed-Stream Demux & 8s Micro-Slice N_scenarios = 2 · N_switched_apps = 6 · N_8s_slices = 8 (50 interleaved flows) Demux Recall: 100.0% (6/6) · 8s Slice Hit: 100.0% (8/8) · Window processing 29.77 ms
EMP-04: Dual-Gallery Throughput & Cloud API Footprint N_flows = 186 (6.41 MB raw cellular pcap on RTX 4060 Ti & Cloud API node) 10k gallery: 391.3 MB VRAM, 9.36 ms (1,603.2 flows/s) · 45k gallery: 1,301.3 MB VRAM, 12.28 ms (937.9 flows/s) · Pure-CPU Cloud API node: <45 MB RSS, <1 ms single lookup

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.