Hi, I'm Devendra. I've spent the last few years doing DevOps: CI/CD pipelines, cloud infra, containers, Terraform. Most of my work has been making other people's software ship faster.
Now I'm building my own product, and I'm going to do it in public.
What I'm building
Virling answers one question that bugged me for a long time: which traffic sources actually lead to paying customers?
Most analytics tools tell you about visits. Your payment provider tells you about revenue. Joining the two usually means a data warehouse, a third-party tracker, or a pile of spreadsheets.
Virling keeps it small:
- One Rust binary, backed by DuckDB or SQLite
- A tiny script records visits
- It pulls payments (Stripe, Polar, LemonSqueezy, Dodo) with a read-only key, no webhooks
- It joins them using an id passed into checkout, so you see revenue per source
- Open source under AGPLv3, self-hostable
Why build in public
My DevOps background taught me that feedback loops matter more than anything. Shipping in the open is the shortest feedback loop I know. I'll share:
- What I build each week, including the boring parts
- Technical decisions (Rust, DuckDB, why AGPL)
- The numbers: waitlist, users, revenue, mistakes
What's next
Right now I'm working on the first usable version: one-command install and a demo with sample data, no signup needed.
If you've ever wanted to know which blog post, tweet, or channel actually paid off, follow along. Questions, criticism, and "have you thought about X" are all welcome in the comments.
You can also find me on X at @whodeven.
Day 1. Let's go. 🚀
Top comments (0)