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# Read one secretov read ov://Team%20Infra/GitHub/password
# Resolve references into a command's environment; output is maskedov run --env-file .env.tpl -- ./migrate.sh
# Rotate itov rotate ov://Team%20Infra/Deploy/Database/password --generatePick 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.
TypeScript SDKAccounts, vaults, sharing, sync and service accounts. Browser, Node 20+ and Bun.
@openvireo/sdkov CLIRead, inject and rotate secrets from scripts and CI. Signed single binaries, no Node needed.ov read · ov run · ov injectSync server APIHTTP routes for vaults, history, devices and events. Self-host it or use the hosted service./api/v1/vaultsLanguage bindingsThe Rust core for Python, Kotlin and Java, Swift and C++. Same facade, same error codes.Python · Kotlin/Java · Swift · C++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"));# Sign in once on this machine
# Read a fieldov read ov://Personal/GitHub/username
# Fill a template; the output file is mode 0600ov inject -i config.yml.tpl -o config.yml
# Share an item without a login, once, for a dayov share ov://Private/Bank --field Password --once --expires 1dimport openvireo as ovfrom openvireo.hosts import default_host
client = ov.OvClient( ov.ClientConfig( device=ov.DeviceInfo(id=None, name="backup script", platform=ov.Platform.CLI), offline=False, server=None, ), default_host(),)import com.openvireo.core.*import com.openvireo.core.hosts.defaultHost
val client = OvClient( ClientConfig(DeviceInfo(id = null, name = "backup tool", platform = Platform.CLI), offline = false, server = null), defaultHost(cacheDir = Path.of("ov-cache")),)Guides
Start from a task
CI/CDLoad secrets into GitHub ActionsUse a service account and the GitHub Action to load and mask secrets in a workflow.KubernetesServe secrets with ov connectRun a REST server for one service account inside your cluster, with ready manifests.Self-hostingRun your own sync serverInstall, configure and pair devices with a sync server you operate.SharingCreate no-login share linksShare one item or field, with an expiry, a passcode or a single view.AppsWork offlineKeep working without the network, and catch up afterwards.UpgradingMigrate to SDK 1.0What changed in 1.0, on the shared Rust core, and how to upgrade.
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.