Vaarta Vault
Sign inCreate your vault
NewAI agents use your keys without seeing them

Every secret you own, sealed. Your phone is the key.

Passwords, servers, SSH keys, signing keys and cards in one vault, on your Mac, in Chrome and on your Android phone. Your AI agents sign in, call APIs and sign releases with them, and never hold a single one.

Create your vaultSee how agents use it

Per-item keys in AWS KMS Number matching on your phone Agents never see a secret

Vaarta AuthenticatorShow a password?Production database, on MacBook Pro176083
AppleGoogle ChromeAndroidModel Context ProtocolGoogle Password ManagerBitwarden1PasswordLastPassDashlaneKeePassXCFirefoxEnpass

Mac, Chrome and Android · AI agents over MCP · imports from 12 password managers

AI agents · MCP

Let AI agents do real work with your credentials. Without ever holding them.

Your agent finds what it needs by title, asks you once, and the vault does the rest. It works through MCP, the open Model Context Protocol, so any agent that speaks it can connect.

It signs your browser in

A bridge on your own machine types the password straight into the right field over DevTools and submits at once. The model is told “signed_in”. Nothing else.

sign_in_browser

It calls the API for you

The vault adds the stored token to an HTTPS call to the item's own hosts, then scrubs it from the answer before the agent reads it.

use_credential_http

It signs the release

AWS KMS signs with a key that can never be exported. The signature comes back. The key never does.

sign_digest
  1. Agent1Connects onceOAuth 2.1 with PKCE. You allow it on one screen.
  2. Identity Studio2Issues a bound tokenRFC 8707: good for the Vault endpoint and nothing else.
  3. Agent3Asks for one itemNames the item, the operation and the hosts.
  4. Phone4You tap the numberYour phone shows which item and why.
  5. Vault5Does the workSigns in, calls the API or signs, inside the vault.
  6. Agent6Gets the result onlyRedacted. Never a password, token or key.
How we secure agents

In which planYour plan sets how many agents each person connects.See plans →

Why Vaarta Vault

What you get, and how we prove it.

Six outcomes. Under each, the mechanism that makes it true.

Your AI agents sign in and ship, without seeing a password.

Tools answer with titles and results. No tool ever returns a secret or a username.

MCP resource server · RFC 9728 · RFC 8707 bound token · redacted results

Nothing unlocks without your phone and a matching number.

Three numbers on your phone, one on your screen. A wrong tap refuses; “It wasn't me” refuses and records.

Number matching · a request lapses after 10 min · an unlock lasts 5 min at most

Servers, SSH keys, signing keys and cards. Not just passwords.

A server keeps its addresses, services, logins and jump host. A key keeps its algorithm, fingerprint and expiry.

Up to 10 addresses, 12 services and 10 logins per server

Keys that never leave hardware.

Signing keys are made inside AWS KMS and cannot be exported. You or your agent sign; nobody holds the key.

AWS KMS · 500 signatures per key per day · no SHA-1

Share with your team without sharing the secret.

Give a teammate use, reveal or manage on a shared vault. When they leave, you get the list of what to rotate.

Organization vaults · use < reveal < manage · rotation list

A breach check that never sends your password.

Only the first five characters of a SHA-1 hash leave, padded. No item is opened to run the check.

k-anonymity range query · Add-Padding

The problem

Your secrets are everywhere. That is the problem.

A password saved in one browser. A server written in a notes app. A key on a laptop. A token pasted into a chat. Every copy is one more way in.

Six places, six copies, and no moment where you decide who gets in.

Notes · Servers
prod db 10.0.4.12
root / hunter2hunter
jump: bastion-01
Team chat · 10:42
can you send me the staging password?
sure, it's S7ag!ng-2026
~/projects/app/.env
API_TOKEN=tk_8f2a91c0d3
DB_PASSWORD=p4ss
# TODO: move these
Save password for this site?
Saved to this browser only. Your other computers will not know it.
Terminal
$ cp id_ed25519 /Volumes/USB/
no passphrase
Photos · Screenshot
Card photo
4242 4242 4242 4242

One vault

One vault for everything you sign in with.

Put it all in one place, sealed item by item. Every app you use reads from it, and nothing opens until you say so on your phone.

Logins and one-time codes

Up to ten sites per login. One click fills the username, the password and the current code.

Servers, as they really are

Public and private addresses, services and ports, a login for each, the jump host and fingerprint.

Keys with their facts

SSH, TLS, PGP and service-account keys with algorithm, fingerprint and expiry.

API secrets

Tokens your tools and AI agents use through the vault, without reading them.

Signing keys

Made in AWS KMS and never exported. You or your agent sign; nobody holds them.

Cards and identities

