pull down to refresh
Fair criticism. The fact that these answers were not immediately obvious means we buried the lead.
Blindport does not replace Caddy unless you want it to. In passthrough mode, Blindport forwards the original encrypted TLS stream to Caddy on your machine. Your certificates, Caddyfile directives, authentication, routes, and plugins stay where they are. There is nothing to port. If you need the original client IP, Blindport can send it using PROXY protocol v2. And if you want to get Let's Encrypt certs with HTTP-01 challenge, that is forwarded to Caddy as well (or Traefik or whatever you use).
Using a VPS with ssh -R or WireGuard is a valid alternative. Blindport offers the same basic trust boundary with less infrastructure to operate: Relay costs 3,000 sats per 30 days, requires no VPS maintenance, and uses ingress at two providers for improved resilience.
If you already enjoy maintaining your VPS setup, there may be no reason to switch unless you are unhappy with the uptime. Blindport is for people who want that architecture without paying for and administering an entire server.
For users without Caddy, blindportd can optionally manage the Let's Encrypt certificate and forward to a local HTTP service.
It is very challenging (at least for us) to trim this down to the essence. There are many details we want to share, but it's clear that "less is more".
We were wishing to get your feedback, and it happened to be the first comment :-)
Thanks, this was useful.
I think I get where you're going with it, I like the concept generally.
One idea maybe position it against stuff like ngrok, the included subdomain is itself a value add. (I see its a sub-sub domain, maybe offer the subs a higher level than below relay.*)
The sats-based payment too is a friction reduction in many cases, arguably more so than the VPS. That's buried in the cards, maybe move the CTA up higher where all someone has to do is enter a subdomain and they get an invoice and CLI snippet
An agent being able to get an SSL subdomain on the fly has a lot of value
Also be sure to add CLINK for subscriptions, especially for the clankers ;)
We were wishing to get your feedback, and it happened to be the first comment :-)
Feel free to ping any time, I like seeing new services for sats get cooking
eyes glazed over before I got too far, post and website needs distilled down to the essence.
There's 2 types of potential users for this
For 2, why would I look deeper into this rather than just run caddy locally for letsencrypt ssl termination and use ssh -R or wireguard for the reverse tunnel? Is it cheaper than a VPS or VPN? Does it replace Caddy? What about all my Caddy directives? Do I port those or is this another middleware infront of an existing reverse proxy?