Security & accountability

Not “trust us.” Just verify us.

Most AI products call themselves “safe” and mean a paragraph in a system prompt asking the model to please behave. Imperal is a fully decentralized system protected by crypto-resilient encryption protocols across every contour, where every control on this page is enforced by the runtime itself, not requested of the model.

Architectural, not promised

Alignment enforced by the runtime, not requested of the model.

Most “guardrails” are strings of text in a prompt. These are not that, each one is a mechanism you can see fire the moment you use the product.

Propose, confirm, execute

Every tool declares an action_type of read or write at the SDK level, not a prompt instruction, a runtime contract. A write that is destructive or consequential stops and describes the exact action in plain terms before it runs. Not a blanket “yes, you can do things”, a confirmation tied to that one proposal.

Checkpoint before every write

Reversible actions are checkpointed first, so “undo” is a real command and not a promise, the same rule Webbee Code runs in its terminal (Default mode). Anything she cannot undo, she stops and asks you first, by design, not by good behaviour.

Durable, append-only audit log

Every consequential action, every email actually sent, every automation that fired, every tool call an extension made, is recorded and never deleted. Not a debug log someone can quietly prune: the record IS the accountability mechanism.

No fabricated actions

The agent acts against your real, connected systems, not against a guess. If a tool call fails or a system is unreachable, that is what gets reported. An agent that quietly invents a plausible-sounding result is a liability wearing a UI; the runtime is built to surface failure, not paper over it.

Vault, Decentralized Mesh & Cloud Defense

Six cryptographic layers protecting your keys, cloud, and network.

Plain answers to the questions every founder, CTO, and security reviewer asks before connecting production infrastructure.

Zero-Plaintext Secret Broker

Tenant Vault (AES-256-GCM)

Every workspace runs inside a dedicated cryptographic vault.

API keys, OAuth tokens, SSH credentials, and live session context are encrypted at rest with AES-256-GCM using per-tenant key envelopes. When Webbee or an imperal-mcp agent calls a tool, the broker injects credentials inside the isolated execution boundary - raw secrets never enter LLM prompts, context windows, or chat logs.

TLS 1.3 + Ed25519 Node Auth

Decentralized Zero-Trust Mesh

No central honeypot and no shared execution state.

Imperal separates Gateway routing, Cognitive Kernel orchestration, Vault storage, and Worker execution across a decentralized, crypto-resilient node topology. Every inter-node hop is authenticated over mutually verified TLS 1.3 and signed with Ed25519 keys, so compromising or saturating any single edge never exposes tenant workloads.

33 Local Tools + Deterministic Guards

Local-First Exoskeleton & Cloud Defense

33 of 34 Exoskeleton tools run on your machine; cloud calls pass strict perimeter guards.

Local code intelligence (AST symbol graphs, blast-radius analysis, and shadow-git checkpoints) executes 100% on your machine without sending source code to the cloud. When cloud tools run, every request passes through automated PII and secret scrubbing before outbound LLM calls, deterministic shell guards that block destructive commands (unverified rm, DROP, or release symlink mutations), rate-limiting at the edge, and strict per-tenant Linux namespace and cgroup isolation.

Zero Model Training on Your Data

Your Keys, Your Models (BYOLLM)

Route through Anthropic, OpenAI, Google, xAI, or private endpoints.

Bring your own provider API keys in the panel or use Imperal managed routing. Your prompts, code graphs, and business records are never used to train foundation models. You can switch models per task or revoke provider access in one click without losing your Vault memory.

Least-Privilege Access

Scoped, Short-Lived Execution Tokens

Every app connector and SSH target is scoped to exact capabilities.

Connecting Stripe, GitHub, Google Workspace, or a production SSH server grants only the specific read or write scopes you authorize. Execution tokens are short-lived, bound to your tenant ID, and can be rotated or revoked immediately from the Imperal Panel.

SHA-256 + Ed25519 Receipts

Hash-Chained Forensic Audit Ledger

Every read, write, and approval is provable and tamper-evident.

Every action across Web Panel, Webbee Code terminal, Telegram, and imperal-mcp produces a structured receipt containing the actor, tool, arguments hash, approval signature, and SHA-256 link to the previous receipt. Export your ledger anytime for SOC 2, ISO 27001, or internal security audits.

