SHRIKEShip AI Agents That Act — Without Losing Control.
Every prompt, tool call, and response checked against your policy before it executes. Evidence handed to you, out of the box.
The agent's scope is declared at spawn: purpose, allowed tools, expiry. In-scope work flows; the one out-of-scope call waits for a human. You declare; Shrike enforces.
Discover
Every agent, model, and MCP tool in your estate, including the ones nobody registered.
Platform →Govern
Allow, redact, require approval, block, plus declared agent scopes. You declare; Shrike enforces.
Drive the live sandbox →Prove
Every verdict mapped to SOC 2, HIPAA, GDPR, PCI DSS, ISO 27001, and OWASP, with exportable evidence.
Compliance →Declare what the agent is for. Shrike holds it to that.
Give any agent a scope at spawn: a purpose, the tools it may use, and when it expires. Live today on every channel: REST, SDKs, and MCP.
A scope, at spawn
One declaration, from you or your agent framework, never from the agent's own reasoning.
Server-side, every call
Tool calls outside the declared scope route to human approval before they execute. Expired scopes stop acting silently: the check runs in the scan pipeline itself, so every channel inherits it. The model can't talk its way around a boundary it never touches.
Scope cuts both ways
The declared purpose also grounds Shrike's semantic analysis: an agent doing exactly what it was scoped to do isn't second-guessed as an attacker. More control and fewer false alarms, from the same declaration.
Named-tool allowlists and expiry ship today. Resource-level read / write / approval statements (scope as code) are on the roadmap. Scope declaration guide →
Measured against the production scan path on public benchmarks (AdvBench, HarmBench, JailbreakBench, ADR-Bench). False positives reported at message and session level; errored probes re-run, never dropped.
9 layers · 6 integration channels · 5 compliance catalogs · 1 line of code to begin
NIST AI RMF AlignedSOC 2 AlignedFedRAMP Moderate (roadmap)EU AI Act AlignedFeeds Splunk · CrowdStrike Falcon · Microsoft SentinelDiscover your AI, govern what it does, and prove it.
Security Posture Management
Understand your AI risk surface before it becomes an incident.
- Shadow AI discovery
- Model inventory & risk scoring
- Posture monitoring
- Misconfiguration detection
Runtime Policy Enforcement
Your policy, enforced at every agent action: allow, warn, require approval, or block before it executes.
- Allow / warn / require-approval / block, enforced server-side
- MCP tool-call & command governance
- Prompt & response inspection · PII redaction
- LLM Gateway
Security Operations Center
Investigate, respond, and report in one place.
- Real-time dashboard & analytics
- Incident management
- Red team testing (6,500+ patterns)
- Audit trails & compliance reports
Built on original research across six foundations: cognitive detection, hardware-isolated enforcement, self-approval prevention, session-aware correlation, security knowledge graph, and runtime-neutral threat adaptation.
Meet your enterprise where it is.
No rip-and-replace. Six integration channels: REST, MCP, LLM Gateway, and Python, TypeScript, and Go SDKs. Fail-closed by default: when Shrike can't decide, the agent stops.
Start free. Self-serve through Team. Procurement-ready Enterprise.
For developers getting started with AI security.
- 1,000 scans / month
- Real-time threat detection
- MCP server + REST API + SDKs (Python, TypeScript, Go)
- Community support (GitHub Discussions)
For individual developers piloting AI security in production.
- Everything in Community, plus:
- 25,000 scans / month
- Full 9-layer pipeline: LLM analysis, response intelligence, multi-turn session memory
- Human-in-the-loop approval workflows
- Compliance dashboards + audit trail
- Priority email support
For security teams governing AI across a growing organization.
- Everything in Pro, plus:
- 150,000 scans / month
- SSO via Google Workspace + GitHub OAuth
- Multi-user RBAC up to 25 seats
- 90-day audit log retention
- Splunk + webhook SIEM connectors
- Slack + email alert routing
- Priority email support (8-hour SLA)
For organizations governing AI across the enterprise.
- Everything in Team, plus:
- 1M+ scans / month + custom seat count
- All SIEM connectors (Splunk, CrowdStrike, Sentinel, custom)
- SAML SSO + custom IdP federation (Okta, Azure AD, Auth0)
- Air-gapped, VPC, sovereign, and TEE deployment options
- Custom policy authoring: regex rules live on every channel within 60s, no redeploy
- Compliance evidence package (SOC 2, HIPAA, ISO controls mapping)
- Dedicated support engineer + SLA
- Available on GCP Marketplace
Straight answers to what buyers ask us most.
What is action governance for AI agents?
Action governance evaluates what an AI agent is about to do (each tool call, shell command, SQL query, API request, and agent-to-agent message) against your policy, and allows, blocks, or escalates it in real time before it executes. It goes beyond scanning the prompt to governing the action the prompt triggers.
How is Shrike different from a prompt scanner?
Prompt scanners inspect input text for known-bad patterns. Shrike does that too (it's the deterministic floor), then adds the action plane: it governs the tool calls and side effects an agent takes, correlates threats across a full multi-turn session, and enforces scope and human-in-the-loop, server-side where the model can't talk its way around it.
What does Shrike cost?
Community is free: 1,000 scans/month, real-time threat detection, no credit card. Pro is $99/month (adds LLM analysis + multi-turn session memory (the full 9-layer pipeline) plus human-in-the-loop approvals and a compliance dashboard). Team is $499/month (SSO, RBAC, SIEM connectors). Enterprise is custom (SAML, air-gapped/VPC/sovereign deployment, DPA).
Can I restrict which tools an AI agent is allowed to use?
Yes. Declare a scope for any agent: a purpose, a named-tool allowlist, and an expiry. Tool calls outside the scope route to human approval before they execute, expired scopes stop acting silently, and the declared purpose also grounds Shrike's semantic analysis so in-scope work isn't flagged as an attack. Available today via the REST API, the SDKs, and the MCP scan_declare_scope tool.
Which AI providers does Shrike work with?
Any of them. Shrike is model- and vendor-agnostic: it works across OpenAI, Anthropic, Google, Mistral, and open-source models, over MCP, REST, CLI, and A2A. Drop-in SDK wrappers ship for Python, TypeScript, and Go.
Where does Shrike deploy?
Cloud SaaS, inside your VPC, air-gapped, or sovereign/in-region. Hardware-enclave isolation (AMD SEV-SNP) is available under Enterprise engagements that require it. Adding or switching a model provider requires no changes to your Shrike policies.
Does Shrike retain my data?
No content retention by default. Safe interactions are stored as a cryptographic hash plus metadata; the original content isn't kept. Full violation records are retained, encrypted at rest, for audit. We don't keep what we don't need.
Is Shrike SOC 2 certified?
Not yet. Shrike is built to SOC 2-aligned controls, with certification targeted for 2026. Shrike helps you document your own compliance posture (GDPR, HIPAA, ISO 27001, SOC 2, NIST); it is not itself a certification. See the Trust Center for current status.
Begin where trust begins: just watching.
Observe mode records what your agents actually do, with no blocking and no friction, until you decide what policy should say. Most teams see their first surprise within a day.