NuxtBeyond
Build AI-powered SaaS products in days, not months
I've shipped products on Stripe for years and never questioned it. It's the default, it works.
Then I added Polar to my Nuxt boilerplate as a second option and had to actually understand the difference. Here's what I wish I'd figured out earlier.
With Stripe, you are the merchant. You're responsible for collecting and remitting sales tax and VAT everywhere you have customers. As a solo founder selling to the EU, that's VAT obligations from your first sale. Stripe Tax calculates it, but you still register and file yourself.
With Polar (a merchant of record), Polar is legally the seller. They handle all the tax. One payout, no compliance project.
The cost: Stripe is 2.9% + 30c. Polar just changed their pricing, the new default is 5% + 50c (with cheaper paid tiers if you do volume).
So for a while I was comparing the wrong thing. I kept looking at per-transaction fees when the actual decision was how much tax paperwork I wanted to own.
For a US-only project at low volume, Stripe is clearly cheaper. For selling digital products globally, the merchant of record premium is often cheaper than what you'd pay an accountant (or in stress) to stay compliant.
I ended up not picking. I made it switchable with one env var so you can start on Stripe and move to Polar when you actually go international. The right call genuinely depends on where your customers are.
(For context, I build NuxtBeyond, an AI-first Nuxt 4 boilerplate. This was just the latest thing I bolted on. I also wrote up the full Stripe vs Polar breakdown if anyone wants the deeper version.)
Anyone here actually moved from Stripe to a merchant of record? Curious whether the fee bump was worth it for you.
I published a blog post comparing NuxtBeyond to every other Nuxt SaaS boilerplate. Was supposed to be a marketing play.
Turned into a reality check.
My $59 boilerplate has features the $349 ones don't (RAG, embeddable widgets, video generation). But writing the comparison forced me to admit things I'd been ignoring: my auth is basic, I only support Stripe, and my "community" is one sale.
Supastarter has 1,265+ developers. ShipFast has 8,100. I have 1.
Still published it because I think an honest comparison is more useful than a sales page pretending weaknesses don't exist.
I've been building AI SaaS products with Nuxt for about 6 months now. Started with Docuyond (an AI agent for customer support), and I kept needing the same things: auth, UI components, Stripe, database, rate limiting. When I started my second project I was literally copy-pasting files between repos. That's when I figured I should just extract it properly.
I looked at what Nuxt boilerplates existed and most of them were a login page, a Stripe checkout, maybe a dashboard layout, and that's it. You pay $200+ and still build 80% of the product yourself. I wanted something with actual AI infrastructure built in, not a TODO comment where the AI should go.
So here's what's in it:
RAG-powered chat with Cloudflare AutoRAG and Vercel AI SDK v6 (streaming, tool calling, whole setup)
Embeddable chat widget you can drop into any site
Image and video generation with DALL-E 3 and Sora
nuxt-auth-utils for auth (Google OAuth + email/password but can be easily expanded)
Multi-tenant projects with team members and resource scoping
Stripe subscriptions with webhooks and customer portal
Full Cloudflare edge stack: D1, R2, KV, Workers via NuxtHub (but can be used with Vercel or other cloud providers as well)
Nuxt UI v4, Drizzle ORM, Tailwind v4
Blog with Nuxt Content, emails with Resend
The RAG setup and embeddable widget are what I spent the most time on. Getting AutoRAG to work with streaming responses and making the widget secure with CORS and domain whitelisting was painful but it works well now. I use it in my own product.
One honest pain point: the NuxtHub setup. Since Nuxt got acquired by Vercel, it kept getting updates and breaking. I had to chase changes constantly. But it's stable now and deploying is simple once you configure everything in Cloudflare (or other cloud providers)
I also added a CLAUDE.md file so Claude Code, Codex etc actually understand the project when you use them. If you're building with AI coding tools this saves a lot of back and forth. (let's be honest, we all do now)
Currently $59 one-time, lifetime updates. Price increases each 5 sales. I got my first sale from a Reddit post on r/Nuxt this week. I use this for my own products so it won't go stale.
nuxtbeyond.com if you want to check it out.
If you're building with Nuxt + Cloudflare, happy to share what I learned about the edge stack. What's your current setup?
-
2
Congrats on the launch, looks solid. How are you currently thinking about acquiring early users and gathering feedback?
-
1
Currently posting on X and Reddit and see how it goes. Will probably expand in the future
-
-
1
Really cool concept! 👏 NuxtBeyond looks like a powerful way to help developers and teams unlock more from Nuxt.js especially with performance boosts and built-in enhancements that often require manual setup.
I like how focused the positioning feels around “beyond the basics” it communicates that this tool fills the gap between starter projects and production-ready stack enhancements. The clean layout and concise wording make the core value easy to grasp quickly, which matters a lot for developer audiences.
One thing I’m curious about is how you’re guiding first-time visitors toward understanding the exact benefits especially if they’re new to Nuxt or unsure what “beyond” means in concrete terms. Clarifying that in the first scroll could help reduce early drop-offs.
Overall this is a very promising project keen to hear more about your growth plans and what feedback you’ve been getting so far!
The landing page communicates concept, but you could make the outcome even more explicit. For example:Instead of:
“Power up your Nuxt projects”
Try something like:
“Turn Nuxt projects into performant production apps in minutes”
That shifts from feature language to user outcome which often boosts engagement.
-
1
Great job! This is a solid stack. Building real AI infra instead of a fake boilerplate is the right move. The RAG + embeddable widget combo is especially interesting.
Quick security question. With multi-tenant projects, team members, and resource scoping on top of D1, R2, and KV at the edge, how are you enforcing tenant isolation at the data layer? Edge KV and object storage can get tricky if keys or object paths are predictable.
Also, for the embeddable chat widget, beyond CORS and domain whitelisting, are you validating server-side project ownership on every request? Client-side origin checks alone are often bypassed.
-
1
The embeddable chat widget validates project ownership and origin/referer server side on each request.
And multi-tenant projects don't yet use any isolation using Cloudflare services, I didn't have a need for that yet.
-
1
Good move validating project ownership server-side on every widget request. That matters more than CORS.
On the Cloudflare side, it’s good you called out the gap. KV and object storage isolation gets risky fast once you have teams, invites, and shared resources. Predictable keys and object paths turn into cross-tenant reads.
If you want a low-friction next step before you “need it”:
Use tenant scoped prefixes everywhere, enforced in one server-side gate.
Add server-side auth checks per read and write, not only at the widget layer.
Make object keys non-guessable. Use random IDs, not human slugs.
Treat KV as cache, not source of truth, unless you can enforce access rules at fetch time.
Add audit logs for cross-tenant access attempts.We’re a security team building Nautillo Pro for founders and small teams who want to protect users before scale adds complexity. You’re welcome to try our web attack simulator. There’s a free version for solo founders, so you can run a monthly check or test each release and see if any boundary issues slip through.
-
-
3 Comments
I didn't switch. US-heavy SaaS, Stripe already wired, so I also got stuck on 2.9 vs 5. Env var for new checkouts is fine. Polar doesn't inherit the cards, so I wouldn't use it as a cutover – every existing sub re-enters, and that's the number I'd compare to the extra 2%, not the sticker. EU in month one, I'd start on Polar. US-only, I stayed.
Good breakdown, most people get stuck comparing the wrong line item exactly like you flagged (I'm at Payrails, also a MoR, so I see this comparison a lot). On "was the fee bump worth it": the % is only part of the total cost. The bigger hidden cost of staying merchant-of-record-yourself on Stripe is the ongoing operational tax, OSS registration, per-country filings once you cross VAT thresholds, and keeping that current as rules shift. That's recurring time, not a one-time decision. Also worth knowing: "merchant of record" isn't one product, fee %, chargeback handling, payout speed and support responsiveness vary a lot between providers, so if you ever benchmark Polar against others, don't just compare the sticker rate.
The Stripe vs Polar discussion is interesting, but the thing I'd be more careful with is a pattern that shows up across all three posts.
You keep uncovering decisions that looked technical on the surface but turned out to be positioning decisions underneath.
The risk is that buyers end up evaluating NuxtBeyond as a collection of features when the real buying decision is usually much narrower than that.
I wouldn't make that call casually because it changes how people compare you against the other boilerplates in the first place.