Zervox bridges raw Prometheus metrics, pod logs, and safe Kubernetes execution. Ingest alerts securely, diagnose with LLMs, enforce OPA policy guardrails, and execute remediation automatically or via human authorization.
Zervox delivers low-latency incident response with strict security boundary guarantees.
Enforces Bearer Token / API Key validation on all HTTP endpoints. Unauthenticated alert payloads are immediately rejected with HTTP 401.
Validates all AI recommendations prior to execution. Absolute blocks prevent namespace deletion, RBAC edits, secret reads, and container shell exec.
Enable ZERVOX_REQUIRE_APPROVAL=true to transition non-read-only cluster actions to PENDING_APPROVAL in SQLite instead of auto-executing.
SQLite operating in WAL mode with 5-second busy timeout connection pools guarantees zero lock contention or crashed tasks during telemetry spikes.
The Zervox Policy Engine acts as an unbypassable firewall between LLM recommendations and your Kubernetes cluster. Even if an AI model hallucinates a dangerous command, Zervox enforces absolute blocks.
kubectl delete namespacekubectl exec -it commandsNon-blocking, event-driven remediation pipeline built with Axum, Tokio, and kube-rs.
Zervox runs all LLM recommendations through an explicit OPA Policy Engine before executing any API call. Destructive operations like namespace deletions, RBAC edits, secret reads, and container shell exec are hard-blocked by policy.
Yes! Zervox supports OpenAI-compatible API endpoints. You can point the LLM analyzer to a local Ollama instance running llama3 or mistral.
When ZERVOX_REQUIRE_APPROVAL=true is set in your environment, any non-read-only action is stored with status PENDING_APPROVAL in the SQLite database and requires explicit admin authorization before execution.