This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
MultiDocker
Run every docker-compose project at once, no port wars
Every docker-compose project on your Mac gets its own real HTTPS domain — shop.coding9.test instead of localhost:8081, :8082, :8083. MultiDocker never edits your compose files. It generates an override that strips host port mappings, attaches the containers to one shared Traefik edge proxy and issues locally trusted certs via mkcert. Secure cookies, redirects and OAuth callbacks behave like production. Three commands: init, up, open. Native macOS app with self-update included.
Hey Product Hunt 👋
We build client projects for a living, which means a dozen stacks on one Mac: a Shopware shop, a Strapi site, an old monolith. Every one of them wants port 80. So you do what everyone does — 8081, 8082, 8083 — and you edit compose files you don't own, which then blow up on the next git pull.
The port juggling was annoying. The real problem was that localhost is not production: Secure cookies, OAuth callbacks and anything cross-subdomain behave differently there, so bugs show up in staging that never showed up locally.
MultiDocker fixes this at the edge instead of in your files. "mdocker init" writes a separate override file next to your project, strips the host port mappings, attaches the containers to one shared Traefik network and gets a locally trusted certificate from mkcert. Your compose file is never touched — git status stays clean. You get https://shopware-shop.coding9.test, and everything behaves the way it will in production.
It's macOS-native (SwiftUI) with the CLI as its backend, works with both OrbStack and Docker Desktop, and installs its own runtime on first launch.
This is a beta and I would genuinely like to hear where it breaks — especially with unusual compose setups. Ask me anything.
About MultiDocker on Product Hunt
“Run every docker-compose project at once, no port wars”
MultiDocker was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #139 on the daily leaderboard. Every docker-compose project on your Mac gets its own real HTTPS domain — shop.coding9.test instead of localhost:8081, :8082, :8083. MultiDocker never edits your compose files. It generates an override that strips host port mappings, attaches the containers to one shared Traefik edge proxy and issues locally trusted certs via mkcert. Secure cookies, redirects and OAuth callbacks behave like production. Three commands: init, up, open. Native macOS app with self-update included.
On the analytics side, MultiDocker competes within Mac and Developer Tools — topics that collectively have 622.4k followers on Product Hunt. The dashboard above tracks how MultiDocker performed against the three products that launched closest to it on the same day.
Who hunted MultiDocker?
MultiDocker was hunted by Alexander Schikowsky. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of MultiDocker including community comment highlights and product details, visit the product overview.
Alexander Schikowsky