Portal

Security overview

Apps built with AI often go online with keys in the code, outdated libraries and no backups. Kaviris is built so that the safe way is the default and doesn't need to be learned first.

Every app in its own micro-VM

Each app runs in its own lightweight virtual machine (Kata Containers), with its own kernel. In a typical container platform, apps share the host's kernel, and one kernel bug can let one app reach another. Here a break-out would first have to escape a virtual machine.

Apps also get their own network identity, and traffic between parts of the platform is encrypted and authenticated.

Nothing gets out unless the contract says so

Outbound traffic is denied by default. An app can reach only the hosts named in its contract, which you approved. If an attacker gets into an app, they can't send your data to a server of their own, and they can't use your app to attack others.

We don't open or inspect your encrypted traffic: the allowlist limits where it can go.

Every deploy goes through the gate

Before an app goes live, Kaviris:

  1. Builds it in an isolated build machine.
  2. Scans the source and the built image for secrets (keys, passwords, tokens) and for dependencies with known vulnerabilities. Secrets in code stop the deploy. Vulnerable libraries don't: which ones you use is your choice, so you get a recommendation with a ready-made upgrade patch instead.
  3. Runs it in a sealed test machine and records which hosts it tries to reach and which ports it listens on.
  4. Compares all of that with the contract, and refuses what doesn't fit, with a fix.
  5. Signs the image. The cluster runs only images Kaviris has signed, so nothing can be slipped in around the gate.

Secrets are write-only

Secret values go from your machine straight to Kaviris (Secrets). They are delivered to your app as environment variables. Kaviris has no screen, command or support tool that shows them, to you or to us. The API service itself holds no permission on secrets at all; writes go through a separate service that can set one value and nothing else.

Accounts and agents

Backups

Databases are backed up continuously and every night, disks nightly. Restore tests are not yet run on every database: every night we restore a test app's and the platform's own into a separate sealed place and check they work (Backups and restore).

Automatic security rebuilds

Every night Kaviris scans every app's image, sleeping apps too, and sorts what it finds into two piles:

Rebuilds happen a few at a time, worst first, at most once a day per app, never replace a deploy of yours that is in progress or waiting for approval, and don't count against your deploys per day.

Reporting a vulnerability

Found a security problem in Kaviris? Please tell us at security@kaviris.com before telling anyone else. We will answer quickly. Machine-readable: https://app.beta.kaviris.com/.well-known/security.txt. Illegal content or abuse on an app someone hosts here is not a vulnerability: use the notice form (contact points).

This page as Markdown