What would stop you from trying Olegpustovit (https://nexo.sh/posts/building-your-own-https-tunnel/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).
Page reviewed
Build Your Own HTTPS Tunnel in 300 Lines of Go | Oleg Pustovit
https://nexo.sh/posts/building-your-own-https-tunnel/ (opens in a new tab)
10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations
Simulated interest
AI synthesis, not measured demand
Suggested price range
Median $0 · simulated willingness to pay
Response sentiment
What this panel suggests
The main blocker is not the tunnel concept itself, but the work required to operate it. Respondents consistently describe the self-hosted setup as too much overhead for something they want to try this month: provisioning or maintaining a VM, configuring Caddy and Cloudflare DNS, handling wildcard TLS, and troubleshooting when it breaks. That friction matters because the page positions Olegpustovit as lightweight, self-hosted, and $0/month, yet the audience still perceives meaningful operational cost. Today, several would stay with a paid plug-and-play service because it minimizes setup, while others would rely on existing tunnel options such as ngrok or Cloudflare Tunnel. The strongest willingness to pay is very limited: the panel median is $0, with only an outlier indicating up to $20/month, and even that was conditional on a managed-service experience rather than the DIY version. Overall sentiment is mostly neutral rather than enthusiastic or hostile; the product is seen as technically elegant, but not worth the activation effort for most buyers right now.
Pricing & positioning
Do not optimize for immediate paid conversion from this audience. The strongest pattern is willingness to try only if the product removes the self-hosting burden; otherwise, most respondents anchor at $0. A paid offer would likely need to be a managed version with one-click setup, hosted infrastructure, and support.
The supplied willingness-to-pay data centers at $0, with only a single higher outlier up to $20/month. That suggests the current self-hosted proposition is valued more as a DIY utility than a subscription product. If monetized, pricing would likely need a separate managed tier rather than charging for the self-hosted binary itself.
Recurring themes
“The main thing stopping me from trying something new like this is the setup overhead.”Read Adam Labadie’s response →
“Today, we use a paid service that's mostly plug-and-play, and while it has its own friction points, the setup overhead is minimal.”Read Mayson Brouwer’s response →
Objections to investigate
- High setup complexity (domain, VM, custom binaries)
- Operational maintenance burden
- Lack of managed service option
Use these findings to plan customer interviews or experiments. How to interpret AI research
What the panel said
Click a name to open that persona’s full profile.
Adam LabadieneutralRight now, I'm managing my client demos by just spinning up a quick HTTPS tunnel and logging the temporary URLs in a Google Sheet. It's a bit manual, but it works for the 3-4 projects I juggle. The main thing stopping me from trying something new like this is the setup overhead. The description mentions needing a domain, a VM, and building custom binaries with Caddy and Go. That sounds like more effort than I currently put in, even with the Google Sheet. I'd need to see a much simpler, perhaps even more automated, setup process before I'd consider switching. Since this solution is described as a $0/month Oracle Cloud VM, I wouldn't pay for it.
Simulated interest: 20/100
Marilyn TowneneutralThis seems like an interesting project, but what stops me from trying it this month is the setup overhead. My current process, while manual, is established. We use a spreadsheet and a free tunnel service to rotate ephemeral HTTPS links for builds and bug repro steps. It's functional, albeit time-consuming. Building and managing a self-hosted solution, even with Go and Caddy, requires significant time investment to configure the VM, domain, and Caddy with wildcard TLS. The article mentions requiring a domain and a VM. My maximum acceptable price would be $0 per month. This is a self-hosted project, and my current solution is also free, albeit with a higher cognitive load. I'm evaluating whether to build something similar myself to eliminate the risk of link expiration.
Hanna KrauspeneutralBuilding my own tunnel is an interesting idea, especially since it's self-hosted and the author claims it's free. Today, we mostly use a paid tunneling service for specific projects, and Notion for our access lists. The main hurdle for me with this approach would be the setup and maintenance overhead. We're a small team, and I'm already juggling a lot with prototyping and client communication. While the idea of a $0/month solution is tempting, I'm not sure I have the bandwidth to manage the VM, Caddy configuration, and potential troubleshooting. If it were a more integrated, turnkey solution, I might consider it. For now, I wouldn't pay for this specific solution because the DIY aspect is a significant barrier.
Simulated interest: 20/100
Kartik KaulneutralThis Olegpustovit project sounds intriguing, especially the self-hosted aspect and the $0/month Oracle Cloud VM. My current approach involves using free tools like ngrok or Cloudflare Tunnels, mainly because my SaaS project is still in early beta with just a few testers. I meticulously document everything in my personal wiki to keep track. The main hesitation would be the setup complexity and ongoing maintenance of a self-hosted solution like this. While I appreciate the DIY approach and the potential for zero cost, the time investment in setting up and managing the VM, Caddy, and the tunnel itself might take away from core product development, which is already a challenge with my day job. Given my current situation, I wouldn't pay for this, so my maximum acceptable price is $0 per month.
Simulated interest: 20/100
Walgierz MuszyńskineutralWhat would stop me from trying this? Primarily, it's the significant time investment required to set up and maintain a new, custom solution like this. My current process, while homegrown, is documented and operational. I manage our Caddy configurations in Git and have a system in place. Introducing this would mean re-evaluating the existing setup, potentially debugging new issues, and updating our internal wiki, which is already a challenge. Given my focus on stability and efficiency, and the fact that our current reverse proxy setup works for our partner testing needs, I'm hesitant to divert resources. The article mentions a $0/month Oracle Cloud VM, which is appealing for cost, but the operational overhead is the main concern. Therefore, I wouldn't pay anything for this month. My maximum acceptable price is $0 per month.
Simulated interest: 10/100
Charlotte LecomteneutralThis is interesting because it sounds like you've built something very similar to what I use daily. My current setup involves managing port availability with my team and setting up localhost services with HTTPS for demos. The fact that this is self-hosted and requires no paid plans, with a $0/month Oracle Cloud VM, is appealing. However, the setup seems to involve more technical steps than I'm usually looking for during a support call – configuring Caddy with wildcard TLS and managing DNS via Cloudflare is a bit more involved than simply spinning up a service. I already learned Go to understand tunneling tools better, so I appreciate the transparency, but I'd need to see how easily this integrates into my existing workflow and if it saves me time, or adds more complexity. For now, I wouldn't pay for this, as the core functionality seems to be covered by open-source tools and my own learnings. My maximum acceptable price would be $0 per month.
Simulated interest: 40/100
Pete GloverneutralThe whole idea of building your own tunnel is interesting, and the fact that it's self-hosted with no paid plans is definitely appealing for my budget. Today, I'm using a plain text file to keep track of free tunnel links, which works but is a bit manual. The main thing stopping me from trying this right now is the setup. It sounds like I'd need a domain, a VM, and some command-line work, which adds complexity I'm not sure I have time for with just one contractor and my current workload. I'd prefer something a bit more straightforward if possible. Honestly, if this is something I'd have to maintain and troubleshoot myself, I can't justify paying for it. My maximum would be $0 per month.
Simulated interest: 10/100
Mayson BrouwerneutralThe biggest hurdle for me with this is the setup. It sounds like a cool project, and I appreciate the $0/month Oracle Cloud VM aspect, but building your own tunnel requires a fair bit of effort from my side – setting up a domain, a VM, compiling Caddy with plugins, and managing it all. Today, we use a paid service that's mostly plug-and-play, and while it has its own friction points, the setup overhead is minimal. I'd pay around $20 per month if it meant a significant reduction in setup and maintenance time compared to building it myself.
Simulated interest: 40/100
Winston Carroll-BeernegativeHonestly, the fact that this is a DIY project, requiring setup on an Oracle VM with custom Caddy builds, is a bit of a roadblock. My current workflow relies on temporary public URLs generated on my laptop for quick demos. While I appreciate the self-hosted aspect and the $0/month Oracle Cloud VM mentioned, the setup complexity and maintenance overhead for something like this isn't something I have the bandwidth for right now. I'm already managing a shared spreadsheet for our demo links, and adding server management on top is a step too far. If it were a managed service that offered similar functionality with minimal setup, I might consider it, but as is, I wouldn't pay for this.
Simulated interest: 10/100
Dharani AcharineutralThe concept of a self-hosted HTTPS tunnel is interesting, and the project's description as a "$0/month Oracle Cloud VM" solution is appealing given our current reliance on free tools and scripts. However, the primary concern stopping me from trying this *this month* would be the significant time investment required for setup and maintenance. Today, we manually manage our links in a shared document. While this project aims to automate exposing local dashboards, it requires setting up a VM, configuring a domain, building custom binaries with `xcaddy`, and managing Cloudflare DNS. That's a considerable learning curve and ongoing effort for a small team, especially when my focus is on ensuring the reliability of our existing pipelines. If this were a managed service, I might consider it, but the self-hosting aspect adds a layer of complexity that feels like a step backwards from a purely functional standpoint, even if it's free. Therefore, I wouldn't pay anything for this specific DIY solution.
Simulated interest: 10/100
Keep exploring.
Find your next question or see which topics divide AI panels.
What would you ask next?
Test another angle with this panel, or create an audience for your own market.