Skip to Content
Getting Started

Getting Started

Create Your Account

DepVault supports two registration methods: email/password or GitHub OAuth.

Email and Password

  1. Navigate to the login page and click Register.
  2. Fill in your name, email, and a password (minimum 8 characters, at least 1 uppercase letter and 1 number).
  3. Click Create Account, then verify your email via the link sent to your inbox.

GitHub OAuth

Click Continue with GitHub on the login page and authorize DepVault. Your account is created automatically from your GitHub profile.

Set Up Your Encryption Vault

Before you can store any config or secret file — in the web app or the CLI — set up your encryption vault in the web dashboard under Profile → Security.

  1. Choose a vault password. This is separate from your login password and never leaves your device — it derives the key that encrypts everything.
  2. Save the recovery key shown once. It is your only way back in if you forget your vault password; store it offline.

Everything you store is encrypted in your browser or the CLI before it reaches the server, and the server can never decrypt it. Because of that, DepVault cannot reset your vault password or recover your data — if you lose both the password and the recovery key, the data is gone for good. See Encryption & Security for how this works.

The CLI cannot create an account or set up a vault. Until you complete this step, depvault push and depvault pull fail with Vault not initialized.

Create Your First Project

  1. From the Dashboard, click + New Project.
  2. Enter a project name and optional description.
  3. Click Create.

Your project appears as a card on the dashboard, ready for dependency scans and config/secret file management.

Run Your First Dependency Scan

Web UI

  1. Open your project and go to the Analysis tab.
  2. Click New Analysis and upload a dependency file (e.g., package.json, requirements.txt, Cargo.toml).
  3. Click Analyze to view results with version status and vulnerability data.

CLI

Install the CLI and run a scan:

# Linux / macOS
curl -fsSL https://get.depvault.com | bash
 
# Windows (PowerShell)
irm https://get.depvault.com | iex

Push Your Config & Secret Files

Push your repository’s config and secret files to DepVault. Each file is encrypted in your browser/CLI and uploaded as a single blob. depvault login opens your browser to authenticate; make sure you’ve set up your vault (above) first:

depvault login
depvault push

Run depvault doctor any time to check what’s set up and what’s left — it walks the login, vault, project, and key steps and prints the exact next command for anything missing.

push discovers config files (.env, appsettings.json, …) and secret files (.pem, .key, credentials.json, …), infers each file’s app and environment slug from its path and name, and uploads the encrypted blobs. No --vault or --tag flags needed.

Pull everything back, restored byte-for-byte to its original repo-relative path:

depvault pull

This recreates each file exactly where it was pushed from, recreating directories as needed. See the Pull & Push reference for all options.

Edit a File in the Browser

  1. Open your project and go to the repository view.
  2. Pick an app in the sidebar and an environment tab, then select a config file.
  3. Edit it in the Form (key/value table for .env) or Raw (code editor) view, click Review & Save to preview a git-style diff, and save.

Every save snapshots a new encrypted version. See the Config & Secret Files guide for details.

DepVault DocumentationGuides