DEV Community

Cover image for I Built a Developer Tool in 2 Days. Distribution Took 2 Weeks and Still Counting.
zerodrop
zerodrop

Posted on

I Built a Developer Tool in 2 Days. Distribution Took 2 Weeks and Still Counting.

This isn't a success story. It's an honest account of what it actually feels like to build something real from India and try to get the world to notice it.


How ZeroDrop Started

I was testing email flows for a side project. Using my personal Gmail. Within a week my inbox was a mess — test signups, verification emails, password resets, all mixed in with my actual life.

I went looking for a solution. Every option I found either showed me ads, asked me to create yet another account, or required me to spin up a Docker container in my CI pipeline. MailHog was the standard recommendation — except it hasn't been maintained since 2020 and requires running a fake SMTP server just to catch a test email.

So I built ZeroDrop. Disposable email inboxes for CI pipelines. No Docker. No signup. No ads. Send a real email to a randomly generated address, the SDK catches it, your test passes.

Two days to build the basics. One week to polish it enough that I wasn't embarrassed to show it.


Then the Real Work Started

Building was the easy part. I say that genuinely — the technical problem was straightforward. Cloudflare Email Routing catches emails at the edge, a Worker parses them, Upstash Redis stores them for 30 minutes, the SDK polls and resolves. Clean architecture, $0 infrastructure cost, works globally.

What followed was two weeks of fighting platforms I didn't build for and didn't build me.

Hacker News.
I submitted. It got flagged before most people could read it. I tried again with a different angle. Flagged again. I have 9 karma. HN is still the ideal place to reach technical builders — that's not the problem. The problem is you have no idea who flagged you or why. Was it a bot? Was it a user who saw "new account" and assumed AI slop? It's not 2016 anymore — the paranoia about generated content has made it harder for real builders with new accounts to be heard. The product never got a fair read.

Reddit.
I commented on communities I'd been watching and learning from for months. Banned. No warning, no appeal that went anywhere. The account was new. That was enough. Whether it was bots or downvotes, the result was the same — invisible.

Stripe.
This one hurt the most because it wasn't about karma or account age. Stripe has been invite-only in India since May 2024. Every modern payment platform — LemonSqueezy, Polar — uses Stripe under the hood for identity verification. They all hit the same wall. The tool I built for developers globally couldn't collect a single dollar globally because I'm Indian and I don't have an invitation from a US company.

Razorpay works. But Razorpay is Indian-facing. The developers I'm trying to reach are paying in USD on Stripe-native checkout pages. The gap between "I built this" and "I can get paid for this" is a wall that most Indian developers hit and never talk about publicly.


What Nobody Tells You

The internet says build in public. Ship fast. Get feedback. Most of the "build in public" playbooks were written by people who already had Stripe accounts and established platform presence. The advice is real — the context was just different.

Building from India in 2026 means:

You can build anything. The infrastructure is global, the tools are accessible, the talent is world-class. Indian developers are some of the best engineers on the planet.

But the moment you try to distribute or monetize globally, you hit systems designed for a different geography. Payment processors that require invitations. Communities that weight account age over product quality. Platforms where the algorithm decides before a human does.

None of this is new. Indian developers have known this forever. We just don't say it out loud enough.


What Actually Works

Everything I can control works.

The green CI badge on the example repo — works. The npm package with OTP auto-extraction — works. The GitHub Action on the Marketplace — works. The articles I've written are being cited by other sites without me doing anything. The SDK downloads are growing organically. The status page shows 100% uptime.

The product is genuinely good. I know that not because a platform validated it but because the code runs, the tests pass, and the emails arrive in under a second via SSE.

That's the only validation that actually matters.


What I'd Tell Another Indian Developer

Build. Ship. Document it.

Don't spend your energy trying to get karma on platforms that don't value what you built — they value how long you've been posting there. Don't chase Stripe integration before you have paying customers. Don't expect Reddit to welcome a new account commenting about something real you made.

Find the thing you can control and make it undeniable. For me that's the code, the articles, and the npm downloads. Those compound quietly while I stop refreshing HN.

The distribution will come. But it will come from the product being genuinely useful — not from a platform deciding your account is old enough to be heard.

Build for Indian developers first. We are a massive, underserved market that understands exactly what you built and why you built it. The global market will follow.


ZeroDrop is free and open source. No signup, no Docker, no ads.

SDK: npmjs.com/package/zerodrop-client

GitHub Action: github.com/marketplace/actions/zerodrop-create-inbox

Live sandbox: zerodrop.dev

Top comments (0)