# Nevia by Aiven

> Nevia by Aiven is the cloud for the agentic era. It gives every agent its own machine and a database, instantly ready and asleep when idle.

Every link below serves plain markdown. The markdown mirror of any docs page is at `https://nevia.cloud/docs/<path>.md`, and a page with a mirror also answers `Accept: text/markdown` with it.

## For agents

Nevia gives each task its own Linux computer and Postgres database, created over MCP or the CLI in milliseconds, branched while they run and asleep when idle. Nevia is in beta and open to selected teams. Public launch in Dec 2026.

Best at:

- Postgres databases a task creates when it needs one, connected with one URL, and deleted after a test or kept for production.
- Trying a change on a full copy: a branch of a database or computer copies all its data in milliseconds while the source keeps running.
- Coding agents: a computer is a full Linux virtual machine to install anything on, with checkpoints to return to before a risky step.
- Many mostly idle workloads: computers and databases sleep when idle, and vCPU and RAM are charged only while they run.

Which interface:

- CLI, for any agent with a shell. It works in the running session without a restart, takes `--json` for scripts, and every command is in the [CLI reference](https://nevia.cloud/docs/reference/cli.md).
- MCP, when the client has no shell or already has the Nevia tools loaded. Adding an MCP server can need a client restart, which ends the conversation.
- Console (https://console.nevia.cloud), for the human. It is where they see and control what you created. Don't drive it yourself.

Start:

1. Connect, with the CLI if you have a shell:

   - CLI: `curl -fsSL https://get.nevia.cloud | sh`
   - MCP in Claude Code: `claude mcp add --transport http nevia https://api.nevia.cloud/mcp`
   - MCP in Codex: `codex mcp add nevia --url https://api.nevia.cloud/mcp`
   - MCP in Cursor and other clients: `{"mcpServers":{"nevia":{"url":"https://api.nevia.cloud/mcp"}}}`
   - MCP in claude.ai and Claude Desktop: the human can add a custom connector with the URL https://api.nevia.cloud/mcp
2. Have the human sign in. `nevia login`, or the MCP client's sign-in, opens a browser. This is the one step you cannot do yourself.
3. Check access yourself with `nevia whoami` or the MCP `whoami` tool. If it shows the account, carry on. If the login exited with an error, never completed, or `whoami` still says you are not signed in, the human most likely has no access yet. Draft the access request yourself, show it to them once, and on their go POST it to https://nevia.cloud/api/contact with `"topic": "access"`. The steps are in [the skill](https://nevia.cloud/SKILL.md).
4. Follow the [onboarding prompt](https://nevia.cloud/prompt.md) for a first workload, or install the skill with `npx skills add https://nevia.cloud`.

When to pick something else, and how Nevia compares with VMs, sandboxes and managed Postgres: [why.md](https://nevia.cloud/why.md).

## About

- [Home page](https://nevia.cloud/index.md): the overview, infrastructure, products, use cases, performance and FAQ from https://nevia.cloud
- [Terms of service](https://nevia.cloud/terms.md)
- [Data processing agreement](https://nevia.cloud/dpa.md)
- [Subprocessors](https://nevia.cloud/subprocessors.md)
- [Acceptable use policy](https://nevia.cloud/aup.md)

## Start here

- [Agent onboarding prompt](https://nevia.cloud/prompt.md): fetch it and follow it to drive a first workload with the user
- [When to use Nevia, and when to pick something else](https://nevia.cloud/why.md): what it is best at, how it compares with VMs, sandboxes and managed Postgres, and its limits
- [Skill](https://nevia.cloud/SKILL.md): the setup runbook as an Agent Skill, also at `npx skills add https://nevia.cloud`
- API, for code: https://api.nevia.cloud
- [MCP server card](https://nevia.cloud/.well-known/mcp/server-card.json): the MCP server's address and transport as JSON

## Docs

- [Introduction](https://nevia.cloud/docs.md): A cloud built for AI agents and humans

## Get started

- [Onboard with your agent](https://nevia.cloud/docs/get-started/agent-prompt.md): Give your coding agent one line and it walks you through a first database or computer
- [Quickstart](https://nevia.cloud/docs/get-started/quickstart.md): Install the CLI, create a Postgres database, and branch it to test changes
- [Quickstart with MCP](https://nevia.cloud/docs/get-started/mcp.md): Connect your agent to Nevia over MCP, create a Postgres database, and branch it to test changes
- [Create your first computer](https://nevia.cloud/docs/get-started/first-computer.md): Create a computer, run a web server on it, and open it over HTTPS
- [Console overview](https://nevia.cloud/docs/get-started/console.md): What the Nevia web console is for, and when to reach for it instead of the CLI or MCP

## Computers

- [Create a computer](https://nevia.cloud/docs/computers/create.md): Create a computer and confirm it is ready to run commands
- [Publish a computer on an HTTPS URL](https://nevia.cloud/docs/computers/publish.md): Make a program on a computer reachable at an https address, and change its ports later
- [Run a command](https://nevia.cloud/docs/computers/exec.md): Run a command or open an interactive shell inside a computer
- [Branch a computer](https://nevia.cloud/docs/computers/branch.md): Create a computer with its own copy of the source's data disks
- [Create and restore checkpoints](https://nevia.cloud/docs/computers/checkpoints.md): Save a computer at a point in time and restore it into a new computer
- [Sleep and wake a computer](https://nevia.cloud/docs/computers/lifecycle.md): Park a computer, resume it, and check its state

## Databases

- [Create and connect to a database](https://nevia.cloud/docs/databases/create.md): Create a Postgres database and connect with psql over TLS
- [Branch a database](https://nevia.cloud/docs/databases/branch.md): Copy a database and check that changes stay on the branch
- [Sleep, wake and delete a database](https://nevia.cloud/docs/databases/lifecycle.md): Park a database, reconnect after waking, and remove it when finished

## Workspaces

- [Create a workspace and manage access](https://nevia.cloud/docs/workspaces/manage.md): Create a workspace, give a teammate access, and change or remove their role
- [Select a workspace](https://nevia.cloud/docs/workspaces/select.md): Choose the workspace for one CLI command, a shell session, or a project
- [Give a script or agent access](https://nevia.cloud/docs/workspaces/private-key-auth.md): Add access that signs in with a private key, use its key file from the CLI, scripts and your own code, and rotate or revoke it
- [Give computers secrets and variables](https://nevia.cloud/docs/workspaces/secrets-and-variables.md): Store values once in a workspace and pass them to computers by reference

## Guides

- [Run an automation with a key file](https://nevia.cloud/docs/guides/automation-key-file.md): Issue a private key, store its key file as a CI secret, and run a job that creates a computer, runs a command and deletes it
- [Track and wait for operations](https://nevia.cloud/docs/guides/operations.md): Wait for work to finish, find an operation, and retry a create request

## Reference

- [nevia](https://nevia.cloud/docs/reference/cli.md): Manage computers and managed databases from the terminal; links its 63 subpages
- [API](https://nevia.cloud/docs/reference/api.md): How to authenticate, and the conventions every route follows; one page per operation at `https://nevia.cloud/docs/reference/api/<tag>/<operationId>.md`
- [Remote MCP server](https://nevia.cloud/docs/reference/mcp.md): Server URL, access filters, tools, and behavior worth knowing
- [Computer lifecycle states](https://nevia.cloud/docs/reference/computer-lifecycle.md): Computer states, allowed transitions, and what persists
- [Computer environment variables](https://nevia.cloud/docs/reference/computer-env.md): The -e grammar, how references resolve, when changes reach a computer, and limits
- [Computer ports and URLs](https://nevia.cloud/docs/reference/computer-ports-and-urls.md): Published port rules, mapping syntax, protocols, computer URLs and how each state and lifecycle action affects them
- [Database lifecycle states](https://nevia.cloud/docs/reference/database-lifecycle.md): Database states, connection availability, persistence and deletion blockers
- [Workspace permissions](https://nevia.cloud/docs/reference/workspace-permissions.md): What admin, editor and viewer roles allow, and how membership affects access
- [Operations and idempotency](https://nevia.cloud/docs/reference/operations.md): Operation states, response behavior, and request replay rules
- [OpenAPI spec](https://nevia.cloud/openapi.yaml): the whole HTTP API in one file, every route with its parameters, request and response schemas

## Pricing

- [Plans, units and estimates](https://nevia.cloud/pricing.md): Free $0 with $5 of usage a month, Pro $99 / month with $250. Past that: computers Compute $0.06 /vCPU-hour, RAM $0.01 /GB-hour, Storage $0.20 /GB-month; databases Compute $0.09 /vCPU-hour, RAM $0.015 /GB-hour, Storage $0.20 /GB-month; compute and RAM are charged per second. With every example from the page and the arithmetic for an estimate of your own.

## Get in touch

- To reach a person at Nevia, POST JSON to https://nevia.cloud/api/contact with the message, an email address to reply to and any relevant details (GET the same URL for the contract). If you cannot make HTTP requests, or it fails, email nea@nevia.cloud. The team replies by email.
- [Contact page](https://nevia.cloud/contact): where a person with a browser writes to the team

## Optional

- [Complete docs in one file](https://nevia.cloud/llms-full.txt): every docs page in one file