Documentation
Implemented vs planned
Everlock already contains real working pieces, but it also documents future backend families in detail. Keeping that distinction visible is important for operators and contributors.
Backend status
| Backend | Status |
|---|---|
backend-git-ssh | Implemented and active |
backend-site-http | Implemented and active |
backend-image-http | Implemented and active |
backend-admin-ssh | Implemented and active |
backend-admin-http | Implemented and active |
backend-dns-dns | Implemented and active |
backend-oci-http | Implemented and active |
backend-mail-smtp | Implemented and active |
backend-mail-imap | Implemented and active |
backend-calendar-http | Implemented and active |
backend-contacts-http | Implemented and active |
backend-oauth-http | Implemented and active |
backend-ai-ssh | Implemented and active |
backend-dns-http | Implemented and active |
Shared resource crates
| Crate | Status |
|---|---|
everlock-mail-storage | Implemented — shared by backend-mail-smtp and backend-mail-imap |
everlock-ai-runtime | Implemented — shared by backend-ai-ssh and backend-image-http |
everlock-acme | Implemented — used by frontend-http |
Frontend status
| Frontend | Status |
|---|---|
frontend-ssh | Implemented and active |
frontend-http | Implemented and active |
frontend-dns | Implemented and active |
frontend-mdns | Implemented in the repository |
frontend-smtp | Implemented and active |
frontend-imap | Implemented and active |
Planned work
- smart HTTP Git support
- fuller OCI registry behavior and finer-grained OCI authorization
- webmail / HTTP mail read path
- richer calendar client compatibility and query behavior
- MQTT transport (
frontend-mqtt) for event and device-oriented backends
Reading this correctly
Planned does not mean vague. In several areas the repository already contains substantial design docs, storage notes, and API intent. That makes the project easier to contribute to because the shape is discussed before the code lands.