Security

Security is not a feature at Pylon; it is our fundamental product. We define our success by our inability to access your data.

1. Zero-Knowledge Architecture

Pylon is engineered as a Zero-Knowledge system. Your inference data is encrypted on your client before it ever touches our network. We utilize ephemeral GPU enclaves that are cryptographically isolated from the host OS.

2. Encryption Standard

All data at rest is encrypted using AES-256-GCM. All data in transit is protected via TLS 1.3 with rigorous forward secrecy. Our key management employs Shamir's Secret Sharing to ensure no single key holder can decrypt sensitive keys.

3. Infrastructure Isolation

We enforce strict tenant isolation to prevent side-channel attacks:

• No Prefix Caching: We disable vLLM prefix caching to prevent timing attacks between tenants.
• Memory Scrubbing: We force explicit garbage collection and memory overwrites after every inference request.
• Network Policy: GPU containers run in a restricted network namespace with no egress access except to the response stream.

4. Private Keys

Your Master Encryption Keys are never stored in plaintext on our servers. They are derived from your password on the client side or stored in a dedicated HSM (Hardware Security Module) vault if you are an Enterprise customer.

5. Vulnerability Disclosure

We take responsible disclosure seriously. If you believe you have found a vulnerability in Pylon, please report it to security@pylon.run. We offer a bug bounty program for qualified reports.