Security isn't a feature. It's the foundation.

AI agents that can browse the web, execute code, and access your tools need serious guardrails. Here's how we build them.

Per-tenant isolation

Every KiwiClaw agent runs in its own isolated container with a dedicated filesystem and workspace — separate from other tenants.

Your agent's data, configuration, and conversation history are scoped to that tenant and are not shared with any other tenant.

Sandboxed execution

Browser automation and code execution run inside your agent's own container, under kernel-level sandboxing (gVisor) for defense in depth. If your agent runs a script or drives a headless browser, it happens in an environment scoped to your agent.

The execution environment is disposable and contained. No sandbox is unbreakable, so we pair it with capability and egress controls rather than claiming isolation is absolute.

Managed skills marketplace

341 malicious skills have been found in the OpenClaw ecosystem. Skills that exfiltrate data, install backdoors, or run cryptominers. If you self-host, you're on your own to vet them.

Marketplace publication uses an administrative submission and approval workflow. It is not a security certification and does not replace review of the publisher, code, permissions, credentials, and network access before installation.

Encryption

Public traffic and managed database connections use TLS. Provider credentials supplied by BYOK users are encrypted with AES-256-GCM before database storage and are decrypted only for authenticated runtime configuration.

Tenant runtime files live on persistent host storage. KiwiClaw does not currently make a blanket encryption-at-rest claim for every runtime file.

Managed LLM users never see or handle API keys at all. Their requests are authenticated via per-tenant JWTs and routed through our internal LLM proxy. Pooled API keys live only in the proxy and are never exposed to tenant machines.

BYOK is the exception: your own provider key is placed in your own container so your agent can call your provider account directly. How the credential flow works, and what it does and doesn't cover.

Audit logs

KiwiClaw records application audit events for account, agent, configuration, and administrative activity. Audit views and export endpoints are available.

The current audit store is not an immutable write-once ledger and does not include turnkey SIEM delivery, customer-configurable retention, or compliance-ready evidence packages.

Role-based access control

Enterprise teams get RBAC with granular permissions. Admins configure agents and skills. Members can chat and use the agent. Viewers can read conversation history but not interact.

Invite teammates, assign roles, control who can do what. No more sharing a single login or worrying about interns accidentally reconfiguring the agent.

Hosting location

Production tenant workloads currently run in Falkenstein, Germany. Customer-selectable US, EU, or APAC regions are not generally available.

Control-plane vendors and LLM providers may process data in other locations under their own terms. Request the current data-flow and subprocessor picture before sending regulated data.

Compliance gaps

KiwiClaw is not SOC 2 certified, does not sign HIPAA BAAs, does not currently offer a standard DPA, and does not claim that a customer's use is GDPR compliant.

The team can document the technical controls that are live today, but your organization must complete its own legal, security, and vendor-risk review.

Responsible disclosure

Found a vulnerability? We take security reports seriously and respond within 24 hours.

Email hi@kiwiclaw.app with details. Include steps to reproduce, impact assessment, and your contact information. We'll acknowledge receipt within 24 hours and provide a timeline for resolution.

We do not pursue legal action against researchers who report in good faith.

Frequently Asked Questions

How does KiwiClaw isolate tenants from each other?

Every KiwiClaw agent runs in its own isolated container with a dedicated filesystem and workspace, separate from other tenants. Your data, configuration, and conversation history are scoped to your tenant and not shared with any other tenant.

Is code execution safe on KiwiClaw?

Code execution and browser automation run inside your agent's own container, under kernel-level sandboxing (gVisor) for defense in depth. The execution environment is disposable and scoped to your agent. No sandbox is unbreakable, so we pair it with capability and egress controls rather than claiming isolation is absolute.

Does KiwiClaw support SOC 2 or HIPAA compliance?

No. KiwiClaw is not currently SOC 2 certified, does not sign HIPAA BAAs, and does not claim GDPR compliance. Do not process PHI and complete a legal and vendor-risk review before regulated use.

How does KiwiClaw handle marketplace skills?

Marketplace publication uses an administrative submission and approval workflow. KiwiClaw does not claim that every skill passes automated security scanning. Review the publisher, code, permissions, credentials, and network access before installation.

Evaluate the controls that are live.

gVisor isolation, authenticated ingress, enforced egress, credential encryption, audit events, and an explicit list of current gaps.