Security
Security at Kairo Technologies.
How to report a problem to us, and how KAIRO is designed to keep each person's work separate from everyone else's.
Reporting a vulnerability
If you believe you have found a security issue in KAIRO Cloud OS or on this website, please tell us privately by email. Do not open a public issue or post the details publicly before we have had a chance to respond.
A useful report includes:
- What you found and where.
- The steps needed to reproduce it.
- What an attacker could do with it, as far as you can tell.
Send reports to founder@thekairo.dev.
Workspace isolation
KAIRO Cloud OS runs each workspace in its own container. The design assumes workloads may be hostile and keeps them apart.
- Workspaces run in isolated containers, with network isolation between them.
- CPU, memory, and storage limits are enforced per workspace.
- Containers do not run in privileged mode.
Accounts and sessions
- Passwords are hashed with Argon2id and are never stored in plain text.
- Sign-in sessions use short-lived access tokens that are renewed with a separate refresh token.
The service itself
- Requests to the KAIRO API require authentication.
- Rate limiting and input validation are applied to API endpoints.
- Cross-origin access is restricted to approved origins.
This website
thekairo.tech is an informational site. It has no accounts and no forms, and it does not set cookies or run tracking scripts.
Certifications
We do not currently hold any third-party security certifications, and we will not claim one before we have it. If that changes, it will be stated here.

