# Routeup – stable local HTTPS URLs and opt-in public tunnels — retained record

> Retained lobsters record from lobsters.

Canonical: https://highsignal.app/data/records/84d21b537da04a66

[← sources](https://highsignal.app/data)


source: [lobsters](https://highsignal.app/data/lobsters) published 2026-08-24 19:08 ingested 2026-08-25 06:44

[original source ↗](https://routeup.dev/)

## retained text



```
<p>I built Routeup around a simple idea: local apps should use their real names.</p>
<p>It was inspired by <a href="https://portless.sh/" rel="ugc">Portless</a>, but I also wanted built-in public tunneling, selective path exposure, request inspection, and live logs.</p>
<p>Instead of opening <code>localhost:3000</code>, I can give a project a stable, trusted HTTPS URL and keep using it across restarts:</p>
<pre lang="text"><code>https://example-app.localhost
</code></pre>
<p>The app stays local by default. When an external service needs access, I can expose the whole route or only selected paths such as <code>/api/webhooks/*</code>:</p>
<pre lang="text"><code>local:  https://example-app.localhost
public: https://example-app.try.routeup.dev
expose: /api/webhooks/*
</code></pre>
<p>Exposure has its own lifecycle. I can expose an already-running route from another terminal and stop sharing it without stopping the local app.</p>
<p>For quick, temporary exposure, Routeup provides names under <code>*.try.routeup.dev</code> without requiring an account or token. For stable public names, a token claims a namespace such as <code>team.routeup.dev</code>. Apps can then use names beneath it, such as <code>api.team.routeup.dev</code> and <code>docs.team.routeup.dev</code>. The same namespace model works with a self-hosted Routeup server and your own domain.</p>
<p>Routeup grew out of frustrations I had using ngrok and localtunnel. They could expose a port, but their tunnel-first model was not the workflow I wanted. I wanted the app to have a stable local identity first, with public access added only when and where it was needed.</p>
<p>I use this workflow heavily at work and for personal projects. Routeup currently supports multiple path targets behind one origin, repository-level configuration, running an app command, request inspection, hosted public URLs, and self-hosted servers.</p>
<p>The local workflow requires no account, token, DNS, or remote server. Routeup is a single Go binary, has no CLI telemetry, and is MIT licensed.</p>
<ul>
<li><a href="https://routeup.dev" rel="ugc">Website and documentation</a></li>
<li><a href="https://github.com/mukul-mehta/routeup" rel="ugc">Source code</a></li>
</ul>
<p>I'd appreciate any feedback on the project, especially ideas for improving the workflow, documentation, or features. If you run into any issues during setup or while using the tool, please <a href="https://github.com/mukul-mehta/routeup/issues/new/choose" rel="ugc">open a GitHub issue</a> or email <a href="mailto:help@routeup.dev" rel="ugc">help@routeup.dev</a>.</p>
<p><a href="https://lobste.rs/s/daohlz/routeup_stable_local_https_urls_opt">Comments</a></p>
Tags: go, networking, show, vibecoding
```



document fetched 2026-08-25 07:57
