Trust Center
Security you can check, not just read about.
How kosa8 protects your agents, your code and your account: the controls in place, the companies that process data for us, where we stand on audits, and the documents your security review needs.
Updated 3 November 2026.
Compliance
Where we stand, plainly.
Readiness assessment under way. No audit has been completed, so there is no report yet.
No external test yet. The threat model and research paper are public.
Available to Enterprise and Government, from a private signed release channel.
A signed site licence: no activation, no check-ins, nothing leaves the building.
Controls
What is in place today.
Only controls that exist today and can be checked in the product or the code. The security page explains how each works.
Product security
Each agent in a hardware-virtualised microVM with its own kernel, disk and network
- ✓Hardware-virtualised microVM per sandbox (Apple Virtualization framework, Cloud Hypervisor on KVM)
- ✓Network rules enforced on the host, closed by default for agent and brokered sandboxes
- ✓API keys held by an egress broker outside the sandbox; the agent sees a placeholder
- ✓Risky actions held for human approval; named approvers under a signed policy
- ✓Signed, hash-chained audit log anyone can verify; CEF export for a SIEM
- ✓No telemetry, crash reporting or analytics in the software
kosa8 Cloud
Accounts, keys and sandboxes on kosa8's hosts
- ✓API keys stored only as SHA-256 hashes, scoped, with rotation
- ✓Passwords hashed with PBKDF2-SHA256 at 100,000 rounds; lockout after repeated failures
- ✓Session cookies HttpOnly, Secure and SameSite=Strict, re-checked on every request
- ✓Every query scoped to its organisation, with tests that one organisation cannot see another's
- ✓Single sign-on with Okta, Microsoft Entra ID or Google Workspace
- ✓Compute hosts reachable only through an encrypted tunnel; services bound to localhost; firewall default deny
- ✓Bot protection on sign-up; per-organisation running limits and a spending cap
Release integrity
What you install is what we built
- ✓macOS binaries signed with a Developer ID and notarised by Apple
- ✓Windows binaries Authenticode-signed; an unsigned build fails the publish job
- ✓Checksums for every release, checked by the install script
- ✓Software bill of materials generated for every release
- ✓FIPS 140-3 builds from a private, signed release channel for government
Data protection
Your code stays where it runs
- ✓On your own machines and servers, code, files, prompts and logs never reach kosa8
- ✓Encrypted in transit everywhere: TLS, HSTS preload, strict content security policy
- ✓Snapshots can be encrypted at rest with a key kept on that machine, and a policy can require it
- ✓Short-lived data pruned on schedule: sign-in tokens, attempts, function runs and billing events
- ✓We do not sell data or use it to train models
Your data
Where it lives depends on where you run it.
Everything stays on it. kosa8 sees a licence check and, on plans with limits, daily usage counts.
Sandboxes run on your servers; kosa8 Cloud holds only their metadata.
Sandboxes run on kosa8's hosts in Helsinki; account data is held by Cloudflare.
Nothing at all reaches kosa8.
Subprocessors
Who processes data for us.
These companies process data for kosa8 Cloud and billing. The software on your own machines uses none of them for your data.
| Company | Purpose | Data | Location |
|---|---|---|---|
| Cloudflare | Website, kosa8 Cloud API and dashboard, database, email routing | Account data, request logs | Global network |
| Hetzner | kosa8 Cloud compute hosts | Customer sandboxes and their snapshots | Helsinki, Finland |
| Polar | Merchant of record: checkout, subscriptions, invoices | Name, email, billing details | — |
| Resend | Transactional email (sign-in links, confirmations) | Email address | — |
Documents
For your security review.
Vulnerability disclosure
Found something? Tell us first.
Email contact@kosa8.com with a description, steps to reproduce and the output of kosa8 version --json. A person reads every report. Please give us a chance to fix the issue before you publish it, and leave other people's data out. Our security.txt has the same details.
Running a security review?
Send your questionnaire, or talk it through for 30 minutes.