--- title: Security overview description: How Kaviris keeps apps apart, controls what they reach, checks every deploy, and backs up your data. --- # 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](concepts/contract.md), 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](refusals/vuln_fixable.md) 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](refusals/index.md). 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](concepts/secrets.md)). 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 - Sign-in with a passkey; no passwords to leak. - Coding agents get short-lived access tokens (10 minutes), only for the permissions you granted, and only for your account. You can see and revoke each connected agent. - Deleting apps and rolling back are not given to agents automatically, and always need a confirmation. Connecting GitHub and exporting a database are done by a person in the portal ([roles](concepts/organisation.md)). - Support can look at your app only with a time-limited case grant you give ([Support](support.md)). - Every action is recorded: who, through which agent, what changed. ## 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](concepts/backups-and-restore.md)). ## Automatic security rebuilds Every night Kaviris scans every app's image, sleeping apps too, and sorts what it finds into two piles: - **The platform's part** (the operating system packages and the language runtime Kaviris provides). When a security fix is out, Kaviris rebuilds your app from your last approved source, puts it through the whole gate again, and releases it. Your app's card says so, for example *"security update: bsdutils 1:2.41.5-0+deb13u2"*. If the rebuild fails a check, the version you had keeps running and you are told what happened. - **Your part** (the libraries in your lockfile, and programs they bring along, such as esbuild). Kaviris never changes those for you. They show on your app's card as advice with the upgrade ready to apply ([vuln_fixable](refusals/vuln_fixable.md)), and you are notified when the list changes. 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](https://app.beta.kaviris.com/report) ([contact points](contact.md)).