Shatachandra Shield
ML-KEM-768 KeyGen (mean)
0.4335 ms
ML-KEM-768 Encaps (mean)
0.5041 ms
Avalanche Effect (SAC)
49.93%
NIST ACVP KAT Vectors
180/180 Pass
Shannon Entropy Density
7.9999 / 8.0000

Live Gateway Testing Console

A genuine, end-to-end ML-KEM-768 handshake against the live production gateway. Server-side key generation happens on our real L4→L3→L5 pipeline; client-side encapsulation happens for real, in your browser, using the independently-audited noble-post-quantum library — nothing here is simulated. Genuine failures (invalid key, rate limits, gateway errors) are displayed exactly as the server returns them.

Wire Boundary: Length-Prefixed JSON • Real ML-KEM-768 • Fail-Closed • Don't have a key? Generate one in the Operator Console
shatachandra-shield-live-diagnostics
LIVE PRODUCTION CLUSTER: api.shatachandrashield.xyz | [Qualys A+ Verified]
[SYSTEM] Ready. Paste a real API key above and click "Run Live Handshake" to begin a genuine ML-KEM-768 session against production. This will use part of your key's 14-day trial window, same as any other real request.

How to Deploy Shatachandra Shield on Your Server

Integrate the 3-tier post-quantum zero-trust defense engine into your microservices, reverse proxies, or edge API gateways using per-installation API keys and Unix Domain Sockets.

Step 1 • Authentication

Configure Your Installation Key

Obtain your static per-installation secret (L4_INSTALLATION_KEY) from your Operator Console. The Layer 4 gateway performs constant-time validation on every incoming request alongside background license verification.

Step 2 • Local Socket Relay

Unix Domain Socket Plumbing

Run the Layer 4 proxy process bound to /tmp/shatachandra_l4.sock. Communication utilizes length-prefixed JSON frames with strict 1 MiB boundaries, guaranteeing zero shared-memory leakage into L5 crypto memory.

Step 3 • Inline PQC Handshake

FIPS 203 ML-KEM Session Key

Send handshake_start to receive public parameters, execute ML-KEM-768 encapsulation, and submit handshake_finish to establish an authenticated, quantum-resistant session in under 0.51 ms.

PYTHON ASYNCIO CLIENT • LOCAL UNIX DOMAIN SOCKET RELAY PROTOCOL: LENGTH-PREFIXED JSON
import asyncio
import json
import struct

# 1. Connect to the Layer 4 Security Gateway local socket
SOCKET_PATH = "/tmp/shatachandra_l4.sock"
INSTALLATION_KEY = "YOUR_L4_INSTALLATION_API_KEY"

async def send_pqc_handshake(session_id: str):
    reader, writer = await asyncio.open_unix_connection(SOCKET_PATH)
    
    # 2. Construct authenticated wire frame (handshake_start)
    request_payload = {
        "api_key": INSTALLATION_KEY,
        "session_id": session_id,
        "request_type": "handshake_start"
    }
    
    # 3. Serialize and length-prefix payload (4-byte big-endian header)
    payload_bytes = json.dumps(request_payload).encode("utf-8")
    frame_header = struct.pack("!I", len(payload_bytes))
    writer.write(frame_header + payload_bytes)
    await writer.drain()
    
    # 4. Read response frame
    response_length = struct.unpack("!I", await reader.readexactly(4))[0]
    response_data = json.loads((await reader.readexactly(response_length)).decode("utf-8"))
    
    print("PQC Gateway Response:", response_data)
    writer.close()
    await writer.wait_closed()

asyncio.run(send_pqc_handshake("session-prod-001"))
NGINX REVERSE PROXY SIDECAR CONFIGURATION LAYER 4 GATEWAY SIDECAR
# Route edge API traffic through Shatachandra Shield PQC Gateway
upstream pqc_gateway {
    server unix:/tmp/shatachandra_l4.sock fail_timeout=0;
}

server {
    listen 443 ssl http2;
    server_name api.yourdomain.com;

    # Injected Operator Installation Key
    proxy_set_header X-Shield-Key "YOUR_L4_INSTALLATION_API_KEY";
    proxy_set_header X-Client-IP $remote_addr;

    location /pqc/handshake {
        proxy_pass http://pqc_gateway;
        proxy_http_version 1.1;
        proxy_set_header Host $host;
        proxy_buffering off;
        proxy_read_timeout 5s;
    }
}