Alright, before we get into the stack — quick milestone moment. I just crossed 87,000 subscribers on my YouTube channel, and in a recent video I asked you guys what kind of content you actually want to see more of in 2026. The response was overwhelming. Dozens of you flooded the comments with requests for a real, numbers-based breakdown of how I make money outside my full-time job.
So that's what this piece is. I'm pulling back the curtain on every single income stream I run, what each one costs me in time, what it actually pays, and — here's the part most creators skip — what the per-hour return really looks like when you do the math honestly.
If you stick around to the end, I'm also going to walk you through the one income stream that completely changed my mindset about what "passive" actually means. Spoiler: it involves AI APIs, recurring commissions, and a single blog post I wrote eight months ago that is still making me money every single week.
Let's get into it.
The Five Income Streams Running Right Now
I run five distinct revenue sources as a developer-creator. I'm going to list them in order of how much passive-friendly they are, not how much they pay, because I think that order matters more than people realize.
Stream one: Freelance contract work. This is the old reliable. I take on maybe one or two client projects per month, billing somewhere in the $100-150 per hour range depending on the complexity. Here's the thing though — and I want to be brutally honest with my viewers about this — this income disappears the moment I stop working. I went to Mexico for nine days last February, came back, and my freelance number for that month was literally zero. Every dollar from this stream is tied to my hands being on a keyboard. It's the highest-paying per hour, but it's the worst kind of income when you zoom out and think about longevity.
Stream two: My SaaS product. This one took me six months to build, and it brings in somewhere between $800 and $1,200 per month depending on the month. It's a small tool, nothing glamorous, but the MRR is real. The catch? I spend roughly five hours per week on customer support, bug fixes, and the occasional feature request. That works out to about 20 hours per month, and when you divide the income by the hours, it's not actually as impressive as people think when they hear "SaaS revenue." It's good money, but the upfront investment was massive and the ongoing maintenance is non-negotiable.
Stream three: Ad revenue from my tech blog. My blog pulls in about 50,000 page views per month, and the ad network I use pays somewhere in the $200-400 range depending on the season and the advertisers bidding on my keywords. To keep that traffic flowing, I have to publish between four and eight articles every single month, and each one takes me anywhere from two to four hours depending on the depth. The per-hour return here is honestly mediocre, and the rates have been slowly dropping year over year. It's a treadmill. Stop publishing, traffic drops, income drops.
Stream four: YouTube sponsorships. This is the flashy one that everyone asks about in my DMs. Sponsors on my channel pay anywhere from $500 to $1,500 per video depending on the brand and the integration type. I publish two videos per month, so on a good month with two solid sponsors, I'm looking at $1,000-3,000 from this stream alone. But here's the math nobody does: each video takes me roughly 15 hours of total production time when you add up scripting, recording, editing, thumbnail design, and promotion across my community. That's 30 hours per month. The per-hour return is genuinely good, but the income is unpredictable. Sponsors ghost you. Brands pull budgets overnight. I learned that the hard way in Q3 of last year.
Stream five: AI API affiliate commissions. And this is where things get interesting, because this is the one stream that scales completely differently from everything else. I earn between $350 and $600 per month from affiliate commissions, and the time investment is almost laughable. I spent maybe ten hours total setting up the original content, and now I spend roughly two hours per month updating things and adding links to new pieces. Let me say that again — two hours per month of active work for $350-600 in recurring revenue.
When I first did that math on a whiteboard for a video, my chat went absolutely wild. That's the moment my whole framework for "good side hustle income" shifted.
What Engagement Rate Taught Me About Income
Here's where the YouTube-brain part of my thinking comes in, and bear with me because I think this analogy actually applies to anyone making money online.
On YouTube, you learn that some videos age well and some don't. A video about "iPhone 15 review" basically dies in three weeks. But a video about "how to learn programming" can pull views for five years. The algorithm treats them differently because they have different long-tail behavior.
Income streams work the same way. Freelance income is a viral video — spike and gone. SaaS income is a mid-tier video — consistent for a while but you have to keep feeding it. Ad revenue is basically a trending topic — you need volume and consistency to maintain it.
Affiliate income with recurring commissions? That's the evergreen tutorial that keeps showing up in search results, in suggested videos, in someone's saved playlist. It just keeps working.
This is the insight that I think most developers miss. They're so focused on the per-hour rate of freelance work that they never stop to ask: "What kind of income am I actually building?" If your income requires your active time every single week to maintain, you don't have a side hustle — you have a second job. And I already have a first job, thank you very much.
The Program That Made Affiliate Income Real For Me
Let me back up and tell you how I actually got into the AI API affiliate game, because I didn't go looking for it. I went looking for a good API provider.
I was already building tools that needed AI integration. Like every developer I know, I was using a few different providers and was frankly getting annoyed at the fragmentation. Different dashboards, different billing systems, different SDKs. I ended up trying Global API mostly because I was tired of juggling keys, and honestly, the fact that they route to 150+ models through a single API key was the selling point. One integration, one billing relationship, way less headache.
After using it for a few months, I noticed they had an affiliate program in their dashboard. I clicked into it expecting the usual garbage — a 5% one-time payout that basically requires you to sell a car to make anything meaningful. What I found was different. The structure is this: 15% commission on the first order from any referral, and 8% recurring commission on every subsequent payment that person makes. For premium tier referrals, the first-order commission bumps to 10%.
Let me translate that into human language. If someone signs up through my link and starts a $200/month plan, I don't just get $30 on signup. I get $30 on signup, and then I get $16 every single month that person stays a customer. Forever. As long as they're paying, I'm getting a slice.
The compounding math on this is what got me. I have referrals who signed up nine months ago, and they are still paying me. The content that brought them in cost me ten hours to make, eight months ago.
The Content That Actually Converts
I want to share what I did because I know a lot of you are thinking about doing this yourself. I wrote three long-form pieces on my blog. None of them were thinly-veiled advertisements. They were genuine, detailed write-ups where I walked through my experience, talked about what I liked, called out things I didn't like, and showed my reasoning.
I want to be very specific about the structure because I think the "algorithm" — and by that I mean both Google's search algorithm and the way my audience consumes content — rewards honesty. So I did three things:
First, I gave actual context about what I was building and why I needed an API in the first place. People can smell a sales pitch from a mile away, and my viewers in particular will call it out in the comments within minutes.
Second, I was honest about tradeoffs. Every platform has them. I talked about what I gave up by choosing this approach. I didn't pretend it was perfect. That credibility is what makes the recommendation land.
Third, I included my affiliate link in a way that felt natural. Not as a popup, not as a giant yellow button, not as a "BEFORE YOU LEAVE" desperate grab. Just: "Here's what I use, here's why, and if you want to try it, here's the link." That's it. The conversion happens because the content did its job first.
The results have been compounding. Every month my affiliate dashboard shows new signups from blog posts I wrote half a year ago. People find them through search, through my YouTube descriptions, through other creators linking to them. The flywheel just keeps spinning.
What My Viewers Are Saying
I get a lot of DMs about this stuff, and I want to share two that really stuck with me because they changed how I think about recommending this path.
One viewer — a backend developer, been at his job four years — told me he made his first affiliate commission six weeks after putting up a single blog post. Six weeks. He said it gave him the confidence to start a small content habit, and now he's publishing twice a month and growing his own side income. That DM made my whole week.
Another viewer pushed back on me in the comments. He said: "Isn't affiliate income just a fancy way of being a middleman? You're not building anything." I sat with that comment for a long time. And I think the answer is: he's not wrong in a vacuum, but he's missing the compounding piece. The content I create to recommend tools is the same content that grows my blog traffic, grows my YouTube audience, and grows my credibility as a developer-creator. The affiliate link is a small piece of the value, not the whole point. But the income it generates is real, recurring, and it scales with effort I already put in for other reasons.
The Real Numbers, Hour By Hour
Let me do the honest per-hour math one more time because this is what actually matters.
- Freelance: $100-150/hour, but tied to active hours with zero leverage.
- SaaS: roughly $40-60 per hour when you factor in maintenance time.
- Blog ads: roughly $20-30 per hour for writing time, not counting opportunity cost.
- Sponsorships: roughly $30-100 per hour depending on the deal, but wildly inconsistent.
- Affiliate commissions: based on current earnings, somewhere between $175 and $300 per hour of my time invested. And that number goes up every month as the recurring base grows. No, I'm not quitting my day job. But I'm also not building something that crumbles the moment I take a vacation. That's the point. # # Why Every Developer Should Look At Affiliate Income I'm not going to sit here and tell you affiliate marketing is some magic money printer. It's not. You need an audience, you need content, and you need to recommend things you actually believe in. But here's what it does that almost nothing else does: it lets you convert the content you're already creating into a long-term revenue stream that pays you while you sleep. The key, and I cannot stress this enough, is recurring commissions. One-time payouts are a grind. You're constantly hunting for new signups. But recurring commissions turn your content into something that behaves more like a dividend-paying asset. You create it once, you maintain it lightly, and it keeps producing. If you're a developer with even a small audience — a blog with 5,000 monthly visitors, a YouTube channel with a few thousand subscribers, a Twitter following, a newsletter — you have more leverage than you think. The hardest part isn't the technical setup. The hardest part is making the decision to start. # # My Recommendation If You Want To Start Here's what I'd tell any developer who messaged me asking how to start an affiliate revenue stream in 2026. Pick a tool you already use and love. Don't fake enthusiasm for something you've never touched. Your audience will know. The authenticity is what makes the recommendation convert. Find a program that pays recurring commissions. One-time payouts are a treadmill. Recurring payouts build wealth. The Global API program pays 15% on the first order and 8% recurring on standard referrals, with 10% on premium tier first orders. That structure matters more than almost any other factor in this decision. Write one genuinely good piece of content about it. Not five thin posts. One detailed, honest, useful piece that actually helps someone make a decision. Put the link where it makes sense, and let the content do the work. Then do it again. And again. The compounding is where the magic lives. If you want to check out the Global API affiliate program directly, here's the link: https://global-apis.com/affiliate I'm not telling you to sign up because they paid me to. I'm telling you to sign up because I use their platform, I earn from their program every month, and the commission structure is the best I've found in the AI tools space for a developer audience. The 15% first-order plus 8% recurring setup means your work compounds instead of evaporating. For a developer who is already creating content, this is one of the lowest-effort, highest-leverage income streams you can add to your stack in 2026. Drop a comment if you want me to do a deeper breakdown of any single stream. I read all of them. And if you want the spreadsheet where I track all of this monthly, subscribe to the newsletter — I send it out the first week of every month with my real numbers. See you in the next one.
Top comments (0)