What Cynative Does
Cynative works by combining four components:- Model — Your frontier LLM (Anthropic, OpenAI, Amazon Bedrock, Google Vertex, and more) drives the research loop, reasoning through questions, writing investigative code, and synthesizing findings.
- Sandbox — The model generates and runs JavaScript in an ephemeral, isolated sandbox that has no direct network or host access of its own. Tool functions (e.g.
http_request) are exposed as async JavaScript functions, allowing the model to loop, filter, and fan out API calls concurrently usingmapConcurrent— returning only what itconsole.logs, keeping research fast and token-efficient. - Action gate — Every operation is resolved to its required IAM actions, derived from the cloud providers’ own API definitions, and authorized against a read-only policy (
SecurityAuditfor AWS,roles/viewerfor GCP,Readerfor Azure) before any credential is attached. The gate fails closed on anything it classifies as a write. - Connectors — Built-in connectors for AWS, GCP, Azure, EKS/GKE/AKS, self-managed Kubernetes, GitHub, and GitLab pick up the credentials already in your shell. Network access is pinned per-connector — your agent reaches your infrastructure and nothing else.
Key Capabilities
45 Built-in Agents
Pre-reviewed, embedded agents for AWS (20), Azure (11), GCP (5), GitHub (4), and Kubernetes (5) — covering privilege escalation, public exposure, supply chain, detection coverage, and more.
Read-Only by Construction
Every call is gated before a credential is attached. The action gate checks required IAM actions against a security-audit policy and fails closed —
SecurityAudit blocks secretsmanager:GetSecretValue where a simple read filter would pass it.JS Sandbox for Concurrent Research
The model writes JavaScript that runs in an isolated sandbox. Independent API calls fan out concurrently with
mapConcurrent, following pagination and aggregating results — far fewer tokens and faster answers than one-call-at-a-time approaches.Multi-Cloud Connectors
Native connectors for AWS, GCP, Azure, EKS, GKE, AKS, self-managed Kubernetes, GitHub, and GitLab. Uses the credentials already in your shell — no separate credential store.
Any LLM Provider
Powered by the embedded Bifrost SDK. Supports OpenAI, Anthropic, Azure OpenAI, Amazon Bedrock, Google Vertex/Gemini, Cohere, Mistral, Groq, Ollama, vLLM, and more.
Fail-Closed Audit Log
Every tool call is recorded to a persistent JSONL audit log (
~/.cynative/audit.log). If a call can’t be recorded, the run aborts. Agent runs also record the agent name, source, and file digest — every finding traces back to its exact prompt.How It Differs from Coding Agents and MCP Servers
Cynative is purpose-built for security research, not general automation. Here’s how it compares to reaching for a coding agent with MCP servers:What Your Agents Get
Every agent — built-in or custom — runs with the same set of capabilities:- Code-to-runtime: Reasons through AWS, GCP, Azure, any K8s, GitHub and GitLab
- Sandbox: Generates and runs code to research at scale, with no network or host access of its own
- Action-gate: Resolves every call to its required IAM actions and applies a read-only policy before a credential is attached
- Evidence-backed: Cross-checks to verify every finding
- Sovereign: One binary, your model, your data stays yours

