Domain Locker

Self-Hosting

Docker Deployment - How to deploy Domain Locker using docker compose
Kubernetes Deployment - How to deploy Domain Locker using Kubernetes and Helm charts
Deploy to Umbrel OS - One-click install Domain Locker on your Umbrel OS server
Deploy from Source - Building the app manually from source code
Notifications - How to setup alerts for domain changes and upcoming expirations in a self-hosted Domain Locker instance
Docker Tips - Securing, monitoring, backing up and generally maintaining your container
Self-Hosted Architecture - Overview of Domain Locker's architecture and components
Publishing a Public Instance - Etiquette for deploying a public instance of Domain Locker
Quick Start - Get up and running in minutes

Self-Hosting Domain Locker

I have documented and open sourced Domain Locker for free. You can find the source on GitHub, at lissy93/domain-locker.

⚠️ 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. It is not intended to be publicly exposed, unless secured it behind a firewall, with correct access controls implemented.

Prerequisites

In order to self-host Domain Locker, you will need a server. This can be anything from a low-powered SBC like a Raspberry Pi to a dedicated VPS.

Domain Locker is intended to be run with Docker, so you will need to have Docker and Docker Compose installed on your server. You may also need a domain name and a valid SSL certificate for that domain.

Deployment

One-Liner

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