IdeaWell

Project ideas from Hacker News discussions.

Cloudflare Flagship

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1. Cloudflare’s Flags vs. Vercel – permission & account isolation concerns

“Cloudflare are winning these days, they’re just lacking good fine‑grained permissions. You still have to make an entirely separate account for prod, which messes up SSO since one domain can only be bound to one account.” — aetherspawn

2. Fear of uncontrolled billing > “Will never use them without prepayment or spending limit options. Insane to be a bug, attack, or misclick away from a 6‑7 digit invoice.” — wahnfrieden

3. Feature flags are simple; outsourcing feels over‑engineered > “Feature flags are so ridiculously simple I have never needed to outsource this to someone else.” — throwaway613746

4. Rising interest in OpenFeature and vendor‑neutral flagging

“I have had a lot of experience with OpenFeature, and have early commits in a few of the client libraries. It's definitely the future of feature flagging, and the ecosystem is really growing.” — melwell64

🚀 Project Ideas

EdgeFlagger

Summary

  • Edge‑native feature flagging for Cloudflare Workers with per‑app token scopes and SSO integration.
  • Solves the fine‑grained permission and SR‑compatible redirect issues highlighted in HN discussions.

Details

Key Value
Target Audience Cloudflare Workers developers, SaaS founders, security‑focused teams
Core Feature Flag evaluation at the edge with token‑scoped access and JWT‑based SSO
Tech Stack Cloudflare Workers (JavaScript/TypeScript), D1 database, OpenFeature SDKs
Difficulty Medium
Monetization Revenue-ready: {subscription per active project}

Notes

  • HN users repeatedly cite “lack of fine‑grained permissions” and “account compromise risk” (e.g., corvad, atsaloli).
  • Provides SSO‑friendly per‑app tokens, eliminates shared account exposure, and can be used for SSR redirects.

OpenFlag Cloudflare Provider#Summary

  • Fully edge‑hosted OpenFeature provider offering targeting rules, rollouts, and audit logs without external network calls. - Addresses the desire for “no‑network‑request” flag evaluations that HN commenters crave.

Details

Key Value
Target Audience Teams adopting OpenFeature, CI/CD pipelines, enterprise feature‑flag users
Core Feature Edge‑only rule engine with built‑in segmentation, rollback, and audit history
Tech Stack Cloudflare Workers (Rust/Wasm), KV, OpenFeature spec compliance
Difficulty High
Monetization Revenue-ready: {pay‑as‑you‑go compute}

Notes

  • Quote from swyx: “only 2 hard problems…” and many HN posts discuss needing “more fine‑grained permissions”.
  • Eliminates external API dependency, reduces latency, and can be toggled instantly via Workers KV updates.

FlagSync CLI

Summary

  • CLI tool that auto‑generates OpenFeature‑compatible flag wrappers from existing codebases and syncs them to Cloudflare KV, enabling zero‑cost flagging.
  • Meets the “simple JSON commit” and “no‑new infra” expectations from HN discussions.

Details

Key Value
Target Audience Open‑source contributors, early‑stage startups, hobby developers
Core Feature Scans repo for feature‑flag patterns, emits OpenFeature SDK code, pushes flags to KV
Tech Stack Node.js CLI, ESLint parser, Cloudflare KV API
Difficulty Low
Monetization Hobby

Notes

  • “Feature flags are just a boolean in a database” (bluelightning2k) but the tooling around them matters; FlagSync provides easy admin UI and rollout controls without extra services. - Can be used alongside OpenFeature, aligning with wilj’s desire for “OpenFeature‑compatible” solutions.

PermissionGate Cloudflare#Summary

  • SaaS that adds enterprise‑grade per‑project billing caps, quota enforcement, and RBAC to Cloudflare Workers and related services, preventing accidental large invoices. - Directly addresses “will never use them without prepayment or spending limit options” concerns.

Details

Key Value
Target Audience Cloudflare enterprise prospects, security‑conscious teams, finance‑oriented users
Core Feature Dashboard‑driven quota limits, automatic invoice alerts, role‑based access to services
Tech Stack Cloudflare Pages front‑end, D1 for quota storage, Cloudflare Workers for enforcement
Difficulty Low
Monetization Revenue-ready: {tiered subscription per account}

Notes

  • Multiple HN comments (wahnfrieden, 7thpower) express “need for prepayment or spending limit options” and fear of “doomed” invoices.
  • Provides the missing financial safety net that keeps developers from adopting Cloudflare for production workloads.

Read Later