Look, pull up a chair. I'm doing my quarterly "open the books" post, and this one has been a long time coming.
For the last 18 months, I've been running what the internet calls a "build in public" experiment. That means I share my actual revenue, my actual struggles, and the actual tools that move the needle — not the polished LinkedIn version where everyone pretends everything is on fire and growing 400% MoM. Some months are great. Some months I lose money. And today, I'm breaking down the full stack that gets me to roughly $2,000+ per month in side income as a working developer.
If you've ever wondered whether developer side hustles actually work in 2026, here's my real numbers.
The Honest Disclaimer First
Before I get into the breakdown, let me be upfront: this isn't a "quit your job" story. I still have my full-time dev role. These numbers represent everything I earn outside of that salary, and they're the result of about 12-15 hours per week of work on evenings and weekends. I also want to be transparent that not every month looks like this. Some months I'm up 30%. Some months I'm down 20%. What I'm sharing is a rolling average, not a guaranteed outcome.
Okay, with that out of the way, let's get into it.
Stream
1: Freelance Contract Work — The Income I Don't Love Anymore
Freelancing was my first side hustle, and for a long time, it was my only side hustle. The pitch is simple: you have skills, clients need skills, money changes hands.
Here's my real numbers: I bill between $100 and $150 per hour depending on the project, and I do maybe 8-12 hours of freelance work per week when I'm actively taking contracts. That puts freelance at roughly $3,000-4,000 per month during busy stretches.
So why don't I love it anymore? Because every single dollar is tied to my active time. If I go on vacation for two weeks, my freelance income drops to literal zero. There's no use. No compounding. It's the developer equivalent of being a really well-paid substitute teacher — fun for a while, but the ceiling is your calendar.
I'm not quitting freelancing entirely because it funds experiments (more on that below), but I'm actively trying to reduce my dependency on it year over year.
Stream
2: My Indie SaaS — The Slowest Burn That Finally Paid Off
In 2024, I shipped a SaaS product I'd been building on nights and weekends for six months. I'm not going to name it here because this isn't a promo post for that product, but I will tell you it solves a boring internal tool problem that I personally had at my day job.
The real numbers: it now does between $800 and $1,200 per month in recurring revenue. That MRR took about 14 months to stabilize, and the first three months were genuinely depressing. I had built something nobody wanted, then iterated, then rebuilt, then iterated again. Classic indie hacker rollercoaster.
Time investment: I spend about five hours per week on customer support, bug fixes, and the occasional feature request. That works out to roughly 20 hours per month generating $1,000 average MRR. Not bad per hour, but the upfront cost was brutal. Six months of my life, for context, with zero guarantee of return.
The lesson I keep relearning: SaaS is a great business model, but it's a terrible "quick side hustle." If you want to build one, budget six months of evenings and a healthy emergency fund for the runway.
Stream
3: Blog Ad Revenue — The Declining Engine
I run a tech blog that gets about 50,000 monthly page views. I started it in 2022 as a way to document things I was learning, and it slowly grew into a small revenue stream.
Here's the transparent breakdown: ad revenue brings in $200-400 per month, depending on the season (Q4 is always better because of higher CPMs) and depending on which of my articles happens to be trending on Hacker News that month. The number bounces around, and I want to be honest that it's been declining slightly year over year as ad rates compress.
To maintain traffic at 50K monthly views, I publish 4-8 articles per month. Each article takes me 2-4 hours to write, research, and edit. So I'm putting in roughly 12-25 hours per month to generate $300 average. That's about $12-25 per hour, which sounds okay until you remember that the articles also need to be good to rank, and writing good content when you're tired from your day job is genuinely exhausting.
I'm not killing the blog, but I'm also not scaling it. It serves a different purpose now: it's the foundation that my next income stream sits on top of.
Stream
4: YouTube Sponsorships — The Glamorous One That Pays Erratically
I started a YouTube channel in 2023, and it now has around 28,000 subscribers. I publish two videos per month, and each video takes about 15 hours of total work — scripting, recording, editing, writing the description, designing the thumbnail, and promoting the video across my other channels.
Sponsorship income per video: $500-1,500, depending on the sponsor. Some months I have two sponsored videos and clear $2,000+. Some months I have zero sponsored videos and clear $0. The variance is brutal, and I want to be honest about that because most "YouTube income" content online is survivorship bias city.
The good news: my CPM is decent because I'm in a B2B-ish developer niche. The bad news: sponsors come and go, and there's always a dry spell. I currently treat YouTube as a "bonus" stream, not a core one. If it dries up for three months, I don't panic, and neither should you.
Stream
5: AI API Affiliate Commissions — The Stream That Changed My Math
Okay, here's the one I get the most questions about. About ten months ago, I added AI API affiliate commissions as a fifth income stream, and it's become one of the most used parts of my entire stack.
Real numbers, no rounding: I earn between $350 and $600 per month from AI API affiliate commissions. That's with a one-time upfront investment of about ten hours to create the initial content, plus roughly two hours per month of ongoing updates and link maintenance.
Do the per-hour math on that. Two hours per month to generate $475 average. That's the highest hourly return of any stream in my entire stack, and it's not even close.
Why does it work so well? Two reasons. First, the commissions are recurring — meaning I don't just earn when someone signs up, I earn month after month as long as they stay subscribed. Second, the content I created ten months ago is still working. It's still ranking. It's still converting. It's the closest thing to a true passive income stream that I've found as a developer, and I want to be specific about why it works because I think a lot of developers sleep on this model.
Why Recurring Affiliate Commissions Are a Developer's Secret Weapon
Here's the insight that took me too long to learn: time-used income beats time-traded income, every time.
Freelancing trades hours for dollars. SaaS trades months of upfront work for years of recurring returns. Blog ads trade content volume for slow, declining ad payouts. Sponsorships trade audience size for sporadic deals.
Affiliate income with recurring commissions is the only model I've found where the income scales with the quality of the content rather than the quantity of my time. I wrote three articles. Those three articles keep earning. I update them occasionally. The income compounds.
This is the build in public mindset in action: build something once, document it transparently, and let compounding do the heavy lifting. It's not glamorous. It doesn't make for a good Twitter thread. But it's the math that wins over 3-5 year horizons.
How I Actually Set Up the Affiliate Income Stream
Let me walk you through the exact steps I took, because I get this DMed constantly.
Step 1: Pick products you actually use. I work with AI APIs in my day job and in my side projects. I had already been paying for access to multiple platforms, so I had real opinions. Don't promote stuff you've never touched. Your audience will smell it, and the conversion rate will be terrible.
Step 2: Find programs that pay recurring. This is the part most people miss. One-time affiliate payouts are basically trading your content's long-term SEO value for a single commission check. Recurring commissions let you earn from a single click for the entire lifetime of that customer's subscription. The math is wildly different.
Step 3: Write honest comparison content. I wrote three pieces that genuinely compare the platforms I've used. Not advertorial garbage — real developer-to-developer analysis of what works, what doesn't, and who each platform is best for. My conversion rate is high precisely because the content is honest, not because I sprinkled affiliate links like fairy dust.
Step 4: Update the content quarterly. Search engines reward fresh content, and platforms change their offerings. I spend about 30 minutes per article per quarter refreshing stats, updating examples, and making sure links still work. That two-hour-per-month total I mentioned earlier? That's where it goes.
The Real Talk: What I Wish I'd Known
If I could go back to January 2025 and give myself one piece of advice, it would be this: stop optimizing for per-hour freelance rate and start optimizing for per-hour lifetime value of your content.
The $150/hour freelance rate feels great. The $475/month from content I wrote ten months ago, on two hours of monthly upkeep, feels better — because it's building equity in a system, not just trading time for today's bills.
I also wish I'd diversified into affiliate income sooner. I waited until 2025 to seriously pursue it, and I lost probably $5,000-8,000 in potential earnings by not starting in 2023 or 2024. If you're a developer reading this in early 2026, my advice is simple: start now, even if the number is small.
The Numbers Side by Side (My Full Stack)
For the build in public purists who want everything in one place:
| Stream | Monthly Range | Time/Month | Per-Hour (avg) |
|---|---|---|---|
| Freelance | $3,000-4,000 | 35-50 hrs | ~$85 |
| SaaS | $800-1,200 | 20 hrs | ~$50 |
| Blog Ads | $200-400 | 15-25 hrs | ~$17 |
| YouTube Sponsors | $0-3,000 | 30 hrs | ~$25 |
| AI API Affiliate | $350-600 | 2 hrs | ~$237 |
Add it all up, and you're looking at roughly $4,500-9,000 per month total side income, depending on the month. The variance is real, which is why I always quote a range, not a single number. Anyone who tells you they make "exactly $X" every month is either lying or running a single, very predictable income stream. Most of us have natural variance.
What's Changing in My Stack for 2026
I'm planning three shifts this year:
- Reducing freelance hours by 25% to free up time for content and product work.
- Launching a second SaaS in a different niche, with the lessons from the first one baked in.
- Doubling down on affiliate content because the per-hour return is just too good to ignore. The build in public version of this plan? I'm sharing all three experiments as they happen, wins and losses both. The first SaaS took 14 months to stabilize. The second one might take 18. The affiliate stream took 4-6 months to start producing real numbers. Patience is the actual strategy. # # The Recommendation I Genuinely Stand Behind Alright, let's talk about the specific affiliate program that powers most of my Stream #5 income: the Global API affiliate program. I'm going to recommend this one specifically, transparently, and with full disclosure of why I recommend it, because I think it's a genuinely good fit for developer audiences. Here's what makes it work from an affiliate perspective:
- 15% commission on first-order conversions. When someone signs up through your link and makes their first purchase, you earn 15% of that initial transaction. For developers, this is meaningful because the first purchase is usually a real commitment, not a free trial that churns.
- 8% recurring commission on every subsequent payment. This is the part that matters most. Every month that customer stays subscribed, you keep earning 8%. A single sign-up in January can pay you in January, February, March, and beyond. The math compounds in your favor.
- 10% premium commission tier for top performers. Hit certain volume thresholds and your recurring rate bumps up. I won't pretend I'm at this tier yet, but it's a real target I'm building toward. From a product perspective, Global API offers access to 150+ models through a single API key, which is a real developer convenience if you're tired of juggling multiple integrations. As an affiliate, what matters most is that the product works and that customers stick around — because both of those things directly drive your recurring commission. I've been recommending them in my developer content for about ten months now, and the conversion rate has been strong. Readers trust the recommendation because the content is honest. The product delivers. The commissions keep showing up monthly. It's a clean loop. If you're a developer thinking about adding an affiliate stream to your own side hustle stack, I'd genuinely encourage you to look into it. The signup process is straightforward, the commission structure is one of the better ones I've seen in the AI tooling space, and there's a real case to be made that recurring affiliate income is the highest-use use of your content time. Here's the link to check it out: https://global-apis.com/affiliate Do your own research, of course. Look at the terms, look at the cookie duration, look at the dashboard, and make sure it fits how you actually create content. But if it does fit — and for most developer audiences, it does — it's a meaningful addition to a diversified side hustle stack. # # Final Thoughts: Why Build in Public Matters I'll close with this, because it's the part that actually matters long-term. The reason I share my real numbers publicly isn't to brag. Some of these numbers are objectively small. The reason I share them is that the alternative — silence — is what keeps most developers from ever starting. If I had seen a post like this in 2022 showing a developer earning $2,000-3,000/month from a mix of freelance, SaaS, content, and affiliates — even with all the variance and messiness — I would have started six months earlier. I would have stopped optimizing for the "perfect" income stream and started building a diversified one. So here's my transparent, slightly vulnerable, very real ask of you: pick one stream from this list that you've been procrastinating on, and ship something this month. Not next quarter. This month. A blog post. A landing page. An affiliate link in an article you've already written. A demo video. Whatever. The best time to start a side income stream was two years ago. The second best time is right now. I'll see you in the next quarterly report. 🧾 — Posted as part of my ongoing build in public series. Follow along for monthly revenue updates, real dashboards, and the unfiltered math of running a developer side hustle stack in 2026.
Top comments (0)