Fill checkout and sign-up forms. A card asks your phone every time and shows for one minute.

Notes and files

Secure notes and up to ten sealed files on any item. Deleted items wait 30 days in the trash.

Password health

Reused, weak and breached passwords in one list, with the fix on the same screen.

In which planEvery item type, in Personal and Organization.See plans →

How a reveal works

What happens when you press Show.

Unlocking the vault on a computer or in Chrome takes a number match on your phone, and the unlock lasts five minutes at most.

  1. Production database••••••••••Show
    Step 1

    You ask

    You press Show. The app signs the request with its own device key, so the vault knows which device is asking.

  2. Vaarta Authenticator · nowShow a password?Production database · MacBook Pro
    Step 2

    Your phone asks you

    Vaarta Authenticator shows what is asking, from which device, and three numbers.

  3. Screen60Phone176083
    Step 3

    You match the number

    Tap the one your screen shows. A wrong number refuses. “It wasn't me” refuses and records it.

  4. Production databasex9T#q2…vLp4Approved · recorded
    Step 4

    One field opens

    On that device only, recorded before it is shown. A card shows for 60 seconds, then asks again.

The full security architecture

In which planNumber matching protects every plan.See plans →

A day with Vault

One Monday, four moments, one vault.

It shows up where you are working, and steps back when you are done.

08:52 · Chrome

Sign in without typing a thing

Open the extension on the sign-in page. One click fills the username, the password and the current code.

Vaarta Vault · For this site
github.commanish@example.com · code 482 913Fill
11:20 · Vault for Mac

Open the server, not a notes file

Addresses, ports, the right login and the key that opens it, on one card.

Production database · via bastion-01
Public203.0.113.24
Private10.0.4.12
ServicesSSH 22 · PostgreSQL 5432
Loginsdeploy · postgres
KeyDeploy key · ed25519
13:40 · Chrome at checkout

Pay without reaching for your wallet

Your card fills a checkout form after a fresh tap. Cards never leave your personal vault.

•••• 4242Tap 35 on your phone
Each field opens for one minute, in this browser only.
17:05 · Your AI agent

A release, signed while you watch

Your agent asks to sign with the release key. You tap once. The signature comes back; the key never does.

Agent sign_digest with “Release key”You tap 47 on your phoneVault Signed. The key never left AWS KMS.

Get the apps

AppleMacApple siliconGoogle ChromeChromeExtensionAndroidAndroidVaarta AuthenticatorWinWindowsWindows64-bitComing soonLinuxLinux64-bitComing soon

In which planEvery app in every plan, with up to 10 browsers and computers per person.See plans →

Security, plainly

Six promises, in plain words.

What protects your things, and what it means on an ordinary day.

Sealed item by item

Each item has its own data key from AWS KMS, bound to that item. Opening one never opens the rest.

Requests signed by the device

The extension and the desktop app sign every request with their own key. Replays and stale requests are refused.

Number matching on your phone

A tired “yes” to a request you did not start is not enough. You tap the number your screen shows.

Nothing behind your back

Every reveal is recorded before the value is shown. Every browser, computer and agent is listed, and you can cut any off.

Some things stay on one computer

Mark an item device-only and it never leaves that Mac. No request ever carries it.

Leave whenever you like

Export your vault as one file sealed with your own passphrase: Argon2id and AES-256-GCM.

Security architectureSign-in and access

Moving in

Bring everything. Leave nothing behind.

Choose where your passwords live today. We open that app's export page, show what will come across before anything is saved, and remind you to delete the export file.

Google Password ManagerChromeEdEdgeBraveApple PasswordsFirefoxBitwarden1PasswordLastPassDashlanePPProton PassNPNordPassEnpassKeePassXCKPKeePassAny CSV
Every source, and what comes across
BitwardenImport from BitwardenStep 2 of 3

Here is what will come across. Nothing is saved until you choose Import.

Logins, with their one-time codesready
Secure notesready
Payment cardsnever imported

Afterwards, delete the export file from your Downloads.

Import

In which planImport from every source, up to 2,000 rows a file, in every plan.See plans →

Plans

A vault for you. Shared vaults for your team.

The same protection in both. Organization adds vaults your team shares, with access you control item by item.

Personal

For you, on every device you own.

  • Every item type, cards and identities included
  • Mac, Chrome and Android
  • AI agents over MCP
See Personal

Organization

For teams

For teams that share servers, keys and logins.

  • Everything in Personal, for each member
  • Shared vaults with use, reveal and manage access
  • Audit trail and a rotation list when someone leaves
See Organization
Compare every feature

Put every secret behind one tap.

Create your vault, link your phone, and bring everything in from where it lives today.

Create your vaultSee plans