# Marcus Lindqvist, Founder at Claimflow (solo, 1 contractor) — read of api-rate-limit-proxy-for-indie-projects, June 14 2026

> 7 years backend engineering, 2 years indie hacking, currently building a document AI tool for small insurance adjusters. Run every morning at 6am before my 4-year-old wakes up and that's when I catch up on HN.

## How I got here

11pm on a Thursday. I'd just pushed a hotfix after OpenAI 429s started dropping user requests in production. Googled "openai 429 queuing without redis" and ended up in a Reddit thread from 2023. Someone in the comments had linked this page about six months ago. I clicked it the way you click anything at 11pm: hoping someone already solved this so you can go to bed.

## What I clicked first

The before/after code block. That's the right move. You show me my exact code -- `if (response.status === 429) { // Retry logic. Exponential backoff. Manual queue...` -- and then show me what it looks like after I use your thing. I've seen a hundred landing pages that explain the problem in marketing language. This one put my actual code on screen. I scrolled back up to the top after reading that.

## Where I paused

The scoring table. Specifically this: `$-4,560 Year-1 take-home (Fermi)` and `1 in 6 Meaningful-success odds`. I stared at this for a solid minute. I've never seen a product page publish a negative revenue estimate for the product it's selling. That either means whoever built this is unusually honest or this page isn't selling what I thought it was selling. I read it three more times and landed on: this is not a live product. It's an idea being sold as a dossier. "We shipped the strategy package; you ship the customer conversations." So the proxy doesn't exist yet. I'm not buying a proxy. I'm being pitched on buying the right to build and sell one.

## What I distrusted

Two things.

First, "Your App Never Crashes" in the step-3 header. That's a guarantee nobody should make about a proxy they don't have in production yet. What happens when MY proxy goes down? Now I've introduced a new single point of failure between me and OpenAI. The page does not acknowledge this.

Second, the pricing: "$7/mo for startups. Per-request pricing scales with your volume. No surprises." There are no actual numbers here. Per-request pricing scales HOW? What does it cost at 10k requests/day vs 100k? The "$7/mo" is a floor that tells me nothing about what I'd actually pay once I need this thing.

Also -- and this is the thing that confused me most -- by the time I got to "Adopt this idea -- Browse free. Unlock for $5. Adopt for $99" I had to re-read the whole page. The top half reads like a live SaaS product. The bottom half reveals it's an idea kit. That tonal whiplash is jarring. The hero says "Get Started Now" like I can deploy it right now. I can't.

## What would convince me

I want to see the actual GitHub repo. Not "open-source option available on GitHub" with no link. Show me the code exists. A repo with commits from the last 30 days with a working Docker image I can pull and point at OpenAI in 10 minutes would make this real. That's it. That's the whole thing. I do not need a case study. I need to see that the proxy handles a 429 correctly in a way I can verify.

If this is truly a "buy the idea and build it yourself" product, I want one operator who bought the $99 package and shipped something. Just one. What did they build. Does the queue actually hold up under burst traffic or does it just delay the crash by 30 seconds.

## What I'd ask in an email reply

1. The managed tier -- when you say "use our managed tier," does that tier exist today or is that part of what I'd be building if I bought the dossier? I genuinely cannot tell from the page.

2. The proxy is stateless. Where does the queue live under load? In memory? That means if my proxy instance restarts mid-queue I lose all buffered requests. What's the recovery story there?

3. You show OpenAI and Anthropic as supported providers. Does the proxy handle streaming responses (SSE / chunked transfer), or only standard request-response? Because I use streaming for the chat interface and that's where most of my 429s actually happen.

## Verdict: on-the-fence

The code-first approach is the most honest thing on the page and it made me stay. But I spent half my reading time figuring out what was actually for sale, and that's not a problem the product should create. If the repo exists and the Docker image runs, I'd reply.

---
*Memo by skeptic persona, generated 2026-06-14. Studio breaks own self-grading loop.*