Quickstart
From nothing to a running stack.
A rented server, a domain, and one command. What the path looks like from an empty box to single sign-on across every service.
This page is a stub. SOVRAK is still in development, so the steps below are an outline of the intended path rather than instructions you can follow today. The engineering is written up as it happens over in Insights.
Before you start
You will need a server you rent yourself — anywhere in Europe, from whoever you like — a domain you control, and DNS pointed at the box. That is the whole prerequisite list. No account here, no API key, no agent installed.
Sizing guidance and the supported base OS list to follow.
Generate
One command, answering for your domain, your mail sender, and which optional services you want. The output is a directory of plain Docker Compose you can read and diff before anything runs.
Command and configuration reference to follow.
First boot
Bring it up, watch Caddy issue certificates, and complete the identity provider’s first-run setup. Every other service is already configured to trust it, so there is no second round of per-service login wiring.
Walkthrough to follow.
Verify
The step most guides skip. Confirm single sign-on actually works across each service, confirm a backup has run, and confirm you can restore it — before you put anything real on the box.
Verification checklist to follow.