1. Architecture & Customer Trust Boundary
AetherKube is built with an operational sovereignty design philosophy. It runs entirely on customer-managed workstations, servers, or Kubernetes clusters.
Your Kubernetes cluster credentials, kubeconfig files, pod logs, secrets, and application payloads remain inside your trusted network perimeter. Only minimal, cryptographically signed licensing tokens pass between your instance and our edge control plane.
2. Core Security Controls
License tokens use tamper-proof HMAC-SHA256 signatures verifying organization ID, cluster limits, and expiry dates without exposing secrets.
Release package downloads require one-time session tokens. Replay attempts are instantly blocked (HTTP 410).
The control plane records licensing milestones in a strictly append-only ledger. Records are never deleted or overwritten, ensuring complete auditability.
The administrative control plane runs on an isolated port (9090) with zero route exposure to the customer backend.
3. Zero-Exfiltration Guarantee
- No Kubeconfig Telemetry: Cluster credentials are never transmitted externally.
- No Workload Inspection: Diagnostic engines inspect only Kubernetes API status metadata and event logs, never application database payloads.
- Air-Gapped Copilot Support: AI Copilot supports local model engines (such as Ollama or vLLM), allowing fully air-gapped diagnostics.
4. Vulnerability Disclosure
To report a security vulnerability or operational anomaly, contact: