Domain Locker — Self-Hosted, Open-Source

Features

• 👁️ Total visibility of all your domains and upcoming expirations
• 📡 Auto-fetched data: SSL certs, hosts, registrars, IPs, subdomains, DNS, etc
• 🔬 View detailed metrics and analysis for each domain
• 📊 Visual analytics and breakdowns and trends across your portfolio
• 💬 Configurable alerts and webhook notifications
• 🗃️ Easy import/export, as well as API data access
• 📜 Track changes in domain configuration over time
• 📈 Monitor website health, security and performance
• 💹 Keep record of purchase prices and renewal costs
• 🔖 Add categories, and link related resources to domains

Installation

git clone [email protected]:Lissy93/domain-locker.git # Get the code cd domain-locker # Navigate into directory npm install --legacy-peer-deps # Install dependencies cp .env.example .env # Set environmental variables npm run dev # Start the dev server

Why self-host Domain Locker

Self-hosting gives you three things SaaS can’t: data ownership (the files live on disks you control), cost predictability (a one-time setup vs. recurring per-seat fees that grow with your household or team), and longevity (open-source means the app keeps working even if the maintainers move on, since you can pin a working version). The trade-off is that you take on the operational work of running a server, applying updates, and handling backups.

What hardware do you need

Most self-hosted apps run comfortably on modest hardware — a Raspberry Pi 4, a mini PC, a NAS with Docker support, or a small VPS is usually enough for personal or family use. CPU and RAM requirements scale with how many simultaneous users or how much data you push through Domain Locker. Storage requirements depend on the kind of data you keep; check the README for guidance on data retention.

Where to go from here

• Browse the full self-hosted app directory
• Compare self-hosted alternatives side-by-side
• DevOps roadmap — learn the skills to run your own server