Skip to content

Blog Platform & Monetization Research — March 2026

Context

Research for Augusto Hermosilla — supply chain professional running a 68-service homelab across 4 hosts (VPS, Docker VM, NAS, Proxmox), located in Paraguay, bilingual Spanish/English, with a public repo and existing docs.cronova.dev (MkDocs Material). Goal: technical blog as portfolio + consulting funnel.

1. Blog Platform Landscape (2026)

Static Site Generators

Platform Pros Cons Best For
Hugo Fastest builds (10K pages < 3s), single binary, 60K+ GitHub stars, low maintenance, Go templating Steeper template learning curve, no JS interactivity without workarounds Large content sites, pure blogging
Astro Islands architecture, zero JS by default, mix React/Vue/Svelte, fastest-growing SSG (3M npm downloads), highest developer interest Younger ecosystem, Node.js dependency, more complex than needed for pure blog Interactive content, component-heavy sites
11ty Simple, flexible, great community Smaller ecosystem than Hugo/Astro Minimalist blogs
MkDocs Material (blog plugin) Already in use at docs.cronova.dev, built-in blog plugin (free since March 2026), archives, categories, tags, social cards Designed for docs first, blog second; less blog-specific SEO tooling Adding blog alongside existing docs

Hosted Platforms

Platform Pros Cons Best For
dev.to Built-in developer audience, free, good SEO, canonical URL support No monetization, no custom domain, platform owns distribution Cross-posting for reach
Hashnode Custom domain free, built-in audience, newsletter, canonical URLs, GitHub backup Limited customization, platform dependency Developer-focused blogging
Medium Large general audience, Partner Program payouts Paywall friction, no custom domain, poor for technical content formatting Cross-posting only
Substack Newsletter-first, paid subscriptions built-in, growing tech community 10% revenue cut on paid subs, limited design, not developer-focused Newsletter monetization

Self-Hosted

Platform Pros Cons Best For
Ghost (self-hosted) Membership/newsletter built-in, 0% revenue cut on self-hosted, clean editor, good SEO, native Stripe Requires Node.js hosting, ~512MB RAM minimum, maintenance overhead Serious newsletter + membership monetization
Ghost (managed) Same features, zero maintenance $15-29/month minimum, $199/month for business features Budget allows managed hosting
WordPress Largest ecosystem, endless plugins Security maintenance burden, bloated, PHP dependency Avoid unless specific plugin needed
WriteFreely Minimalist, federated (ActivityPub) Very limited features, tiny community Niche federated web audience

The homelab/self-hosted community in 2026 heavily favors:

  • Static sites hosted on their own infrastructure (dogfooding)
  • Hugo and Astro are the two dominant choices
  • Ghost is respected for its membership model
  • Self-hosting your blog is a credibility signal in this community

2. Market Saturation Reality Check

The Honest Picture

Yes, the generic homelab blog space is saturated. Common topics that are overdone:

  • "How I set up Pi-hole"
  • "My homelab tour" (without depth)
  • "Docker Compose for beginners"
  • "Setting up Nginx Proxy Manager"
  • Generic "self-hosting in 2026" listicles

AI has made saturation worse. Nearly 90% of newly indexed content is now AI-generated. Google has responded with AI Overviews that summarize informational content, reducing clicks by 58% for "how-to" and "what is" style queries. B2B tech content has been hit hardest (70% impact).

Where Opportunity Still Exists

Content that AI cannot easily generate and that few humans write:

  1. Incident reports with real data — cascading failure analysis, actual logs, real timelines (your WAN watchdog story)

  2. Operational discipline content — backup verification drills, DR testing results, what actually broke during restore

  3. Security hardening at scale — not "add a firewall", but cap_drop on 68 containers with specific gotchas per image type

  4. Architecture decisions with trade-offs — why you chose X over Y, with numbers and real constraints

  5. Non-English-speaking-world perspectives — Latin America homelab content is genuinely underrepresented

  6. Cross-domain expertise — supply chain + infrastructure is unusual and valuable

What Readers Actually Engage With

Based on Reddit (r/selfhosted, r/homelab) and Hacker News patterns:

  • Incident post-mortems get massive engagement (people love learning from failures)

  • "I actually tested my backups and here's what happened" — universally upvoted because almost nobody does this

  • Architecture deep-dives with real numbers (RAM usage, cost breakdowns, power consumption)

  • Opinionated takes with evidence — "Why I stopped using X" posts with data

  • Show HN posts with working demos or open repos
  • Generic tutorials get ignored unless they solve a genuinely undocumented problem

3. Monetization Options — Honest Assessment

Direct Blog Revenue

