# Console overview

> What the Nevia web console is for, and when to reach for it instead of the CLI or MCP

> Nevia is in beta and open to selected teams. Public launch in Dec 2026. The CLI installs with `curl -fsSL https://get.nevia.cloud | sh`, and the MCP server is at https://api.nevia.cloud/mcp. A person signs in once in the browser.
> Setup, sign-in and requesting access: [SKILL.md](https://nevia.cloud/SKILL.md). When Nevia fits and when it doesn't: [why.md](https://nevia.cloud/why.md).

> For the complete documentation index, see [llms.txt](https://nevia.cloud/llms.txt). This page's HTML version: https://nevia.cloud/docs/get-started/console

The console is the web UI for Nevia at
[console.nevia.cloud](https://console.nevia.cloud/). It works on the same
workspaces, computers, databases and operations as the CLI and MCP.

Everything you can do in the console you can also do from the CLI or MCP.
The console is for doing it in a browser: create and branch resources, read
connection details, see what your agents did, and clean up.

![The Nevia console showing a workspace overview with computers, databases and recent activity](/docs/images/console-overview.webp)

## What the console includes

* A workspace menu at the top. It lists your workspaces with your role in
  each, and everything below is scoped to the selected one.
* [**Overview**](https://console.nevia.cloud/): a count per kind of resource,
  and an activity feed of created, branched, restored, deleted and failed
  events.
* [**Computers**](https://console.nevia.cloud/computers): the list with each
  computer's lineage tree, and a detail page with its URL, image, ports and
  checkpoints. Create, branch, sleep, wake, protect and delete.
* [**Databases**](https://console.nevia.cloud/databases): the list, and a
  detail page per database with its connection URI, a code snippet per client,
  and a prompt for an agent. Create, branch, sleep, wake, protect and delete.
* [**Settings**](https://console.nevia.cloud/settings): rename the workspace,
  manage members and roles, manage the workspace's secrets and variables,
  delete the workspace.

## When to use the console instead of the CLI or MCP

Agents and scripts drive Nevia through the [CLI](https://nevia.cloud/docs/get-started/quickstart.md) or
[MCP](https://nevia.cloud/docs/get-started/mcp.md).

People use the console to see the state of a workspace, inspect connection
details, and clean up what they no longer need. The choice is about who is
acting, not about what is possible.

## Working alongside your agents

The console and your agents act on the same resources. A database an agent
branched from the CLI appears in the list as soon as the operation completes.
A computer you delete in the console is gone for the agent too.

The activity feed on **Overview** shows what an agent did in a workspace.

The **Agent** tab on a database's Connect card gives you a prompt with the
connection details, so you can hand a database to an agent without copying
values by hand.

## Who can do what

Your role in the selected workspace decides which actions the console offers.
Viewers read, editors create, branch and delete, admins also manage members
and the workspace itself.

The full matrix is in
[Workspace permissions](https://nevia.cloud/docs/reference/workspace-permissions.md).

## Guardrails against mistakes

Deleting a database or a computer removes its data, so the console asks you to
confirm every delete.

Turn on **Protected** for a resource that must survive an agent's cleanup. The
console and the API refuse to delete it until you turn protection off.

Sleeping a resource keeps its data and stops it from running. Use it when you
only want to pause work.