Important Disclaimer

⚠️ The self-hosted edition comes with no warranty. There are no guarantees for functionality and maintaining, securing and managing the infrastructure will be your responsibility. The developer cannot be held liable for any damages or losses caused by the use of the self-hosted edition.

‼️ Domain Locker is not intended to be publicly exposed to the internet. It does not come with authentication, and may be susceptible unrestricted or arbitrary SQL execution unless properly secured behind a firewall, with correct access controls implemented.

---

Prerequisites

In order to self-host Domain Locker, you will need a server (such as a Raspberry Pi, laptop, VM or VPS). Domain Locker is intended to be run with Docker, so you will need to have Docker and Docker Compose installed.

---

Deployment

• With Docker
• With Kubernetes
• On Proxmox VE
• On Umbrel
• On easypanel
• From Source
• With Supabase

One-Liner

curl -fsSL https://install.domain-locker.com | bash

---

Resolving Issues

• Debugging Docs - Walk through of diagnosing issues
• Checking Logs - How view and understand the build and runtime logs
• Troubleshooting - Solutions for common issues and outline of known limitations
• 3rd-party Docs - Signposting to docs for related packages and services
• Support - Contact details for support queries (currently unavailable for free users)

---

Developing

• Dev Setup and Docs
• Source Code

---

See Also

• Auto-Fetching Domain Info
• Configuring Expiry Notifications
• Docker Best Practices
• Architecture Overview
• Conditions for Public Instances