Defense-in-Depth Cloud Contour

How every request travels through the Imperal Cloud OS.

Layer 01

Pre-Flight PII & Secret Scrubbing

Before any context reaches an external LLM, the Exoskeleton and Gateway scrub raw credentials, bearer tokens, private keys, and sensitive PII patterns automatically.

Layer 02

Isolated Worker Sandboxes

Tool calls and SSH commands execute inside isolated per-tenant worker boundaries with strict resource ceilings, filesystem checkpoints, and instant rollback capability.

Layer 03

Cryptographic Consensus & Verification

State-changing operations require explicit human confirmation or policy-bound verification, sealing the outcome into your tenant's append-only cryptographic ledger.

Marketplace review

Every extension is gated before it reaches you.

KAV, the Kernel Advanced Validator, is a three-phase automated gate every developer submission passes through before a single user can install it.

1

Static analysis

Automated checks across the submitted code before it ever runs, declared scopes match actual behaviour, no undeclared network calls, no secrets committed, dependency and license checks.

2

Behavioural sandbox

The extension runs in an isolated environment against synthetic data. Its actual tool calls are compared against what it declared it would do.

3

Manual review

A human reviewer looks at anything the automated phases flag, plus every extension requesting a destructive or high-trust scope, before it goes live on the marketplace.

Security FAQ

Frequently asked security questions.

Everything you need to know about our Tenant Vault, decentralized mesh, cloud isolation, and cryptographic audit receipts.

How does the Imperal Tenant Vault protect my API keys and SSH credentials?
Every workspace has an isolated Tenant Vault encrypted at rest with AES-256-GCM and per-tenant key envelopes. When Webbee or a connected agent (via imperal-mcp) runs a tool, the kernel's credential broker injects the secret only at the network execution boundary. Neither the LLM nor the chat transcript ever sees your raw API keys, OAuth tokens, or SSH private keys.
What makes Imperal's network architecture decentralized and crypto-resilient?
Imperal splits ingress gateways, orchestration kernels, encrypted vaults, and execution workers across separate, mutually authenticated nodes over TLS 1.3. Every cross-node command and receipt is signed with Ed25519 and chained with SHA-256 hashes, eliminating single-point-of-failure honeypots and ensuring tamper-evident execution across the entire cloud contour.
Can an AI agent execute destructive commands on my servers or database without permission?
No. Imperal enforces a protocol-level Propose -> Confirm gate (Kernel Action Verification) outside the model's context window. Read-only operations execute safely, while writes, deployments, billing actions, and server mutations pause and raise a cryptographic approval card in the Web Panel, Terminal, or Telegram. In addition, runtime guards block unverified destructive patterns like rm -rf or DROP TABLE.
Is my company data or source code ever used to train AI models?
Never. Imperal does not train models on your prompts, files, code graphs, or tool outputs. When you use managed models or bring your own API keys (BYOLLM) for Claude, GPT, Gemini, or Grok, requests are transmitted over zero-data-retention commercial API channels with pre-flight secret scrubbing.
How is security enforced when I connect external agents via imperal-mcp (Exoskeleton)?
When Claude Code, Cursor, Windsurf, Codex, or Gemini CLI connects through imperal-mcp, 33 of the 34 Exoskeleton tools run locally on your machine at $0 without sending raw source code to the cloud. When an agent invokes cloud Vault memory or any of the 300+ marketplace extensions, the local MCP bridge authenticates with a scoped tenant token and routes cloud tool calls through the exact same Tenant Vault, PII masker, and Propose -> Confirm approval gates as Webbee. You get full multi-agent power without scattering raw .env secrets across developer laptops.
Can I audit or export every action taken by AI agents in my workspace?
Yes. Every tool call, parameter summary, human approval, and execution result is recorded in a hash-linked SHA-256 and Ed25519-signed receipt log inside your panel. You can inspect receipts in real time, roll back file mutations, or export the audit trail for compliance reviews.

See it yourself

Read the mechanism. Then try it.

Every control on this page is documented, and every one of them fires the moment you connect a real tool and give Webbee a real command.

Read the security guide

Procurement, compliance, or on-prem questions? Talk to us.