Channel Realistic Year 1 Year 2-3 Notes
Ad revenue (e.g., Carbon Ads) $0-50/month $50-200/month Tech CPMs are decent ($2-5) but you need 50K+ monthly views. Niche blogs rarely hit this in year 1.
Affiliate links $0-100/month $100-500/month VPN affiliates pay well (NordVPN 40-100% commission, Surfshark 40%) but feel sleazy for homelab audience. Hosting affiliates ($100-200/sale) convert better. Hardware Amazon links earn 1-4%.
Sponsored posts $0 $500-2000/post Need established traffic (10K+ monthly). Tech/SaaS sponsors pay $500-5000 per post depending on authority.
Paid newsletter $0 $50-500/month Requires 1000+ free subscribers before converting to paid. Buttondown (free up to 100 subs, $9/month for 1K, 0% revenue cut) or Ghost.
GitHub Sponsors $0-50/month $50-200/month Works if you open-source tools/configs that people use
Ko-fi / Buy Me a Coffee $0-20/month $20-100/month Supplementary at best

Year 1 total direct blog revenue: realistically $0-200/month. Year 2-3 total: $200-1500/month if you execute well and consistently.

These numbers assume 2-4 posts per month, consistent quality, and active community engagement.

The Real Money: Consulting Funnel

This is where the blog actually pays off. DevOps consulting rates in 2026:

  • Junior (1-3 years visible experience): $50-100/hour
  • Mid-level (portfolio + public work): $75-150/hour
  • Senior/specialized: $100-200+/hour

One consulting client per month at $75/hour for 20 hours = $1,500/month. That dwarfs any direct blog monetization.

The blog's primary economic value is as a credibility engine:

  • Public repo with 68 services demonstrates operational capability
  • Incident reports show you can handle production issues
  • Security hardening posts show you take it seriously
  • DR drill posts prove operational maturity
  • The blog IS the portfolio

From Paraguay, you are cost-competitive for US/EU clients while delivering senior-level work. LATAM DevOps outsourcing is a growing market — the blog positions you as a known entity rather than an anonymous freelancer on Upwork.

YouTube as Complementary Channel

YouTube homelab content is proven (TechnoTim, Jeff Geerling, NetworkChuck, Lawrence Systems). However:

  • High production overhead — filming, editing, thumbnails

  • Sponsorship-dependent — YouTube ad revenue alone is modest for niche content

  • Time investment is 5-10x a blog post for equivalent content

  • Recommendation: Start with blog, add short-form video (5-10 min) only after establishing written content cadence. Screen recordings of terminal sessions are low-effort and authentic.

Newsletter Economics

Platform Free Tier Paid Plan Revenue Cut Developer-Friendly
Buttondown 100 subs $9/month (1K subs) 0% Yes (Markdown-native, API-first)
Ghost (self-hosted) Unlimited Hosting cost only 0% Yes
Substack Unlimited Free 10% of paid subs Decent
Beehiiv 2,500 subs $39/month 0% on paid Good growth tools

Buttondown is the best fit for a developer audience: Markdown-native, proper syntax highlighting, API/webhooks, Stripe integration, and 0% revenue cut.

4. AI Impact on Blogging Economics

The New Reality

  • 90% of newly indexed content is AI-generated — mostly low-quality affiliate/SEO farm content

  • Google AI Overviews reduce CTR by 58% for informational queries

  • B2B tech content hit hardest at 70% traffic impact
  • Pages ranking #1 lost 34.5% CTR when AI Overviews appeared

What Still Works

  • Experience-based content that AI cannot fabricate (your actual incidents, your actual hardware, your actual configs)

  • Opinionated content with genuine reasoning (AI generates bland consensus)

  • Content with real data — screenshots, logs, metrics, cost breakdowns

  • Community engagement — responses to comments, Reddit participation, real identity behind the content

  • Long-tail technical queries — specific error messages, edge cases, obscure integrations (AI Overviews appear less frequently here)

Reader Sentiment

Readers increasingly value content that is visibly human-written:

  • Personal voice and opinions
  • "I tried this and it broke because..."
  • Real screenshots of real dashboards
  • Admitting mistakes and trade-offs
  • Unique perspective (Paraguay, supply chain background)

SEO Strategy Shift

Traditional SEO (ranking for "how to set up Docker") is declining in value. What works now:

  • Be citable — AI systems cite earned media (blogs account for 12% of AI citations). Original research and unique data get cited.

  • Build direct audience — newsletter subscribers, RSS readers, Reddit/HN followers don't depend on Google

  • Long-tail specificity — "Restic backup verification drill results for 68-container homelab" is not getting an AI Overview

5. What the Community Actually Reads

Reddit (r/selfhosted: 400K+, r/homelab: 1.5M+)

