Back to all templates
Domain Locker logo

Domain Locker

Infrastructure512MB+ RAM

Self-hosted domain portfolio manager - track expiry dates, WHOIS data, SSL certs, and DNS records

infrastructurenetworkingdomainlockeropen-sourceself-hosteddocker

Deploy Domain Locker in 3 Steps

1

Connect Your VPS

Add your server credentials to Server Compass

2

Select Domain Locker

Choose from our template library

3

Deploy & Configure

Fill in settings and click Deploy

No Docker knowledge required
Step-by-step deployment guide

Deploy Domain Locker on a VPS with Server Compass

Use the Domain Locker template in Server Compass to deploy a self-hosted domain portfolio manager with PostgreSQL on your VPS, then verify the first-user page.

About 10 minutesBrowser verified
1
Step 1

Open the server Apps tab

Select the tutorial-vps VPS, open the Apps tab, and start a new app deployment. Keep sensitive server details hidden before capturing or sharing screenshots.

Server Compass Apps tab before creating a Domain Locker app
2
Step 2

Choose an app template

Click New App and choose the template deployment path so Server Compass can load the built-in catalog.

Choosing to deploy an app from a Server Compass template
3
Step 3

Search for Domain Locker

Use the template picker search to find Domain Locker in the Server Compass template catalog.

Searching for Domain Locker in the Server Compass template picker
4
Step 4

Select the Domain Locker template

Choose the Domain Locker template. Server Compass fills the web service, PostgreSQL service, auth session secret, database password, and public web port.

Domain Locker template selected in Server Compass
5
Step 5

Review the Domain Locker settings

Confirm the app name and compose service. In this run, the app was named domain-locker-demo and used host port 4203.

Reviewing Domain Locker project settings and compose service
6
Step 6

Deploy Domain Locker

Review the generated compose settings, confirm the Domain Locker web port is available, and click Deploy.

Reviewing Domain Locker web port before deployment
7
Step 7

Watch the deployment progress

Keep the deployment modal open while Server Compass uploads the compose file, pulls the Domain Locker image, starts the container, and verifies the stack.

Server Compass deploying the Domain Locker template on the VPS
8
Step 8

Confirm Domain Locker is running

After deployment finishes, return to the Apps tab and confirm the Domain Locker app is marked Running with its application URL available.

Domain Locker template running in the Server Compass Apps tab
9
Step 9

Open Domain Locker in the browser

Open the application URL in a browser. The Domain Locker first-account or sign-in page confirms the domain tracking app is reachable.

The deployed Domain Locker web UI loaded in a browser

After Domain Locker Opens

  • Create the first Domain Locker account immediately after deployment.
  • Place Domain Locker behind HTTPS before adding real domain data.
  • Treat the PostgreSQL volume as sensitive because it stores your domain portfolio and integration settings.
  • Rotate AUTH_SECRET if it is exposed; existing sessions will be invalidated.
  • Configure alerts only after confirming WHOIS, DNS, and SSL lookups work for a harmless test domain.
  • Avoid overly aggressive polling intervals to reduce WHOIS throttling.
  • Back up the PostgreSQL volume on a regular schedule.

Verified Result

The Domain Locker web UI loaded successfully from the deployed container.

Domain Locker deployment questions

What does the Domain Locker template deploy?

It deploys Domain Locker with PostgreSQL, a generated auth secret, and a public web UI for tracking domains, WHOIS, DNS, SSL, and expiry status.

Which port did the tutorial use?

The tutorial used host port 4203, which maps to the Domain Locker web UI inside the container on the same generated port.

Does Domain Locker need setup after deployment?

Create the first account, add a harmless test domain, and confirm WHOIS, DNS, SSL, and expiry data refresh correctly.

Should this become a blog post?

No. The deployment guide should live on the Domain Locker template detail page and be linked from the reusable template deployment docs page.

After Deployment

After deploying Domain Locker with Server Compass, complete these steps to finish setup

1

Open http://YOUR_SERVER_IP:{{PORT}} and create the first user account

2

Add a few domains under Add Domain and verify the WHOIS + SSL data refreshes correctly

3

Configure notification channels (email, webhook) under Settings → Notifications to get expiry alerts

4

Set up a reverse proxy + HTTPS before sharing the URL with anyone else

Need help? Check out our documentation for detailed guides.

Domain Locker FAQ

Common questions about self-hosting Domain Locker

How do I deploy Domain Locker with Server Compass?

Simply download Server Compass, connect to your VPS, and select Domain Locker from the templates list. Fill in the required configuration and click Deploy. The entire process takes under 3 minutes.

What are the system requirements for Domain Locker?

Domain Locker requires a minimum of 512MB RAM. We recommend a VPS with at least 1024MB RAM for optimal performance. Any modern Linux server with Docker support will work.

Can I migrate my existing Domain Locker data?

Yes! Server Compass provides volume mapping that allows you to import existing data. You can also use standard Domain Locker backup and restore procedures.

How do I update Domain Locker to the latest version?

Server Compass makes updates easy. Simply click the Update button in your deployment dashboard, and the latest Domain Locker image will be pulled and deployed with zero downtime.

Is Domain Locker free to self-host?

Domain Locker is open-source software. You only pay for your VPS hosting (typically $5-20/month) and optionally Server Compass ($29 one-time). No subscription fees or per-seat pricing.

Ready to Self-Host Domain Locker?

Download Server Compass and deploy Domain Locker to your VPS in under 3 minutes. No Docker expertise required.

Download Server Compass