Skip to content
OpenVireoDeveloper
GitHub

Language bindings

Every language binding, what it is for, and how they differ.

The core is Rust. Each binding exposes the same facade (ov-core): OvClient, Account, Vault, ServiceAccount, SelfHosted, the records, OvError with the same codes, and the crypto, share-link and TOTP functions. None of them reimplements OPAQUE, keysets or the KDBX merge. A program on any binding interoperates with the apps.

Language Use it for Binding Get it Docs
TypeScript / JavaScript Web apps, Node, Bun, CLIs wasm (bindings/ov-wasm), wrapped by @openvireo/sdk npm: @openvireo/sdk SDK docs
Swift iOS and macOS apps UniFFI (bindings/ov-ffi), module OpenVireoRustCore cargo xtask xcframework (the iOS app vendors it) bindings/ov-ffi
C++ Qt and other native desktop code cxx (bindings/ov-ffi-cpp), <ovcore.h> CMake / Corrosion at a pinned commit bindings/ov-ffi-cpp
Python Scripts, automation, backends UniFFI (bindings/ov-ffi), package openvireo wheels on the GitHub release Python
Kotlin / Java JVM services and tools, Android apps UniFFI (bindings/ov-ffi), package com.openvireo.core GitHub Packages (Maven) Kotlin and Java

Pick the TypeScript SDK if you work in JavaScript. It adds a higher-level API, the ov CLI, ov connect and the GitHub Action on top of the core. Use the wasm package (@openvireo/core-wasm) directly only for the low-level calls.

TypeScript (wasm) Swift C++ Python Kotlin / Java
Async calls Promises async blocking (call from a worker thread) asyncio coroutines suspend; CompletableFuture in Java
Cancelling AbortSignal CancelToken CancelToken task cancel or cancel=CancelToken() coroutine cancel or CancelToken; future.cancel in Java
Errors OpenVireoError (code) OvError (code, wireCode) ov::Error (via ov::call) OvError (code, wire_code) OvException (code, wireCode)
Ready-made Host yes (fetch, IndexedDB or memory) the app’s own the app’s own openvireo.hosts com.openvireo.core.hosts
Secrets linear memory zeroed on free Data, caller wipes rust::Vec<uint8_t>, caller wipes bytes, can’t be wiped ByteArray, fill(0)

The core does no I/O. Every binding passes in a Host with five parts: an HTTP transport, a secure store, an offline cache, a clock and a log sink. TLS, proxies, the keychain and logging stay with the platform. Architecture describes the contract. Two rules apply to every transport: it must not follow redirects, and it must not send or store cookies.

Every binding is built from the same commit and has the core’s version. Until 1.0.0 the API can change between releases. Pin an exact version.