Kite Cloud handles code, data, and traffic for the teams that use it. Security is part of the product, not an add-on. Here is a high-level view.
Encryption in transit
Public traffic to Kite Cloud uses TLS. HTTP requests are redirected to HTTPS.
Isolation
Each deployment runs in its own container with CPU and memory limits. Project secrets are scoped to the project and injected at runtime.
Storage access
Object storage and container registries require project credentials. Access is limited to the project that owns the resource.
Production access
Only the people who operate Kite Cloud have access to production systems, and only when they need it.
Reporting a vulnerability
If you think you have found a security issue, email sales@kitecloud.net with the details. We aim to respond within two business days. Please give us time to fix it before disclosing it publicly.
More detail
A fuller security overview is available to customers and investors under NDA.
Last updated · October 2026