Skip to content
Zero Docs

Getting started with ZeroVault

This walks through the dashboard. By the end you have a project with a secret and a terminal that can read it.

1. Sign in

Section titled “1. Sign in”

Go to dash.zeroapps.dev and sign in (or sign up).

On sign-up an organization is created for you and is already active, shown in the switcher in the top-right corner. There is no separate “create an organization” step. If you belong to more than one organization, use that switcher to pick the one you want to work in.

2. Create a project

Section titled “2. Create a project”

Open Projects in the sidebar, type a name (for example my-app) in the New project name field, and click Create.

The new project starts with two environments, development and production. Open the project to see them; you can add or remove environments here.

3. Add a secret

Section titled “3. Add a secret”

Open the project, then open an environment (for example development). Add a secret as a key and value (for example API_TOKEN / your token) and save. Secret values are stored for that one environment.

4. Read it from your terminal

Section titled “4. Read it from your terminal”

Sign the CLI in with the same account. There is no key to copy:

Terminal window
npx @zeroapps/cli@0.7.0 login
npx @zeroapps/cli@0.7.0 vault secrets list -p my-app -e development

login opens your browser and asks which organization to use. It signs in that one machine, and zero logout signs it out.

5. When you need a key

Section titled “5. When you need a key”

zero login covers your own machine. A GitHub Actions job can use its OIDC token. A server or a container has neither, so it needs a key.

Open API keys in the sidebar, below the product list, add a label if you want one, and click Create. From a signed-in terminal, zero keys create does the same thing.

The full key (zv_…) is shown once, right after you create it, with a copy button. Copy it now; it is not shown again. If you lose it, revoke it and create a new one.

Keep the key secret. It is organization-scoped, so it reaches every project and environment in your organization, and it also authorizes ZeroErrors. See API keys for the full reference.

Next

Section titled “Next”