Edges vs. Tunnels: Choosing the Default for Multi‑Service Exposure in ngrok v4

Goal

Determine whether the default configuration for exposing multiple local services should use ngrok v4 edges or the legacy v3 tunnels format, given the constraints of plan limits, protocol flexibility, and migration effort.

Constraints & Uncertainty

• Edges enable shared subdomains and HTTP/2 but require a paid plan and explicit hosts and protocols entries.
• Tunnels are free, simpler, and automatically supported by the v4 CLI, but allow only one protocol per service.
• The ngrok config migrate command warns of incompatibilities but does not fully convert all fields, leaving manual editing necessary.
• Future releases may add automated migration tooling, but the timeline and feature set remain unspecified.

Specific Questions

1. For a deployment that needs to expose three HTTP services on the same subdomain, should the default be an edge that hosts all three or separate tunnels?
2. How does the cost and bandwidth limitation of a paid plan influence the choice when multi‑service exposure is required?
3. What is the recommended manual adjustment workflow if the automated migration from a v3 tunnels file to a v4 edges configuration fails to preserve all protocol settings?