High engagement content:

  • Post-mortems and failure stories
  • "What I learned running X for Y months"
  • Architecture diagrams with real specs
  • Cost breakdowns (power, hardware, hosting)
  • Before/after optimization stories
  • Unusual setups (your Guarani naming + Paraguay angle)

Low engagement:

  • Generic tutorials (unless solving undocumented problem)
  • "Check out my new blog" self-promotion
  • Content that reads like a product review

Hacker News

What hits the front page:

  • Show HN with working demo or public repo
  • Detailed incident reports
  • Contrarian but well-reasoned takes
  • Novel approaches to common problems
  • Open source tools with clear use case

Your repo (68 services, public, well-documented) is exactly what HN values.

YouTube Homelab Creators (Reference)

  • Jeff Geerling: Hardware reviews, Raspberry Pi, open source advocacy. Full-time creator, Patreon + sponsors.

  • TechnoTim: Tutorials, server builds, home automation. Sponsor-dependent.

  • NetworkChuck: Beginner-friendly, high energy. Courses + sponsors.
  • Lawrence Systems: Deep-dive enterprise content. Consulting funnel.

Lawrence Systems is the closest model to your situation — blog/video content that feeds a consulting business.

6. Realistic Income Expectations

Year 1 (Months 1-12)

  • Blog direct revenue: $0-100/month
  • Newsletter subscribers: 100-500 (mostly free)
  • Monthly traffic: 1,000-5,000 visits
  • Consulting leads from blog: 0-2 total
  • Time investment: 8-15 hours/month (2-3 posts)
  • Total blog-attributed income: $0-500 for the year

Year 2 (Months 13-24)

  • Blog direct revenue: $100-500/month (affiliates + occasional sponsor)
  • Newsletter subscribers: 500-2,000
  • Monthly traffic: 5,000-15,000 visits
  • Consulting leads from blog: 1-3 per quarter
  • Time investment: 10-20 hours/month
  • Total blog-attributed income: $2,000-10,000 for the year (mostly consulting leads)

Year 3 (Months 25-36)

  • Blog direct revenue: $300-1,500/month
  • Newsletter subscribers: 2,000-5,000
  • Monthly traffic: 15,000-40,000 visits
  • Consulting leads from blog: 1-2 per month
  • Time investment: 15-25 hours/month
  • Total blog-attributed income: $10,000-30,000 for the year (consulting dominant)

Honest Assessment

Blogging alone will not generate meaningful income in year 1. Period. Anyone telling you otherwise is selling a course.

The value proposition is:

  1. Portfolio that works while you sleep — clients find your content, see your competence, reach out
  2. Compounding credibility — each post adds to your authority
  3. Consulting funnel — this is where the real money is
  4. Skill development — writing forces you to understand deeply
  5. Network building — community engagement leads to opportunities

From Paraguay, one US/EU consulting client paying $75-100/hour is worth more than 2 years of blog ad revenue.

7. Your Unique Angles (Ranked by Potential Impact)

Tier 1 — Genuinely Unique, High Value

  1. Backup Verification Drills — You have 8 backup-verify test suites and 9 DR scenarios documented. Almost nobody in the homelab community actually tests their backups and publishes results. This is gold for both content and credibility. "I restored every service in my homelab from backup — here's what broke" would hit HN front page.

  2. Container Security Hardening at Scale — cap_drop ALL + specific cap_add across 68 containers, with per-image-type gotchas (LinuxServer.io, PostgreSQL, BusyBox). This is enterprise-grade operational knowledge applied to homelab.

  3. Cascading Failure Analysis — The WAN watchdog incident with Tailscale logout cascade, DNS dependency chains, and the /etc/hosts fix. Real incident reports with real timelines are the most engaging content format.

Tier 2 — Differentiated, Good Engagement

  1. Solo Operator Running Production-Grade Infra — 68 services, monitoring pipeline (vmagent -> VictoriaMetrics -> Grafana -> ntfy), alerting with 11 rules, automated backups with offsite sync. This is a "how one person runs what looks like a team's infrastructure" story.

  2. Supply Chain + DevOps Crossover — Unusual combination. Write about how supply chain thinking (redundancy, single points of failure, lead times, risk management) maps to infrastructure design. This is genuinely original.

  3. Paraguay / Latin America Perspective — Underrepresented in English homelab content. Hardware sourcing challenges, ISP limitations, power reliability, cost constraints. Bilingual content opens Spanish-speaking audience (500M+ speakers, growing tech community).

Tier 3 — Interesting, Niche Appeal

  1. Guarani Naming Convention — Cultural angle that makes your setup memorable and distinct. Good for a single viral post, less for ongoing content.

  2. OPNsense + Proxmox + Docker Architecture — Well-documented but not unique. Valuable as supporting content for the above topics.

