Launchpad 0.62.1 alpha — build 260926001 This testing release combines the native macOS app with Launchpad server 0.62.1. The built-in server includes its Bun runtime; no separate Bun or Node.js installation is needed. Docker is required to run local apps. Public access: choose your tunnel and DNS style - Public access now offers two setups. Use this Mac's tunnel adopts a Cloudflare tunnel you already run here: the app shows the server's proof check by check, and Apply stays off until every check passes. Or let Launchpad create and manage a tunnel for you. - Choose how DNS reaches your apps: one record per app (the default) or one wildcard record. You can switch between them later without a gap in reachability. - An adopted tunnel is never changed. Withdrawing it removes only the DNS records and routes Launchpad added. - The Public access card now shows the DNS style and who owns the tunnel. Launches that check DNS first - A launch on a tunnel now reads DNS before it starts. If a record points the app's names somewhere else, the launch refuses and names the record, instead of succeeding with an app nobody can reach. - Names under your routing domain, including declared at: names, are served by this Launchpad directly. They no longer start a second tunnel. Fixed - An app's own Redis or database is now reachable only from that app, on every server. A component that connected by host and port no longer fails with NOAUTH. - A web dashboard left open past its 7-day session now asks you to sign in again in place, and returns to the same page. - The launchpad command-line tool finds the server's secret by itself on this Mac, so you no longer need to export LAUNCHPAD_SECRET. Own domain, name choices and declared names need a server that supports them. The built-in server in this release does. A server you connect to by address shows the declared names only once it runs Launchpad 0.51.0 or later. Alpha limitations - Once an installation has begun, it cannot be undone. Launchpad cannot prove that the installer has exited, so it will not restart the previous server behind it. If an install is cancelled or interrupted, finish it by downloading this release and replacing Launchpad yourself, then reopening it. - Installing an update requires the built-in server to be running and reachable. Servers you connect to by address are updated separately by their owners. - Signing and notarization verify the package, not successful Cloudflare configuration or Gate acceptance on your machine. Those remain alpha testing targets. - Names two levels below the app's host (*.*) are refused: no hostname front door can route them. Closing or quitting Launchpad leaves its registered built-in server running. Use the app's server controls to stop it. Running app containers are separate from the control-plane UI.