This isn’t a conclusion. It’s a hypothesis. I’m betting that self-hosting my own subscription platform is worth the tradeoff over Patreon — but I could be wrong.

What Patreon Gives You for Free

Patreon is a known brand. When someone sees “Support me on Patreon,” there’s instant recognition. They know what it is, they trust it with their credit card, and they probably already have an account. That’s a massive advantage that’s easy to underestimate.

Beyond trust, Patreon provides:

  • Discoverability — Patreon surfaces creators to potential supporters. People browse the platform looking for things to back. Your page exists inside a marketplace.
  • Payment infrastructure — Stripe integration, failed payment recovery, currency handling, invoicing — all handled. You never touch a webhook.
  • Mobile app — Supporters get push notifications, manage their subscriptions, browse exclusive content from their phone.
  • Community tools — Posts, polls, DMs, tiers with gated content, Discord role integration. All built in.
  • Legal and tax compliance — VAT collection, sales tax handling, 1099 generation for US creators. This is genuinely complicated to do yourself.

That’s a lot of value for a solo indie dev. Every one of those is a feature you’d need to build or go without.

What Patreon Costs

Patreon’s Pro plan takes 8% of every dollar your supporters pay. The Founders plan from the early days was 5%, but new creators pay 8-12% depending on the plan. On top of that, there’s payment processing (Stripe’s 2.9% + 30¢) which Patreon passes through.

So on a $7/month subscription, Patreon keeps roughly $0.56 in platform fees plus ~$0.50 in payment processing. That’s $1.06 out of every $7 — about 15%.

But the cost isn’t just money:

  • You don’t own the relationship. Patreon owns your subscriber list. If you leave, you can’t take your supporters with you easily. You’re building on rented land.
  • Platform risk. Patreon changes their terms, algorithms, and fee structures. They’ve done it before. Creators have been demonetized or had their accounts flagged. Your income depends on a company’s policy decisions.
  • Limited customization. Your page looks like every other Patreon page. You’re a row in someone else’s database, not a destination.

What Self-Hosting Gives You

My setup costs roughly under $5/month for hosting (S3 + CloudFront + Route 53 + Lambda + Secrets Manager) plus Stripe’s 2.9% + 30¢ per transaction. No platform fee on top.

On that same $7/month subscription, I’d pay about $0.50 in Stripe fees. That’s it. The difference is $0.56/subscriber/month — small at first, but it scales linearly.

More importantly:

  • Full ownership. I own the subscriber data, the email list, the payment relationships. If I ever move platforms, I take everything with me.
  • Creative control. The site matches my brand exactly — the bilateral layout, the custom font, the engine/heart aesthetic. It’s not a Patreon template.
  • No platform dependency. Nobody can change the rules on me. The site is static files on a CDN I control.

What Self-Hosting Actually Costs

Marketing Risk

Nobody is going to stumble onto allbyte.studio. There’s no Patreon browse page, no recommendation algorithm, no “creators you might like” sidebar. Every single subscriber has to be driven there through my own marketing — social media, Discord, word of mouth, gameplay clips. Patreon has a built-in audience. I have a domain name.

A beautifully engineered site with zero traffic is worse than an ugly Patreon with 50 subscribers.

Trust Risk

“Support me on Patreon” is a sentence people understand. “Go to allbyte.studio and click Subscribe” is a harder sell. A custom domain with a custom payment flow looks sketchy to anyone who’s been on the internet long enough. I use Stripe Checkout (which people do recognize), but the path to get there is unfamiliar.

Technical Risk

Every bug is my bug. OAuth breaks at 2am? That’s on me. Stripe webhook misses an event? I’m digging through Lambda logs instead of making the game. CloudFront serves a stale page? Me again.

Patreon has an engineering team. I have Claude and a prayer.

Opportunity Cost

Every hour spent on infrastructure — building OAuth, debugging CloudFormation, writing this very analysis — is an hour not spent on the game. The whole point of AllByte Studios is to make a tactical RPG. Not a web platform.

The infrastructure work is interesting and feels productive, but if the game isn’t good, the website is irrelevant.

Unknown Unknowns

What happens when we need:

  • Refund handling?
  • Subscription pausing?
  • Gift subscriptions?
  • Annual billing?
  • Tax compliance across jurisdictions?
  • Failed payment retry logic?

Patreon has solved all of these. I’d need to build each one or accept that I don’t have it.

The Hypothesis

I’m betting that the combination of:

  1. Low hosting costs (<$5/mo vs 8-12% of revenue)
  2. Full data ownership (subscriber list, payment history)
  3. AI-assisted development (Claude turns weeks of infrastructure work into hours)

…will outweigh the marketing, trust, and maintenance overhead.

The third point is the key one. Five years ago, a solo developer self-hosting a subscription platform would be absurd. But with an AI pair-programmer that can write CloudFormation templates, debug OAuth flows, and set up CI/CD pipelines in a single conversation, the calculus changes. The infrastructure that used to be the hard part is now the fast part. The marketing and trust-building — which Patreon solves — is now the hard part.

This is unproven. I could end up with a beautifully engineered ghost town and wish I’d just set up a Patreon page in 10 minutes. Worst case, I learn a lot and migrate to Patreon later. Best case, I keep 100% of my revenue minus Stripe’s cut and own everything.

I’ll report back.