What we've learned building Reloop in public, from the first commit to shipping real features, growing the community, and staying focused.
Why we build in public
Building in public forces clarity. When you have to explain what you're working on and why, you can't hide behind vague roadmap items. It also builds an audience before you have a product, and creates accountability that solo or small-team projects often lack.
Lesson 1: Ship something embarrassingly early
The first version of Reloop was a Docker Compose file and a basic SMTP relay. No dashboard, no API, no analytics. We shared it anyway. The feedback shaped every subsequent decision more than any internal planning session.
Lesson 2: Documentation is marketing
Every time we wrote a "how to deploy on Coolify" or "how to configure DKIM" guide, we got inbound traffic from people who needed exactly that. Documentation compounds. It's the gift that keeps giving without ongoing effort.
Lesson 3: GitHub stars lag real interest by weeks
When something gets shared on Hacker News or a relevant subreddit, stars spike 3–5 days later, not immediately. Don't judge the success of a post by the day-of numbers.
Lesson 4: The community knows what to build next
Our most-requested features have consistently surprised us. Things we assumed were "nice to have" turned out to be table stakes for certain users. The issues tab and Discord are better product research than any framework.
Lesson 5: Consistency beats intensity
Shipping once a month consistently, with updates and changelogs, compounds over time. A two-week sprint followed by silence loses momentum and community trust.
What's next
We'll keep shipping in public. If you want to follow along, watch the GitHub repo, join the Discord, or subscribe to the blog. We're just getting started.
Read more
Why We Open-Sourced Our Email Infrastructure
The story behind Reloop: why we built an open-source alternative to SendGrid, Resend, and Mailgun, why email infrastructure is too critical to rent forever, and what we're changing.
Self-Hosted Email Infrastructure: When and How
Why teams self-host email, what Reloop gives you out of the box, and how to deploy with Docker Compose.
Introducing Reloop: Open-Source Email Infrastructure Developers Actually Want to Use
Open-source email infrastructure for indie hackers, startups, product teams, and enterprises. Ship transactional mail, agent inboxes, and inbound on Reloop Cloud or self-host: same product, no lock-in.
The Hidden Costs of Disposable Emails (And How Blocking Them Saves You Thousands)
From CRM contact-tier inflation to free-trial credit farming and burned domain reputation, here is the real cost of disposable emails and how a free temp email checker saves thousands.
Ship your first email with Reloop
in minutes.
Open-source, deliverability-focused, and yours to self-host or run on Reloop Cloud. No lock-in, no rewrite later.