Autoxpose
Autoxpose is an automatic DNS and reverse proxy manager for Docker containers that creates encrypted proxy routes without manual setup.
Platform availability
Available on 2 of 10 platforms
- Unraid (not listed)
- TrueNAS
- Umbrel (not listed)
- ZimaOS
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
66/100 Good
- Maintained
- 82last commit 44 days ago
- Popular
- 44152 GitHub stars
- Easy to install
- 352 install platforms, install notes
- Light to run
- No data
- Security check
- 94no serious findings, 1 minor, CI, tests
Based on 4 of 5 factors.
Availability: platform listings confirmed today, links checked 13 days ago
- GitHub stars
- 152
- Open issues
- 14
- Last commit
- 2026-10-08
- Latest release
- v0.6.0
- License
- MIT
- Activity
- stale
Checked 5 days ago - source: GitHub (mostafa-wahied/autoxpose)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Set IPs and port before starting Enter your public IP (internet IP) as serverIp, your LAN IP (local network IP) as lanIp, and open port 3000 (the app's HTTP port); if any are wrong or closed, Autoxpose may be unreachable or create DNS/proxy entries that don't work. source
- Point it at Docker with the right socket Keep docker.socketPath (the connection point to Docker) set to /var/run/docker.sock and labelPrefix (the tag Autoxpose uses to find its containers) set to autoxpose; if either is wrong, Autoxpose won't see the apps you want to expose. source
- Keep your database file safe Keep the file at database.path (where Autoxpose saves its state, default ./data/autoxpose.db) on storage you can back up; losing it may force you to re-detect services and can leave orphaned entries. source
- Label containers Add autoxpose labels to Docker containers so autoxpose creates the DNS record and reverse proxy entry automatically. source
Fetched 39 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
What Docker label prefix does Autoxpose use to detect containers it should expose?
Set labelPrefix to autoxpose so Autoxpose can find the containers you want to expose. If the prefix is wrong, it will not see those apps.
What IP and port settings need to be correct before Autoxpose starts?
Set your public IP as serverIp and your LAN IP as lanIp, and open port 3000 for Autoxpose's HTTP access. If these are wrong or closed, Autoxpose may be unreachable or create DNS and proxy entries that do not work.
Where does Autoxpose store its state, and why should that file be backed up?
Autoxpose saves state at database.path, defaulting to ./data/autoxpose.db. Losing that file can force service re-detection and leave orphaned entries, so keep it on backup storage.
Does Autoxpose set up SSL when configuring the reverse proxy?
Yes, after you add a label to a container, Autoxpose creates the DNS record and configures the reverse proxy with SSL.
Answers sourced from github.com, github.com, github.com, github.com
Community
- Which Services do you expose? : r/selfhosted - Reddit (reddit)
- Reddit (reddit)
Collected 49 days ago - public community threads