Platform Choice: Hugo + Cross-Post

Primary: Hugo static site at blog.cronova.dev (or a subdirectory of docs.cronova.dev)

Rationale:

  • You already self-host and know Docker — Hugo builds in a container trivially
  • Static site on your existing Caddy infrastructure = zero additional cost
  • Full ownership of content, design, and URLs
  • Best SEO control (sitemaps, structured data, canonical URLs)
  • Git-based workflow matches your existing habits
  • Hugo's speed and stability = low maintenance
  • The homelab community respects self-hosted blogs

Alternative considered: Adding the MkDocs Material blog plugin to your existing docs.cronova.dev. This is simpler but constrains your blog design to docs-style layout. Worth considering if you want to minimize setup time, but Hugo gives you more flexibility for a blog-focused site.

Cross-posting (wait 1-2 weeks after original publication):

  1. dev.to — set canonical URL to your Hugo site
  2. Hashnode — set canonical URL to your Hugo site
  3. Reddit (r/selfhosted, r/homelab) — link posts with genuine discussion
  4. Hacker News — for the best pieces only (backup drill results, incident reports)

Newsletter: Buttondown (free tier to start, Markdown-native, 0% revenue cut). Embed signup in Hugo site. Graduate to Ghost self-hosted only if paid newsletter becomes viable (1000+ subscribers).

Content Calendar — First 6 Months

Month 1 — Launch

  1. "I Tested Every Backup in My 68-Service Homelab — Here's What Broke" (backup verification drill results)

  2. "Anatomy of a Homelab: 68 Services, 4 Hosts, 1 Operator" (architecture overview with diagrams)

Month 2

  1. "The WAN Outage That Took Down Everything: A Cascading Failure Post-Mortem" (incident report with timeline)

  2. "cap_drop ALL: Security Hardening 68 Containers (and the Gotchas Nobody Warns You About)" (practical security)

Month 3

  1. "What Supply Chain Management Taught Me About Infrastructure Design" (crossover piece, HN-friendly)

  2. "Running a Homelab from Paraguay: Hardware Sourcing, ISP Realities, and Cost Constraints" (unique perspective)

Month 4

  1. "My Monitoring Pipeline: From vmagent to ntfy in Under 30 Seconds" (practical monitoring at scale)

  2. "Naming My Servers in Guarani: A Convention That Actually Works" (cultural + practical)

Month 5

  1. "Restic + rclone: Offsite Backups That Actually Get Tested" (backup deep dive)

  2. "The Real Cost of Self-Hosting: Power, Hardware, Time, and Opportunity" (honest cost analysis)

Month 6

  1. "OPNsense as Gateway: VLANs, Firewall Rules, and CrowdSec for a Homelab" (networking deep dive)

  2. Six-month retrospective with traffic numbers and lessons learned

Publishing Cadence

  • 2 posts per month — sustainable with a full-time job
  • Quality over quantity — one deeply researched post beats four thin ones

  • Cross-post 1 week after publication — gives Google time to index the original

  • Newsletter: monthly digest — summarize posts + add personal commentary

Leveraging Existing Assets

  • docs.cronova.dev — Keep as technical reference/docs. Link from blog posts for deep dives.

  • GitHub repo — Reference in every post. The public repo IS the proof. "Don't trust my blog post — here's the actual docker-compose.yml"

  • Forgejo — Could host a mirror, but GitHub is where the audience is

Timeline Expectations

Milestone Realistic Timeline
First 10 posts published Month 5
First Hacker News front page Month 3-8 (backup drill or incident post)
100 newsletter subscribers Month 4-6
First consulting inquiry from blog Month 6-12
1,000 monthly visitors Month 3-6
5,000 monthly visitors Month 8-14
First sponsored post offer Month 12-18
1,000 newsletter subscribers Month 12-18
Sustainable consulting pipeline (1-2 leads/month) Month 18-24

9. Bottom Line

Do not start a blog to make money from the blog. Start a blog to:

  1. Build a public portfolio of operational expertise
  2. Create a consulting/freelancing funnel
  3. Connect with the homelab/DevOps community
  4. Force yourself to document and systematize your knowledge
  5. Establish credibility as a known name in the space

The direct blog revenue (ads, affiliates, sponsors) is a bonus that may materialize in year 2-3. The consulting leads from demonstrated expertise are where the economics actually work, especially from Paraguay where your cost of living means even modest US/EU consulting rates are transformative.

Your setup is genuinely impressive. 68 services with monitoring, alerting, automated backups, security hardening, DR drills, and a public repo — this is better operational practice than most companies. The blog just makes it visible.

Start with Hugo. Write the backup drill post first. Cross-post everywhere. Let the repo speak for itself.