Architecture
Everlock is organized around a simple rule: transport and service logic stay in separate components. {{< mermaid caption="Frontends own transport, backends own service logic, and shared primitives sta
Documentation
Everlock is organized around a simple rule: transport and service logic stay in separate components. {{< mermaid caption="Frontends own transport, backends own service logic, and shared primitives sta
Backends are where Everlock's service logic lives. They should stay transport-agnostic and avoid depending directly on SSH, HTTP, SMTP, or other frontend libraries. | Backend | What it handles | |---|