# Nevia by Aiven > For the complete documentation index, see [llms.txt](https://nevia.cloud/llms.txt). This page's HTML version: https://nevia.cloud/ ## 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). ## Cloud for the agentic era Infrastructure now starts from intent. Nevia gives every agent its own machine and a database, instantly ready and asleep when idle. ## Overview Nevia is the cloud rebuilt from first principles, for humans and agents. ### Computers and databases Start one for every task, branch it while it runs. ### Operated through MCP, CLI or API You and your agents create, branch, sleep and delete infrastructure. ### Cloud primitives Compute, storage and networking, built and operated by Nevia. ### Flexible deployment Runs on Nevia's servers, in your cloud account or on-prem. ## Infrastructure Familiar primitives, rethought for this decade ### Compute Machines that wake the moment work arrives and rest when it ends, with the isolation of a classic VM. Nevia’s default compute is a Firecracker microVM. Each microVM runs on a bare-metal host and is ready in milliseconds. Compute scales to zero when idle and scales up with demand. Virtual machines for larger, long-running workloads are on the roadmap, with startup times measured in seconds. | | microVMs | Virtual machines | | :-- | :-- | :-- | | What it is | A lightweight Firecracker virtual machine | A larger virtual machine with a fixed compute allocation | | Best for | Apps with variable demand and workspaces that can sleep when idle | Always-on applications with steady demand | | Startup time | Milliseconds | Seconds | | Scale to zero | Yes | No | | Scales with demand | Yes | No | | Size | Up to 16 vCPUs | Up to 160 vCPUs | | Status | Available | Roadmap | #### MicroVMs Each workload runs in its own microVM with its own kernel, and workloads are isolated by hardware virtualisation rather than by shared-kernel containers. MicroVMs run directly on bare-metal hosts without an extra hypervisor layer. Your application runs inside the microVM and can be deployed from an OCI image. _Over a day, the vCPU a machine holds rises and falls with its load, and drops to none while it sleeps._ Compute is separate from storage. A machine's data lives on a replicated volume in the region, not on its compute host. This lets the machine sleep, wake and branch without moving data. ##### Benefits - **Starts in milliseconds:** Nevia allocates compute from pre-warmed pools, with startup times in the low hundreds of milliseconds. - **Scales to zero:** Sleeping machines do not consume vCPU or RAM. - **Isolated by default:** Each workload gets its own kernel and its own virtual hardware, with nothing to configure. _A machine's vCPU and RAM are in use while it is active, drop to zero while it sleeps, and return when it wakes._ ##### Purpose-built orchestration Nevia's purpose-built orchestrator manages each microVM's lifecycle and enforces isolation between workloads. Every machine is isolated from its neighbours through hardware virtualisation, control traffic stays off the guest's network interface, and ingress and egress are governed by declarative rules. #### Virtual machines Some workloads are not bursty, like always-on applications with steady demand or services you want sized once and left running. For these, we are building a virtual machine offering with a stable footprint. It runs on the same engine as microVMs, starts in seconds and supports the same branching capabilities. ### Storage Disks that branch like code in under a second, so every experiment starts from a copy of real data. Nevia offers two storage primitives: Block storage for data that needs speed and branching, together with S3-compatible object storage. | | Block storage | Object storage | | :-- | :-- | :-- | | What it is | A block volume from a pool of SSDs, mounted as a disk | S3-compatible object storage | | Best for | Working directories, databases, anything latency-sensitive | Files, artifacts, backups, large blobs | #### Block storage Every VM gets a data disk that behaves like a local NVMe drive. Underneath, it is a volume backed by a pool of SSDs with built-in replication, connected to the VM over a high-speed private network. Compute and storage always sit in the same region to keep read and write latency low. _Compute runs above a separate tier of block storage, a pool of replicated SSDs in the same region; a branch gets a volume that shares its parent's blocks and uses extra storage only for new or changed blocks._ Copy-on-write is built into every volume. Snapshots and clones are metadata operations and a clone shares every block with its parent until one side writes. ##### Benefits - **Sub-second branching:** Create a branch from a snapshot in under a second, whether it's a 1 GB workspace or a 1 TB database. No data is copied. - **Pay only for the delta:** A branch shares its parent's data and only uses extra storage for new or changed blocks. ##### Resilient out of the box Data is replicated across independent drives and spread across many storage nodes by default, with nothing to configure. After a failure, the system automatically rebuilds the affected replicas. Storage is separate from compute, so your data survives if a compute host fails or is replaced. #### Object storage (roadmap) Use object storage for files, build artifacts, exports and large blobs that you write once and read many times. It is S3-compatible, so existing tools and SDKs work out of the box. ### Networking Every machine gets its own name and a TLS endpoint from the moment it starts, the way servers always did. Every Nevia Computer and Database gets its own name, URI and ready-to-use endpoint secured with TLS. Private networking and egress controls are on the roadmap. | | Public endpoints | Private networking | | :-- | :-- | :-- | | What it is | A DNS name and TLS endpoint for every machine | Private connections between your Computers and Databases | | Best for | Apps, APIs and databases reached from anywhere | Applications that communicate across Computers and Databases without public endpoints | | Protocols | HTTPS (HTTP/1.1, HTTP/2), Postgres over TCP with TLS | — | | Status | Available | Roadmap | #### Public endpoints Each machine is named in DNS and reached through an ingress proxy on its host, which routes traffic to the destination VM. Computers get HTTPS URLs for the ports they publish, with TLS handled for you. Databases are reached via a standard Postgres TCP connection, with TLS passed straight through to the database instance. _A connection runs from the client through the machine's DNS name and the ingress proxy on its host to the machine, secured with TLS and waking it if it sleeps; control traffic (shell, console, files) takes a separate channel._ ##### Benefits - **Ready to connect:** Create a machine and it is already addressable. No load balancers, certificates or DNS records to set up. - **Wakes on connection:** A sleeping machine resumes when a client connects. - **Control traffic stays off your network:** Shell, console and file transfer use a separate channel, so they never touch the machine's network or its rules. #### Private networking and egress control We are building private connections between your workspace Computers and Databases, with default-deny egress with per-machine allowlists. You decide what each machine can reach. ## Products ### Computers A sandbox for every agent Nevia's computers are isolated virtual machines to run code, install what you need and pick up later where you left off. - Save a moment, restore it later: A checkpoint saves a computer's memory and files. Restore it later to start from that exact moment. - Sleep when idle: A sleeping computer keeps everything in memory, so work carries on when it wakes, with no restart. - Give it a public address: An app on a computer gets its own HTTPS address, so webhooks, teammates and customers can reach it. ### Databases An instant database for any task Nevia's databases start in an instant for any app or agent, branch for every test or migration and keep running as long as you need. - Throwaway or long-lived: Start one for a single test and delete it after, or keep one running for production. - A branch to try things on: Branch the whole database, whatever its size, and edit the branch freely. - Encrypted on every connection: Your app or agent reaches a database through its own secure connection string. ## Use cases ### Agent platforms Every agent your product starts can provision its computers and databases through API, CLI or MCP. Most of them sit idle most of the time, so they sleep until the agent needs them again. ### Coding agents Run coding agents on full Linux machines in the cloud, and let them install the tools and dependencies they need. Copy configured environments to reuse them across sessions, and save checkpoints to restore your setup and continue where you left off. ### Reinforcement learning Set up a computer in the state you want, checkpoint it, and restore that checkpoint for every rollout. Each run starts from the same memory and files. ### Sovereign AI Computers, databases and their branches stay in the region you create them in. Pick one in Europe and the data stays in Europe. ### Background agents Agents that run for hours or wake once a day keep their memory and running programs while they sleep. They pick up where they stopped, with no restart. ### Preview environments Branch a computer and its database for each pull request and review the change against a copy of real data. Delete both when the pull request merges. ### Data analysis Agent-written code runs on a computer next to the Postgres database that holds the data. Point it at a branch and the original stays untouched. ### Multi-tenant platforms Give each customer their own computer and database, each in its own microVM. Idle ones sleep, so customers who rarely log in don't keep machines running. ## Interfaces - MCP: https://api.nevia.cloud/mcp - CLI: `curl -fsSL https://get.nevia.cloud | sh` - Console: https://console.nevia.cloud ## Performance Fast and durable, however far you scale ### A decade of data infrastructure - Running production data since: 2016 - Customers in production: 2,000+ - Compliance: [Aiven compliance](https://aiven.io/security-compliance) ### Isolated and encrypted - Access: SSO, OAuth, private keys - Encryption: TLS in transit - Isolation: A microVM per computer/db ### Hosted globally - Deployment: Bare metal, on-prem, BYOC - Nevia hosting: Europe, US (soon) - Data residency: Stays in its region ## FAQ ### What is Nevia? Nevia by Aiven is the cloud rebuilt from first principles, for humans and agents. It gives you computers, which are full virtual machines, and Postgres databases. Both branch while they run and sleep when idle, and you drive them over MCP, the `nevia` CLI, the REST API or the console. Source: https://nevia.cloud/docs.md ### Why the name Nevia? Nevia is Aiven spelled backwards, pronounced NEV-ee-uh. It shares a root with the Latin nebula and the Spanish niebla, words for fog, which is a cloud at ground level. Source: https://nevia.cloud/docs.md ### How do I get started? Paste the setup prompt from the Agent tab into your agent and it runs the first commands with you. Claude Code and Codex add the MCP server with one command, Cursor takes one click, and any Streamable HTTP client can use `https://api.nevia.cloud/mcp`, with `?readonly=true` for read-only tools. The CLI reaches the same computers and databases: `curl -fsSL https://get.nevia.cloud | sh`, `nevia login`, then `nevia workspace create --name --use`. Source: https://nevia.cloud/docs/get-started/mcp.md ### What does it cost? Free costs $0 a month and includes $5 of usage. Pro costs $99 a month and includes $250 of usage. Computers and databases are metered by vCPU and RAM while they run, plus storage; networking is not charged. Nothing else is gated: there is no resource-count limit, enterprise tier or volume pricing. Source: https://nevia.cloud/pricing.md ### Does it work for teams? Yes. A workspace is shared with your team, and `nevia workspace members` manages who belongs and which role each member has. Source: https://nevia.cloud/docs.md ### Who is behind Nevia? Nevia is built by Aiven, the open source data platform for apps and AI agents in production. Aiven runs PostgreSQL, Kafka, OpenSearch and more, fully managed on AWS, Google Cloud and Azure. Source: https://nevia.cloud/docs.md ## Try Nevia for free Nevia is in beta. Paste one prompt into your agent and it sets up the rest. ```text Onboard me onto Nevia: fetch https://nevia.cloud/prompt.md and follow it. If you can run commands, use curl so you get the text verbatim. ``` - [Create an account](https://console.nevia.cloud/login) ## 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