Project ideas from Hacker News discussions.

Dropping Cloudflare for Bunny.net

📝 Discussion Summary (Click to expand)

Top 3 Themes from the Discussion

# Theme Supporting Quote(s)
1 Pricing & entry barrier – Many users point out that even a modest fee (≈ 1 €/month) or the need for a credit‑card can deter hobbyists and non‑US users. Unfortunately it doesn’t offer free hosting for hobbyists. Even for superficial traffic you’ll have to pay 1 euro a month (plus VAT)” — mhitza
I’m not in the USA or earn USA salaries, but I can pay 1 euro a month for a thing.” — joehart42
It’s not about the price it’s about the barrier. Even if I love a service, I won’t get very many people to try it if they need to enter a credit card.” — shimman
2 Cheap, low‑commitment alternatives – Users praise services like Bunny.net, DNSimple, or LuaDNS for offering predictable, low‑cost plans (often <$2/mo) that eliminate the “free‑tier lock‑in” feeling. I love bunny.net. For my use case it provides lower latency than Cloudflare.” — smartbit
We use them for a couple of things – very happy. I think probably the best reason (other than service robustness): support.” — tao_oat
Second DNSimple. Cheap to start and lots of nice features/support if you grow.” — corford
3 Vendor lock‑in & multi‑CDN desire – Several commenters warn against relying on a single provider and express a need for fail‑over or hybrid setups to avoid outages and surprise bills. It would be super nice to have a setup that uses multiple CDNs w/ automatic failover.” — Bender
The whole point of paying someone else to handle a problem for you is that you don’t have to worry about it. If you go all in on a provider and then suddenly find out that you’ve been switched to a paid plan in the middle of your vacation, that’s not a place anyone wants to be.” — edoloughlin
If a parent can buy their kid a computer, they can pay 1 euro a month for a CDN… This is a bad argument.” — tensor (highlighting the lock‑in critique)

The summary is intentionally brief, focusing on the three most recurrent topics with direct user quotations.


🚀 Project Ideas

Generating project ideas…

Multi‑CDN Failover Gateway

Summary

  • Provides automatic traffic routing across multiple CDNs to ensure highest uptime and lowest cost.
  • Eliminates single‑point‑of‑failure concerns raised by Cloudflare outages and vendor lock‑in.
  • Offers a truly free tier for hobby projects with seamless upgrade path.

Details

Key Value
Target Audience Hobbyists, indie developers, small SaaS owners who want reliable edge delivery without paying for enterprise plans
Core Feature Multi‑CDN routing with health‑check failover and cost‑aware load balancing
Tech Stack Node.js backend, GraphQL API, Kubernetes for scaling, Redis for state, OpenResty for edge routing
Difficulty Medium
Monetization Revenue-ready: $0.01 per 1k DNS queries, $0.02 per GB transferred

Notes

  • HN commenters repeatedly cite the credit‑card barrier and fear of surprise bills; this service removes both by offering a free quota and credit‑card‑optional sign‑up via SEPA.
  • The “automatic failover” idea directly addresses the desire for multi‑CDN solutions without manually managing each provider’s DNS.
  • Community‑driven plugins can add new CDNs, increasing lock‑in‑free portability.

Zero‑Credit‑Card Edge Hosting

Summary

  • Enables developers to deploy edge containers and static sites without ever entering a credit card.
  • Uses alternative payment methods (SEPA, bank transfer, crypto) to lower the entry barrier for non‑US users.
  • Provides a generous free tier for low‑traffic hobby projects, with clear export tools. ### Details | Key | Value | |-----|-------| | Target Audience | International hobbyists, students, and open‑source contributors lacking credit cards | | Core Feature | Credit‑card‑free sign‑up + prepaid credits that can be topped up via SEPA or crypto; automatic domain + CDN provisioning | | Tech Stack | Python backend, Docker edge functions, Cloudflare API compatibility layer, PostgreSQL | | Difficulty | High | | Monetization | Revenue-ready: $0.005 per GB served, $0.001 per compute second |

Notes

  • Directly answers the “eur a month is too much” and “credit card barrier” concerns voiced in the thread.
  • Users can start with a completely free allocation and upgrade only when they need more resources, matching the “pay‑as‑you‑go” desire.
  • Export/import of edge function code and DNS records is built‑in, facilitating easy migration and reducing lock‑in fears.

Edge Function Marketplace with Vendor‑Neutral Export

Summary

  • A marketplace where developers can discover, deploy, and share edge functions (similar to Cloudflare Workers) that can be exported to any provider. - Includes a free sandbox tier for testing and a simple CLI to bundle and move functions across platforms.
  • Solves the lock‑in anxiety mentioned by users who want to avoid proprietary APIs.

Details

Key Value
Target Audience developers building edge logic, API gateways, and hobbyists wanting portable code
Core Feature Vendor‑neutral function packaging + automatic CI/CD deploy to any supported edge host (Cloudflare, Bunny, Netlify, etc.)
Tech Stack Rust compiler toolchain, WebAssembly runtime, Docker, GitHub Actions, OpenAPI spec
Difficulty High
Monetization Revenue-ready: $5 per month per active function deployment, with a free tier of 100 deployments

Notes

  • The discussion about “WinterTC” and vendor lock‑in shows a clear appetite for an open edge‑function standard; this project delivers it.
  • By charging a modest subscription only after a function is actively used, the model stays hobby‑friendly while being revenue‑ready.
  • Community can contribute adapters for new providers, keeping the ecosystem diverse and reducing the impact of any single CDN’s pricing changes.

Read Later