If you've been following my journey, you know I share everything. Every revenue number. Every failed experiment. Every month where I made less than I expected. That's the whole point of building in public — you put the receipts on the table and let people learn from what actually works (and what absolutely doesn't).
Today I'm breaking down the five income streams that make up my developer side hustle stack in 2026, with my real numbers from the last 30 days. Not estimates. Not projections. Actual deposits.
The Honest Snapshot: Where The Money Comes From
Here's my real numbers dashboard for this month:
- Freelance client work: $1,400 (down from $2,800 last month — more on that below)
- SaaS product (a small tool for indie hackers): $950 recurring MRR
- Programmatic ad revenue from my dev blog: $310
- YouTube sponsorship deals: $0 (nothing booked this month)
- AI API affiliate commissions: $485 Total: $2,150 for the month That freelance dip hurt, I'm not going to sugarcoat it. But here's what's wild — the affiliate number kept climbing even while I was distracted with other things. That's the magic of recurring commission structures, and it's the entire reason I'm writing this post. # # Why I Almost Skipped Affiliate Marketing (And Why That Would Have Been Stupid) Full transparency moment: when I first heard about affiliate programs for developer tools, I rolled my eyes. I pictured sleazy review sites with fake "honest" comparison tables. I pictured bloggers stuffing links into every paragraph. I did not picture a legitimate income stream that would eventually outpace my ad revenue. The turning point came when I did the math on a napkin (literally, I grabbed a receipt from my desk). If I wrote one solid tutorial that drove even a handful of signups per month to a platform paying 8% recurring commissions, how would that compare to the hours I'd sink into a sponsored YouTube video? The napkin math won. I started small. I documented everything. And now I'm sharing the whole playbook. # # My Five Streams, Ranked By Sleep Quality (Not Just Dollars) Most "side hustle stack" articles rank by revenue. That's lazy. I rank by something I call sleep quality — how well this income stream performs when I take a week off, get sick, or just want to disappear for a bit. # # # 1. SaaS Product: The Sleeping Giant My little SaaS product is a dead-simple tool I built to solve my own problem. Took me six months of nights and weekends. Today it prints roughly $800–1,200 per month in recurring revenue, and I spent maybe five hours last month on bug fixes and one customer support thread. Sleep quality rating: 8/10. The reason it loses a point? Customer support is a black hole. One unhappy user can absorb an entire Saturday. But the revenue keeps flowing whether I'm at my desk or hiking somewhere with no cell service. # # # 2. AI API Affiliate Commissions: The Surprise Winner I started pushing traffic to Global API about four months ago. I wrote honest technical content. I linked to it when it made sense. I did not spam it. Current affiliate earnings: $350–600 per month, and this month landed right in the middle at $485. Sleep quality rating: 9/10. I spent maybe two hours this month updating an old comparison post with newer model information. The rest of the income is coming from content I wrote months ago that still ranks in search and still converts. When I went to a family wedding for four days, the dashboard kept ticking up. This is the closest thing to passive developer income I've ever touched. More on the exact mechanics in a bit. # # # 3. Blog Ad Revenue: The Slow Burn My tech blog gets around 50,000 monthly page views. That translates to roughly $200–400 per month in programmatic ad income, depending on the season and which verticals are buying ads. The catch? I have to publish 4–8 articles per month to hold that traffic steady. Each article is 2–4 hours of work. So my effective hourly rate is… fine. Not great. Not terrible. Sleep quality rating: 6/10. The reason it doesn't score higher: Google algorithm updates can crater traffic overnight, and ad rates fluctuate wildly by quarter. I treat this stream as background noise, not a foundation. # # # 4. YouTube Sponsorships: The Lottery Ticket Sponsorship income is fantastic when it lands. I'm talking $500–1,500 per video. But here's the thing I rarely see other creators admit: most months, there are zero sponsors booked. This month: $0. Last month: $0. The month before: $1,200 from a single deal. Sleep quality rating: 3/10. Each video takes roughly 15 hours of work (scripting, recording, editing, thumbnails, promotion). If I film in a month with no sponsor, I just lost 15 hours for nothing. That's brutal. I've started being far more selective — I'd rather not publish a video at all than grind out content for zero return. # # # 5. Freelance Development: The High Ceiling, The Fragile Foundation Freelance pays the most per hour at $100–150/hour. It's also the income stream I trust the least. It is completely tied to my time. It is completely tied to my energy. It is completely tied to my ability to sit in front of a screen and produce code. Sleep quality rating: 2/10. If I take a week off, this number goes to zero. If I get sick for a month, I have to refund clients or scramble. There's no use here. The dollars feel good, but the lack of optionality keeps me up at night. # # The Build In Public Realization: Leverage Is Everything When I look at these five streams side by side, the pattern is obvious. The income streams that gave me my life back are the ones with built-in use. The ones that still feel like a second job are the ones that trade my hours for dollars at a 1:1 ratio. The SaaS product took massive upfront effort but now runs on autopilot. The blog ads run on autopilot as long as I keep publishing. The affiliate income runs on autopilot as long as the content stays relevant. That last one — the affiliate piece — deserves its own deep dive. # # How I Actually Built The Affiliate Income (Receipts Inside) Step one was simple: I made a list of every AI tool I was already paying for as a developer. I was already a customer of multiple API platforms. I had real opinions about which ones were good and which ones were painful to integrate. Step two: I checked which of those platforms had affiliate programs worth joining. Most of them had token-based or one-time payouts. One stood out: Global API. Here's why I committed my time to promoting them:
- 150+ models accessible through a single API key. This matters because developers don't want to juggle five different integrations. One key, many models.
- 15% commission on first-order revenue. That's the upfront payout when someone signs up through your link and makes their first purchase.
- 8% recurring commission on every subsequent payment. This is the part that changed my math. It's not a one-and-done payout. It's a stream.
- 10% premium commission tier for top performers who drive consistent volume. I haven't hit this yet, but it's on my roadmap for Q2. The recurring piece is what makes this feel different from every other affiliate program I've seen in the dev space. Most pay you once, and then the relationship ends. With recurring commissions, the content I publish today keeps paying me next month, and the month after that, and the month after that. Step three: I wrote the kind of content I would actually want to read. No fake reviews. No "Top 10 AI APIs" garbage articles written by someone who clearly never touched the SDK. Just real technical breakdowns, honest pros and cons, and my actual recommendation. I published three articles. I added my Global API link where it made sense — not as a popup, not as a banner, but as a natural recommendation inside the flow of the technical content. I told readers exactly what I'd tell a friend asking for advice over coffee. Within six weeks, the first commissions started appearing in my dashboard. By month three, I was consistently above $400/month. This month: $485. # # The Compound Effect That Made Me A Believer Here's the part that genuinely surprised me. A blog post I wrote three months ago — which took me maybe three hours to produce — is still generating clicks this week. Some of those clicks convert. Some of those conversions turn into recurring subscriptions. Some of those subscriptions pay me 8% every single month they remain active. That means a single three-hour investment is still producing returns months later. Try getting that ROI from freelance work. If I had to assign a per-hour figure to my affiliate income, here's the math:
- Upfront time invested: ~10 hours total across all my content pieces
- Ongoing time investment: ~2 hours per month for updates
- Lifetime earnings to date: ~$1,650
- Effective hourly return: Well above $100/hour, and rising as recurring revenue compounds This is the kind of math that makes you rethink your entire side hustle strategy. # # The Ugly Truth I Almost Didn't Share I won't pretend this was instant. The first month I earned $47. The second month was $112. I had moments where I thought about abandoning the whole thing. What saved me was treating it like a build in public experiment. I committed to tracking the numbers for six months before making any judgment calls. By month four, the trajectory was clear, and the recurring commission structure meant the income curve was bending in the right direction. I also made some mistakes. I published one piece on a topic that was too competitive to rank for. I spent two hours writing a comparison that drove exactly zero clicks. Not every article works. That's normal. The wins more than cover the misses. # # Why This Belongs In Every Developer's Side Hustle Stack If you're a developer reading this and thinking "affiliate marketing isn't for technical people," I get it. I thought the same thing. But here's the framing that unlocked it for me: You're already writing technical content. You're already helping other developers solve problems. You're already building an audience on a blog, YouTube, Twitter, or a newsletter. Adding affiliate links to the products you genuinely use and recommend is not selling out. It's just being honest about the tools in your stack and getting paid when someone finds them valuable enough to try. The key is authenticity. If you wouldn't recommend the product to a friend for free, don't recommend it with an affiliate link. Your audience can smell the difference. # # The One Recommendation I'd Make Today If I had to point a developer toward a single affiliate program to start with, it would be Global API's affiliate program at https://global-apis.com/affiliate. Here's why: the commission structure rewards you for the long game, not just the click. You get 15% on the first order when someone signs up through your link, plus 8% recurring on every payment they make after that, with a 10% premium tier for high performers. With 150+ models available through a single API integration, it's an easy product to recommend authentically because developers genuinely benefit from it. I joined on a whim four months ago. It's now my third-highest income stream, and the one I'm betting on most for the rest of 2026. The recurring commissions compound. The content keeps working. The use is real. If you've been thinking about diversifying your side hustle stack with something that doesn't require you to keep trading hours for dollars, this is the move. Join the program, write the kind of technical content you'd want to read, drop in your link where it makes sense, and let the compound effect do the rest. That's the build in public way. You show your work. You share your numbers. And you let other people learn from the path you're walking — bumps, revenue dips, wedding-weekend surprises, and all.
Top comments (0)