All blog posts
Research 3 min read

Researching Self-Hosted Commonveil With Docker and HTTPS

The practical findings behind Commonveil's independent Docker deployment, HTTPS, backups, site identities and safer update controls.

By Comutability Published Update from

Research record from 6 November 2026. This is an evidence-led account of the research and design, not an announcement of independently audited software.

The practical findings behind Commonveil's independent Docker deployment, HTTPS, backups, site identities and safer update controls.

Why self-hosting matters

A network is not genuinely decentralised if everyone must run it on one provider's infrastructure. The Commonveil self-hosting design begins with a practical requirement: a person or community should be able to operate a site without Base44 and still communicate with other compatible sites. A home server, VPS or suitably configured Raspberry Pi are documented deployment targets.

That freedom also transfers responsibility. The operator has to understand DNS, certificates, storage, updates and what happens when their machine is offline. Calling something self-hostable is only useful if ordinary operators can follow and recover from the installation process.

The deployment model we examined

The documented stack uses Docker Compose and separates the application, HTTPS termination and controlled update responsibilities. Caddy handles certificates. The application contains accounts, encrypted message storage, web functions and federation endpoints. An updater component has access to Docker, so keeping that privilege narrow is especially important.

Installation uses a site domain, environment settings and a first-admin setup code shown locally. The setup-code decision emerged from a security finding: the first person to register on an open site must not automatically become the administrator. A site operator should also be able to disable general registrations.

Key engineering and operational findings

A self-hosted service needs reliable backups before upgrades, visible update status, sensible rollback options and checks that downloaded images actually exist. Automated updates may be convenient, but they increase the cost of a mistaken release. The documented self-hosting guide treats backups, Docker volumes and release selection as part of the product rather than as optional instructions.

DNS is also part of identity. The guide describes both a site domain and optional wildcard records for account-specific addresses. HTTPS is required for ordinary browser security features, and local-only installations must consider how devices trust a certificate without an internet-facing certificate authority.

What decentralisation does and does not solve

Operating your own server reduces dependence on a single service provider. It does not remove the need to secure the host, protect backups, patch dependencies or explain administrator powers. End-to-end encryption protects selected content from the site, but site operators still observe metadata and can affect delivery.

Federation makes independent sites useful together, but introduces signed requests, site-key pinning and cross-site failure handling. A deployment guide should be tested with a fresh installation on both supported architectures rather than copied from a developer's already configured machine.

Status and follow-up

The installation and federation instructions exist in the Commonveil repository; this article is an explanation of their research and design. It does not certify every hardware configuration or claim that the Rust replacement server has already become the Docker production image.

The next practical checks are installation on a clean host, backup restoration, administrator onboarding, security updates, accessibility and interoperability between independently run sites.

Primary sources and further reading

Explore other Comutability research ยท Read about the organisation

Sources and further reading

Explore the evidence and original project records behind this article.