SHIPPED · v1.35.0
Publish an App with Cloudflare Tunnel & Migrate from Dockge
New
Publish an App with Cloudflare Tunnel
Migrate from Dockge
Improved
Connect one app to another over a private network — let your API reach its database or cache by a stable private name, over traffic that never leaves the server or touches the public internet
Pick the exact services and port — choose which part of each app connects and which container port to use, with a suggested connection address you can edit
Close the public port safely — optionally remove the producer's public port after the private link is tested, and Server Compass remembers the exact setting so it can offer to restore it later if the port is free
Know when a connection breaks — if you rename or remove a connected service in a later edit, the link is clearly marked "Drifted" instead of silently failing, so you can fix it or reconnect
Clearer container-vs-host ports — connections use the app's internal container port (for example 5432 for Postgres), with guidance so you don't accidentally use the published host port
See your networking in one place — private connections and tunnel routes now sit together under Tunnel & Networking and in each app's Overview
Fixed
Fixed deployments appearing stuck after Server Compass was closed mid-deploy — a deployment interrupted by closing or restarting the app is now marked as interrupted on the next launch with a clear message to retry, instead of staying "in progress" forever
Dockge migration screen listing every stack discovered over SSH, each ready to adopt in place 
Server Migration source picker with Dockge selected as the platform to import stacks from 
Tunnel & Networking overview showing a live Cloudflare Tunnel with a healthy public hostname route 
Dockge decommission step letting you retire the old Dockge install after stacks are adopted 
Public hostnames list mapping Cloudflare domains to specific apps and container ports 
Manual DNS setup guidance shown when an existing Cloudflare record needs review before changes apply 
Guided Add Public Hostname flow choosing the Cloudflare domain, the app, its port, and HTTP vs HTTPS 
Review Changes screen previewing the exact DNS and tunnel edits before anything is applied 
Diagram of outbound-only tunnel traffic flowing from the app through Cloudflare with no inbound ports open 
Connect Cloudflare Account panel for adding an account and API token, tested and stored encrypted locally 
Tunnel & Networking empty state prompting you to connect a Cloudflare account to publish an app 
Cloudflare API token permissions guidance listing the exact scopes the tunnel setup requires dockge migration discovered services dockge migration source picker cloudflare tunnel overview live dockge migration decommission cleanup cloudflare tunnel public hostnames cloudflare tunnel manual dns setup cloudflare tunnel add public hostname cloudflare tunnel review changes cloudflare tunnel outbound flow cloudflare tunnel connect account cloudflare tunnel networking empty state cloudflare tunnel token permissions