Build proposal

This is a proposed build, with a conceptual architecture. Any linked existing projects have their own documented scope and infrastructure.

Browse existing projects and remaining proposals →

Queue #10

Waiting for votes

LaunchDarkly on Cloudflare

Feature flags, environments, targeting, rollout rules, and edge evaluation on Cloudflare.

replaces LaunchDarkly D1 Durable Objects KV Workers

would replace

LaunchDarkly· feature-flags

Feature flags, rollouts, experiments, and targeting.

How it would work

A URL goes in, an API-ready result comes out. These are the stages the request flows through.

map01
Map the rented workflow
Identify the small-team job that actually needs replacing.
→
build02
Assemble the Cloudflare loadout
Pick the primitives that cover the core data, compute, auth, and delivery path.
→
ship03
Publish the useful version
Release a deployable build with limits, setup notes, and maintenance tradeoffs.

Concrete jobs it does

If you're paying LaunchDarkly for any of these, the proposed build would let you stop.

→Cover the small-team workflow people actually rent the SaaS for
→Expose a simple, deployable API
→Persist the right data in D1 and the right artefacts in R2
→Stay maintainable by one or two engineers

Config knobs

What you'll be able to tune from day one.

Workflow scope: core team workflow only
Deployment target: Cloudflare Workers + supporting primitives
Access model: simple auth and admin controls
Limits: documented scale and maintenance boundaries

proposed architecture

The Cloudflare loadout, wired together.

Architecture

Overview inferred from the listed Cloudflare services. Routes and connections have not been verified.

Public interface

Surfaces1

client / caller

interface not yet reviewed

→

↓

App

Workers

entry

request handler

→

↓

Bindings

relational data

Durable Objects

per-tenant state

small values, fast reads

what each tool does

Cloudflare feature

Function in the proposed app

D1tool 01

Track crawl jobs, pages, status, users, limits, and API keys.

Durable Objectstool 02

Durable Objects

Coordinate realtime state, locks, sessions, or per-customer actors.

KVtool 03

Cache settings, lightweight metadata, and fast lookup tables.

Workerstool 04

Workers

Public API, routing, auth checks, rate limits, and orchestration glue.

will build

+The core workflow small teams actually use every week.
+A deployable Cloudflare-native version with clear setup steps.
+Basic auth, data storage, admin screens, and operational visibility.
+A writeup that explains the useful limits and maintenance burden.

will not build

-A pixel-perfect clone of the SaaS being replaced.
-Enterprise governance, compliance guarantees, or managed support.
-Every advanced feature that only large teams need.
-A promise that replacing the rented tool is always the right call.

readme