Docs
How it fits together
Full documentation is being written. Until then, this is the shape of the platform.
The pieces
| Layer | Component | Role |
|---|---|---|
| Identity | SilverPassport | Sign-in, tenants and single sign-on for every app |
| Control | SilverDESK | Holds the desired state for sites, mail, DNS, edge and servers; queues the jobs |
| Execution | SilverShell Agent | Runs on each server, picks up jobs over mutual TLS and applies them through plugins |
| Edge | SilverGUARD | Terminates TLS and routes traffic to each site, on every edge node |
| Services | Mail, DNS, VPN, websites | Stalwart, Technitium / Cloudflare, WireGuard and VLESS, and the CMS renderer |
A change, end to end
- You make a change in SilverDESK (a new mailbox, a DNS record, a website).
- SilverDESK writes it to the database first, then queues a job.
- The agent on the right server runs the job and reports back step by step.
- Reconcilers keep checking that the live servers still match the database, and put them back if they drift.
Service status
Live status for the platform is at status.silverlined.uk.