Everything a small hosting operation needs. Nothing it doesn't.
A tour of what Atrium does on day one, and how it does it.
The domain is the whole story.
There's no separate “site” or “environment” to keep in sync. A domain hosts at most one thing. Subdomains are domains too, grouped under their parent and sharing its DNS zone, so staging sits right next to production.
- DNS-only and redirect domains in the same list
- Archive a domain and restore it within 30 days
- Every change recorded in the activity log
The stacks client sites actually use.
Choose WordPress, PHP or static when you add hosting to a domain. Images come from a fixed catalog, so nothing unexpected ends up running on your box. Change memory limits, PHP version and environment from the domain's settings.
- WordPressFresh install with its own database
- PHPPHP-FPM, pick your version
- StaticHTML, CSS, built sites
A hacked plugin stays one site's problem.
Each hosted domain runs in its own container with locked-down defaults. A firewall on the host blocks tenant traffic to the host itself, to cloud metadata endpoints and to Atrium's own services.
- User
- dedicated tenant UID
- Network
- own bridge, Caddy + DB only
- Capabilities
- none
- Root filesystem
- read-only
- Mounted
- public/ only
Certificates before cutover.
Caddy handles HTTPS for every domain. By default it proves ownership through DNS using a scoped Cloudflare token, so a migrated site has a valid certificate before you point the DNS at it. HTTP validation is there if you want it.
- DNS-01Default, via the domain's or parent's credential
- Auto-renewFailures raise an alert, not a surprise
- Last known goodProxy config is snapshotted on every change
- Preview URLsCheck a site before its DNS moves
Plan for the day the box dies.
Atrium backs up site files, databases and its own configuration with restic, encrypted, to the destination you choose. The recovery kit holds what you need to rebuild on new hardware. Change anything it depends on and Atrium asks you to save a fresh one.
Do the daily work without SSH.
File manager
Upload, edit, move, restore from trash. Files stay owned by the site's user.
Git deploys
Connect a repo and deploy a branch as a background job.
Terminal
A browser shell inside the site's container. Run WP-CLI or Composer.
Live logs
Access and error logs per domain, streaming as requests arrive.
Databases
MariaDB database and user per domain, credentials encrypted at rest.
One list of what needs you.
Stopped containers, certificate failures, missed backups and proxy errors all land in one place: the home screen. The same list goes out by email or webhook, so you hear about it before your client does.
Three ways in. None of them public.
- Direct
- Through Caddy on your own hostname, with an IP allowlist
- Tunnel
- Cloudflare Tunnel, no open ports at home
- Tailscale
- Only devices on your tailnet can reach it
Questions
Can my clients log in?
Not in version 1. Atrium is built for a single operator. Clients get their sites; you keep the keys.
What do I need to run it?
A Raspberry Pi 5 or a VPS running Ubuntu Server LTS, on ARM or x86, and a domain you control. The installer sets up everything else, including Docker and the firewall.
Do I need Cloudflare?
Cloudflare is the supported DNS provider for automatic certificates via DNS-01. You can use HTTP validation instead if your DNS lives elsewhere.
Does Atrium host email?
No. Atrium hosts websites. Keep mail with a dedicated provider, such as Google Workspace or Fastmail, and point your domain’s mail records at it.
Can I move sites from my current host?
Yes. Add the domain, upload files or push from Git, import the database, check it on a preview URL, then switch DNS.
Get the first release.
One email when Atrium is ready to install.
We'll only use your email for this. Privacy policy