Files backend
The files backend is Everlock's WebDAV service. It serves one or more file shares over HTTP, authenticates with normal Everlock users, and keeps every file — and every version of every file — in Everl
Documentation
Tag: backend
WebDAV behavior and storage reference
This page covers Everlock's WebDAV behavior and the storage model behind it. - served through `frontend-http` - multi-share and multi-vhost, each share on its own mount path - one dedicated `versioned
Captions on the photo frame
An e-paper frame on the wall shows a photo — and now, if you want, a line that says when and where it was taken. The photoframe endpoint draws a caption into the bottom-left corner of every frame it s
Your photo albums on an e-paper frame
Everlock now serves battery-powered e-paper picture frames. Point an [esp32-photoframe](https://github.com/aitjcize/esp32-photoframe) at an album and it wakes up, fetches one picture, and goes back to
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
The gguf-runner inference engine
Everlock runs its AI features on its own inference engine, [**gguf-runner**](https://github.com/apimeister/gguf-runner) — a self-developed, from-scratch GGUF runtime written for this project. It is em
The apimeister-photos engine (ami)
Everlock does not implement a photo library from scratch. The image backend embeds [**apimeister-photos**](https://codeberg.org/apimeister/apimeister-photos) — a standalone, stateless media library kn
Running multiple image instances
A single Everlock process can host many independent photo libraries at once. Each library is an **image instance**: its own storage, its own hostnames, its own access grants, and its own gallery. This
The apimeister-registry engine
Everlock's container registry is powered by [**apimeister-registry**](https://codeberg.org/apimeister/apimeister-registry) — a standalone, open-source OCI Distribution runtime. Everlock embeds that en
AI backend
The AI backend is Everlock's built-in operator assistant and shared vision runtime. It is exposed in two places: - an interactive prompt mode inside the admin SSH session - image captioning for the im