# Security and isolation

URL: https://heaven.dev/docs/security
Updated: 2026-11-21

Each Computer is an isolated Linux virtual machine with its own disk and execution environment. Heaven controls resource access separately from the operating system inside the Computer.

## Isolation and ownership

Root access gives control over the Computer's software and files. Heaven permissions govern actions such as sharing, transferring and resizing resources.

[Organization admins and the billing owner](https://heaven.dev/docs/organizations#membership-and-roles) have Owner authority over the organization's Computers. Members receive access through ownership, teams and shares.

Connections between Computers require explicit authorization through [networking integrations](https://heaven.dev/docs/networking#outbound-and-peer-connections).

## Encryption

Heaven encrypts Computer disks and their [off-site backups](https://heaven.dev/docs/snapshots#backups) at rest. The backup data is already encrypted when Heaven sends it to off-site storage.

## Sharing

**Site only** grants access to the main website. **Site and SSH** adds root access, the browser terminal and development ports.

A root user can read credentials stored inside the Computer and change or delete its files.

A public website accepts anonymous visitors. Development ports require ownership or root access.

After removing access, rotate application credentials the recipient could read.

## Credentials

An [API key](https://heaven.dev/docs/reference/api-keys/create) is limited by its creator's permissions and its assigned commands and resource scopes. A key lasts until you remove it. Set **Expiration** to end its access at a chosen time, up to 365 days ahead. A key created through a `heaven login` or MCP sign-in can't outlive that sign-in.

A site token authorizes requests to a private website. Removing its signing SSH key revokes the token.

Use [integrations](https://heaven.dev/docs/integrations) to give Computers access to external services while Heaven holds the credentials.

Snapshots and copies contain the credentials saved on their disks. Review those credentials when reusing a saved environment.

Only enter Heaven credentials on Heaven's sign-in pages. Websites at `NAME.heaven.dev` contain customer applications.

## Signing in

Sign in to Heaven with a code or link sent to your email, a Google or GitHub account, or a passkey. Connect Google or GitHub and add passkeys in [Settings](https://heaven.dev/dashboard/settings). [Read your sign-ins](https://heaven.dev/docs/reference/account/sign-in-view), [set how long a sign-in lasts](https://heaven.dev/docs/reference/account/sign-in-lifetime) or [sign out everywhere](https://heaven.dev/docs/reference/account/sign-in-end-all).

## Agent sign-in approval

Signing an agent in with your Heaven account takes your approval in a browser:

- `heaven login` shows a code. Approve it in your browser to sign in that machine's CLI, and the agents that use it, with your permissions for 90 days.
- A client that connects to the [hosted MCP server](https://heaven.dev/docs/mcp#hosted-server) signs in through Heaven with OAuth, and you approve the connection in your browser.

Revoke a sign-in or a connection in [SSH & API keys](https://heaven.dev/dashboard/settings/keys). To give an agent fewer permissions than yours, give it a [restricted API key](https://heaven.dev/docs/security#credentials) instead.

## Support access

[Support root access](https://heaven.dev/docs/reference/computers/grant-support-root) authorizes Heaven's operators to read and change a specific Computer's software and files. Its owner can grant and revoke access for an investigation.
