Skip to content
OpenVireoDeveloper
GitHub
NewPython and Kotlin bindings for the Rust core

Build on vaults the server can’t read.

SDKs, the ov CLI and an HTTP API for OpenVireo. Read secrets in CI, script vaults and sharing, or run your own sync server. Everything is encrypted on the client.

npm install @openvireo/sdk
~/deploy
# Read one secret
ov read ov://Team%20Infra/GitHub/password
# Resolve references into a command's environment; output is masked
ov run --env-file .env.tpl -- ./migrate.sh
# Rotate it
ov rotate ov://Team%20Infra/Deploy/Database/password --generate

Pick your tool

One core, four ways in

The same Rust core runs in every app, so code you write here works with vaults people use on desktop, web and iOS.

First program

Read a secret in a few lines

Sign in, open a vault and read an item by its ov:// reference. For automation, use a service account: no password, scoped to the vaults it needs.

import { Account, MemoryStorage } from "@openvireo/sdk";
const account = await Account.connect({
issuer: "https://accounts.openvireo.com",
device: { name: "My script", platform: "cli" },
storage: new MemoryStorage(),
});
await account.login({ email, password, secretKey });
const [first] = await account.listVaults();
const vault = await account.openVault(first.id);
console.log(vault.read("ov://Personal/GitHub/username"));

Guides

Start from a task

All guides →

Zero knowledge, by design

The servers only ever receive OPAQUE messages, encrypted .kdbx files, wrapped keysets and sealed keys. Your integration gets the same guarantees.

What the servers see →
01OPAQUE sign-inThe password never leaves the device, not even as a hash.
02Client-side encryptionVaults are KDBX files, encrypted before upload and merged locally.
03Open sourceThe core and SDK are MIT/Apache-2.0, with signed releases.