Your data stays in your network
The runtime runs inside your environment. AgentKube holds your organization, members and licence, and nothing of your customers’.
Two sides: your runtime, where every conversation, memory, knowledge index and data store lives, under your controls; and the AgentKube account service, which holds metadata only and is built to a SOC 2 and HIPAA control list.
Runtime, conversations, memory files, knowledge index, data stores, provider keys.
Version check-ins and usage counts. No conversation content, no agent names unless you opt in.
Sign-in through your identity provider, owners and members, API keys with scopes, domain restrictions.
Never root. No source maps. Our builder prompts are not in it; they are served per session under your licence.
The account service
Built to a control list so certification is possible later.
Questions about security?
Our security documentation is available under NDA; ask for it in the contact form.
Questions people ask
What data does AgentKube receive from my runtime?
Version check-ins and usage counts: how many agents, by type, sessions in the last day, week and month, which providers by name, and the URLs of your services. Never conversations, memory, keys, files or agent names unless you opt in.
Is AgentKube SOC 2 or HIPAA certified?
Not yet. The account service is built to a SOC 2 and HIPAA control list and runs on Google Cloud services covered by a BAA; certification is on the roadmap. Your runtime, where PHI would live, runs under your own controls.
Does the container run as root?
No. The image runs as an unprivileged user and works under OpenShift’s arbitrary user ids.