Check Point AI Guardrails vs Sanctum Runtime
Check Point AI Guardrails
checkpoint.comSanctum Runtime
sanctumruntime.comSide by side
| Figure | Check Point AI Guardrails | Sanctum Runtime |
|---|---|---|
| Price from | — | — |
| Free plan | — | — |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Linux | — | Yes |
| iOS | — | Yes |
| Android | — | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · LLM Security Tools | 7.6 (#10) | 7.2 (#19) |
| Purpose | AI Guardrails analyzes submitted LLM inputs and outputs to detect prompt injection, data leakage, policy bypass attempts, unsafe content, and other AI threats. | Sanctum is a runtime trust layer that evaluates AI actions before they execute. |
Plans
Check Point AI Guardrails
- Check Point AI GuardrailsPriced on request
In their own words
Check Point AI Guardrails
Check Point AI Guardrails analyzes large-language-model inputs and outputs for prompt injection, data leakage, policy bypass attempts, unsafe content, and related AI threats. It provides threat intelligence, analytics, and developer tooling for securing AI applications. Deployment can be on premises or in a private cloud, with processed personal data kept in the customer’s controlled environment except for agreed support or maintenance. Check Point Firewalls can apply the service to generative and agentic AI traffic, including content moderation and MCP tool responses. Listed supported services include OpenAI, Claude, Gemini, and Mistral AI through developer APIs. A Copilot Studio integration combines runtime guardrails with data-loss prevention and threat prevention. The cloud service may process prompts, messages, tool information, enabled uploads, model outputs, and security analytics. Pricing is on request; retention lasts through the subscription and three months afterward.
Sanctum Runtime
Sanctum Runtime is middleware that checks actions from AI agents, robots, and automated systems before they are carried out. It evaluates proposed actions against policies and can approve them, ask for verification, or block them. Operators can review, approve, deny, or escalate actions through web and mobile workflows. The product describes behavioral monitoring, audit logs, policy history, and decision trails for runtime visibility and incident review. Its open-core runtime supports local policy checks and offline verification, including local Ollama risk scoring. Documented integrations include OpenAI, Claude/MCP, Gemini-style function calling, DeepSeek, Grok, Bedrock-compatible endpoints, NVIDIA NIM, custom agents, and local runtimes. Developers can use Node and Python SDKs, an MCP wrapper, ROS2-oriented policy packs, and smart-home and embodied-agent templates. The repository is described as MIT-licensed and self-hostable; a hosted console and proxy path are also available. The product identifies itself as embedded runtime middleware, not a standalone consumer app or robot controller. Some enterprise capabilities, including fleet orchestration and organization-wide policy sync, are private.