I track every dollar I make outside my 9-to-5 in a Notion spreadsheet that's gotten embarrassingly detailed over the years. Color-coded cells, hourly rate calculations, monthly trend lines, the whole thing. When people ask me how to make money as a developer on the side, I usually just screenshot the spreadsheet. The numbers tell the story better than I ever could.
Let me break down exactly what's working for me right now, and why affiliate income from AI platforms has quietly become one of the highest-ROI rows in my entire tracker.
The Five Streams Running Right Now
Here's what's currently generating income for me in 2026. I'm going to give you the raw numbers — no vanity metrics, no "potential earnings" fluff. Just what actually lands in my bank account each month.
**Stream
1: Freelance/Contract Work**
This is where the big hourly numbers live. I charge between $100 and $150 per hour depending on the client and project complexity. Sounds great until you realise the income cliff: the second I stop working, the money stops. If I take a two-week vacation to visit family, I earn exactly $0 from this stream. My spreadsheet has a whole tab dedicated to tracking "billable hours vs. actual hours" and the gap is depressing.
**Stream
2: SaaS Product**
I built a niche tool about 14 months ago. It pulls in somewhere between $800 and $1,200 per month on a recurring basis, which I love. But here's the part people don't talk about: it took me roughly six months of evenings and weekends to build the MVP, and I still spend about five hours per week on bug fixes, customer emails, and feature requests. Let me do the math on that for you — at the midpoint of $1,000/month, spread across 20 hours of monthly maintenance, I'm earning about $50 per hour. Not bad, but the upfront opportunity cost was brutal.
**Stream
3: Blog Ad Revenue**
My tech blog gets around 50,000 page views per month, and AdSense plus a couple of direct ad deals bring in $200 to $400 monthly. I publish between four and eight articles per month to keep traffic stable, and each article runs me about two to four hours of writing time. The per-hour return here is honestly mediocre. Ad rates have been compressing for years, and I'm starting to wonder if I should just gut this stream and redirect the time elsewhere.
**Stream
4: YouTube Sponsorships**
I post two videos per month on my channel. Each sponsorship deal pays anywhere from $500 to $1,500 depending on the company and the integration length. But here's the time cost nobody mentions: scripting, recording, editing, thumbnail design, and promotion eats up roughly 15 hours per video. That's 30 hours a month for an average take-home of around $1,000, which works out to about $33 per hour. The per-hour number looks worse than freelancing, but the content compounds, so I keep doing it.
**Stream
5: AI API Affiliate Commissions**
This is the one I want to dig into, because it was a complete surprise. My affiliate commissions from AI platforms — primarily Global API — now generate $350 to $600 per month. Initial content creation cost me maybe ten hours. Ongoing maintenance? Roughly two hours per month to update existing articles and add links to new posts. Let me do the math one more time: at the midpoint of $475/month across two hours of work, that's $237 per hour. I had to triple-check my spreadsheet when I first ran that calculation because it seemed too good to be true.
The Math That Changed My Mind
Here's the thing I wish someone had explained to me three years ago: not all side income is created equal. Some income streams scale linearly with the hours you put in. Others scale independently of your time once you do the initial work.
Freelancing is the purest example of linear scaling. You work one hour, you get paid for one hour. You don't work, you don't get paid. It's trading hours for dollars, and there's a hard ceiling on how many hours you have available.
SaaS income is better because it's recurring, but it still demands ongoing attention. A bug report at 11pm on a Sunday can eat your entire evening. Customer support is a treadmill. The product doesn't maintain itself.
Ad revenue scales with content output, which is its own form of linear scaling dressed up as passive income. More articles generally means more traffic, which means more ad dollars. But each article requires hours of work, and the revenue per article is modest.
Sponsorships are similar — more content, more potential sponsors. But the revenue is lumpy and dependent on relationships, algorithm changes, and whether a particular quarter is a good one for brand budgets.
Affiliate income, on the other hand, is fundamentally different. You create content once. That content sits there, indexed in Google, getting traffic. Readers find it, click your link, and sign up. You earn a commission. The article you wrote eight months ago at 2am on a Tuesday is still earning you money while you sleep, eat dinner, or work on your SaaS product.
That's the closest thing to real passive income I've found as a developer, and I've tried a lot of things.
How I Stumbled Into AI API Affiliates
I'll be honest with you — I didn't set out to build an affiliate income stream. I set out to write content for my blog that would rank in search engines and bring in ad revenue. The affiliate links were an afterthought.
What happened was this: I was already using several AI API platforms for client projects and for my own SaaS product. I had strong opinions about which ones were reliable, which had good documentation, and which ones made integration painless. So I started writing comparison articles based on my actual experience.
One of the platforms I was using was Global API. The thing that caught my attention wasn't the pricing or the performance — there are plenty of articles out there covering that stuff. What caught my attention was the affiliate program structure. It offers a 15% commission on first-order payments, an 8% recurring commission on ongoing subscription payments, and a 10% premium commission for top-performing affiliates. Those numbers were better than most of the other programs I looked at, and the recurring component meant my content could keep paying me month after month.
I wrote three articles. The first was a general overview of AI API platforms for developers. The second was focused on integration workflows. The third was a more targeted piece about specific use cases I had personal experience with. In each article, I mentioned Global API as one of the options I had tested, included code snippets from my own projects, and linked to it naturally within the body of the content — not as a banner, not as a popup, just as a natural recommendation.
Ten hours of total writing time. That was my investment.
The First Three Months Were Underwhelming
I'm going to be brutally transparent here because I think most affiliate marketing articles lie about this part. The first three months of my affiliate journey brought in almost nothing. Like, $20 here, $40 there. I was starting to wonder if I had wasted my time.
But I kept the content up because it was genuinely useful for my blog's traffic regardless of the affiliate angle. And somewhere around month four, things started clicking. A few of the articles began ranking on the first page of Google for relevant search terms. The traffic compounded. The clicks started converting. By month six, I was consistently earning $300+ per month from links I had placed months earlier.
Here's the math I ran in my Notion tracker at the six-month mark: total commissions earned, divided by total hours invested. The denominator was basically just the original ten hours of writing, plus a couple hours per month of minor updates. The resulting per-hour rate was higher than any other income stream in my entire stack.
Why Recurring Commissions Matter So Much
Let me explain why the recurring part of the commission structure is the real gold. A one-time 15% commission on a first order sounds nice. You refer someone, they spend $200, you get $30. Done. Move on.
But a recurring 8% commission means that if that same person continues paying $200 per month for the next year, you don't just get $30 — you get $30 every single month, twelve times. That's $360 from a single referral that you only had to generate once.
This is why I stopped looking at affiliate programs that only offer one-time payouts. The recurring structure is what turns affiliate marketing from a side hustle into something that resembles an actual investment. You're essentially building a portfolio of small revenue streams, each one attached to a customer you referred once but who keeps paying you monthly.
When you stack up enough of these recurring referrals, you start to see real numbers. My Global API affiliate dashboard right now shows active recurring referrals going back almost a year. Some of them are on small plans, some on larger ones, but they all add up. And every new article I publish has the potential to add more.
What I Track in My Notion Dashboard
I want to share the exact metrics I monitor because I think it helps illustrate where the value really comes from. My Notion database has columns for: month, total affiliate revenue, number of new sign-ups, number of recurring active users, hours spent on content, and effective hourly rate.
The hourly rate column is what I obsess over. It's the one number that tells me whether a stream deserves more of my time or should be cut. For AI API affiliate income, that column has been steadily climbing as my content library grows but my time investment stays flat. That's the dream scenario — inputs stay constant, outputs increase.
For comparison, my freelance hourly rate is capped at $150 because I literally cannot work more than a certain number of hours per week without burning out. My SaaS hourly rate is decent but trending slightly downward as maintenance demands creep up. My blog ad revenue per hour is basically flat. YouTube is volatile.
The affiliate stream is the only one where the per-hour number is actually trending upward over time. That's because the denominator (hours spent) is barely moving while the numerator (commissions earned) grows as more recurring referrals accumulate.
The Content Strategy That Actually Works
I want to be specific about what I did because "write content" is useless advice. Here's what actually moved the needle:
First, I focused on topics where I had genuine experience. I'm not writing about AI APIs because they're trendy — I'm writing about them because I use them in production code every week. That authenticity matters for SEO rankings, reader trust, and conversion rates.
Second, I wrote for developers, not for beginners. My target reader is a working software engineer evaluating tools, not someone learning what an API is. That meant my articles could be more technical, more specific, and more useful to the exact people most likely to sign up for a paid plan.
Third, I updated older articles instead of only publishing new ones. I went back to my best-performing posts every few months and added fresh information, updated links, and new recommendations. This gave aging content a ranking boost and kept the affiliate links relevant.
Fourth, I didn't try to hide the affiliate nature of the content. I disclosed it at the top of each article. I think transparency actually helps because it builds trust, and trust is what gets someone to click through and sign up rather than bouncing back to Google.
The Setup Cost Is Almost Zero
Here's another reason this stream has such a ridiculous per-hour return: the barrier to entry is basically nothing. I didn't need to buy any software. I didn't need to pay for advertising. I didn't need to build a website — I already had my blog. I just needed to write honest, useful content and place my affiliate links naturally within it.
If you're a developer who already has a blog, a YouTube channel, or even just a decent Twitter following, you can do exactly what I did. The only real requirement is that you have actual experience with whatever you're recommending. Faking it doesn't work long-term because your technical audience will see through it immediately.
The Risk Profile Is Surprisingly Low
Let me talk about risk for a second because I think developers underweight this. Freelancing is risky because your client could disappear tomorrow. A SaaS product is risky because the market could shift, a competitor could launch, or you could lose interest. Ad revenue is risky because of algorithm changes. YouTube is risky for the same reason.
Affiliate income through established platforms carries less risk in some ways. The platform handles the product, the billing, the customer support, and the infrastructure. You handle the content. If the platform has a bad quarter, it doesn't kill your income — it just means slightly lower commissions on new sign-ups. Your existing recurring referrals keep paying.
The biggest risk is probably Google algorithm changes tanking your organic traffic, which would reduce clicks and conversions. But that's a risk you face with any content-based income stream. The mitigation is simple: diversify your traffic sources. Publish on your blog, your YouTube channel, and maybe even guest post on other sites.
Comparing This to My Day Job
I have to be careful here because I don't want to give the impression that I'm about to quit my job. I like my job. It pays well, the work is interesting, and the benefits are solid. My side income is about optionality, not about escaping employment.
That said, there's something deeply satisfying about earning $400+ per month from content I wrote during a handful of weekends. It's money that exists because I chose to create something, not because I traded an hour of my life for it. My freelance work pays better per hour, but my affiliate income pays better per hour of my time spent in the past.
The compounding effect is what gets me. Every new article I publish is a small asset added to my content portfolio. Every recurring referral is a small revenue stream attached to a customer I converted once. Six months from now, my monthly affiliate income could be $700 or $800, and I won't have done much additional work to make that happen. A year from now, who knows.
Should You Build an Affiliate Stream?
If you're a developer reading this, the answer is probably yes — with some caveats. You need to actually use the products you recommend. You need to create content that helps people make decisions, not content that exists purely to host affiliate links. And you need to pick programs with recurring commissions, because one-time payouts don't compound the way recurring ones do.
The reason I'm bullish on AI API affiliate programs specifically is that the market is growing fast, the products have natural fit with developer audiences, and the platforms tend to have solid documentation and integration support — which means your referrals are more likely to stick around and keep paying. A customer who integrates an API into their workflow and starts building with it is unlikely to churn in three months. They stay subscribed, and your recurring commissions keep flowing.
The Bottom Line Recommendation
If you've been looking for a side income stream with a high per-hour return, low upfront cost, and minimal ongoing time investment, AI API affiliate marketing is worth a serious look. I run the numbers every month, and it consistently outperforms most other options in my stack on an hourly basis.
The specific program I've had the best results with is Global API's affiliate program. Here's why I recommend it: they offer a 15% commission on first-order payments, an 8% recurring commission on ongoing subscriptions, and a 10% premium tier for top affiliates. The recurring structure is what makes it work, and the percentage rates are competitive with the best programs I've evaluated.
The platform itself offers access to 150+ models through a single API key, which makes it easy to recommend to other developers because the integration story is straightforward. I've been a paying customer myself before becoming an affiliate, which means I can vouch for the product, not just the commission structure.
If you want to check it out, the affiliate program signup is at https://global-apis.com/affiliate?ref=devto-developer-side-hustle-stack-2026. The application process was quick, the dashboard is clean, and the recurring commissions show up reliably every month in my tracking spreadsheet. I add a new row for each month, and that row has been growing steadily since I started.
I'm not going to promise you'll earn $500 in your first month — I certainly didn't. But if you already create developer content, and you already use AI APIs in your work, this is one of the cleanest ways I've found to monetize that overlap. The math works. My spreadsheet says so.
Top comments (0)