Self-Hosting Passwords Without Trusting the Host
Most self-hosting decisions are decisions about convenience. You move a service onto your own hardware, accept that you are now the person who patches it, and the worst realistic outcome is some downt
Documentation
Tag: vault
Everlock 0.7.0
The 0.7.0 release tightens who may do what. Access now derives solely from explicit grants, git repositories can hand out a contributor role that opens pull requests without touching branches, and vau
Getting started: Vault backend
This guide runs Everlock as a **standalone password vault** and connects an official Bitwarden client to it: - start Everlock with one vault instance on a public HTTPS vhost - point a Bitwarden client
Vault backend
The vault backend is Everlock's **Bitwarden-compatible password manager**. It provides a hosted, end-to-end-encrypted password vault over HTTP, backed by Everlock's versioned storage. Official Bitward
Bitwarden behavior and storage reference
`backend-vault-http` is a multi-instance, Bitwarden-compatible vault backend for Everlock. The wire protocol, client crypto, and data model live in the standalone [`apimeister-vault`](https://codeberg
A Bitwarden-compatible password vault
Everlock now hosts your passwords. The new **vault backend** (`backend-vault-http`) speaks the Bitwarden protocol, so the official Bitwarden clients you already use — desktop, browser extensions, mobi