GPU servers at Trooper.ai operate in a private, high-performance environment without direct public IPs or DNS domains. Classic SSL/TLS certificates require visible domains or IPs for CA verification β conditions our GPU servers donβt meet. Instead, we rely on:
Both methods provide end-to-end encryption and strong identity assurance β even without public CA involvement.
openssl
to generate a certificate and private key.This ensures encrypted communication between your systems β confidential, authenticated, and efficient.
ssh-keygen
) on your workstation.~/.ssh/authorized_keys
.Full root access is provided via SSH, enabling complete control over your GPU server environment.
External HTTPS traffic is handled by our Trooper.ai Gateway, which uses officially issued SSL certificates from public CAs. Internal server communication remains encrypted using your self-signed certificate or SSH key (optional).
flowchart LR
Client["Client Browser/App"] -->|HTTPS (CA-signed)| Proxy["Trooper.ai Gateway (Proxy)"]
Proxy -->|Secure Internal TLS/SSH| GPU["Trooper.ai GPU Server"]
GPU -->|Compute Processing| GPU
This split architecture ensures:
Encrypted & Authenticated: All connections are TLS-secured or SSH-encrypted; clients verify your certificate or key, ensuring identity and privacy.
Full Control, No Dependency: You generate and manage your own certificates and keys. No reliance on third-party CAs or domain verification.
Fast, Flexible Deployment: Skip DNS/IP setups and CA processes β get GPU servers running quickly and securely.
Private, EU-Based Infrastructure: Servers are dedicated instances in GDPR-compliant EU data centers, with NAT, firewall protection, and no public IP exposure.