Built where the work happens 

Legal work runs on confidentiality, and the first generation of legal AI was built as if that were a compliance detail. Tools arrived that asked firms to send their matters to somebody else's cloud and trust a policy document in return. For a profession whose raw material is privileged, that was the wrong default — not an unacceptable risk to negotiate down, but the wrong default.

Vaultr started from the opposite end: the boundary first. What happens on the device stays on the device, and anything that would cross the boundary is a named, explicit mode — never a fallback. Everything else, from the evidence ledger to the published boundary test, follows from that decision.

In the open. The repository is public under AGPL-3.0 — licence, attribution, history and all — because a security team that can read the code is worth more to us than any paragraph this page could write. Dependency lockfiles are committed, automated checks run on the supported flow, and every claim on this site traces to an artifact you can open.

Vaultr is built by a small team operating from Singapore, working directly with the firms evaluating the product — no account-management layer between the people building it and the people testing it. Support during evaluation is replies from the builders; the access form reaches exactly those people.

Assisted evaluation, by request. No public download, no self-service sign-up — deliberately, because what is being evaluated is fit against your bundle and your intended mode, not a demo. macOS on Apple silicon is the tested target; Windows and Linux are planned, not released. No independent audit exists yet; the security brief's not-done list says so in those words.