Dough vs the field · for vibe-coders who ship more than one thing
Other kits marry you to one payment provider, one frontend, and a fork you maintain alone forever. Dough is built the other way around: one base you shape into every product, swap providers without rewriting code, sell anything — and pull every future update into all of them with a single command, instead of merging a fork by hand.
the real numbers
Every figure below is what the underlying open-source layer actually ships — not a rounded-up marketing total.
Through a payment orchestration (Stripe, Adyen, Braintree, Worldpay, Checkout.com, Cybersource & more). 200+ connectors total once you count payouts, fraud and vault, across 150+ payment methods.
Google, GitHub, Apple, Microsoft and dozens more — plus any OpenID Connect provider and SAML 2.0 for B2B SSO. Magic-link / login-by-code is built in.
Transactional email wired for 15+ ESP or SMTP options, so a bad sending reputation or a price hike is a config change, not a migration.
the honest side-by-side
SaaS Pegasus is the Django competitor; ShipFast and Makerkit are the JavaScript leaders. We kept the weak rows in on purpose — a comparison you can trust on the hard rows is worth more than one that wins every cell.
| Dough Django · sell-anything | SaaS Pegasus Django | ShipFast Next.js | Makerkit Next.js / Remix | |
|---|---|---|---|---|
| Payment providers | 100+ | Stripe | Stripe + Lemon Squeezy | Stripe / LS / Paddle |
| Switch provider without rewriting checkout code | ✓ Built in | — re-integrate | — re-integrate | — re-integrate |
| Sell anything subs, lifetime, one-off, options, complex pricing | ✓ All of it | Subs + one-off | Mostly subs | Subs + one-off |
| Social login providers | 50+ + OIDC + SAML | 50+ | ~10 (NextAuth) | ~10+ (Supabase) |
| Magic / passwordless login | ✓ | ✓ | ✓ (magic link) | ✓ |
| Transactional email | 15+ ESP / SMTP | Configurable | Resend / Mailgun | Resend / others |
| Frontend choice | Svelte / Vue / React / HTML | HTMX / React | Next.js only | Next.js / Remix |
| Teams & permissions | ✓ | ✓ | — | ✓ (B2B focus) |
| SEO + AI / GEO blog | ✓ built for AI indexing | Blog | Blog | Blog / CMS |
| GDPR cookie consent | ✓ | DIY | DIY | DIY |
| Upgrade model how you get new versions | ✓ dough update |
Re-generate, re-merge | Fork — merge by hand | git pull upstream + resolve |
| Maturity | New — small & growing | Mature (since 2020) | Large community | Established |
| Price public, approximate | $299 | ~$249+ | ~$199+ | ~$299+ |
the part nobody warns you about
Buy a forked boilerplate and the day you clone it is the day it starts drifting from upstream. Six months in, every security patch and feature is a merge conflict you own — times every product you've shipped. Dough is built to be updated, not forked: one command patches all of them at once, so shipping the next thing never means re-inheriting the maintenance of the last one.
With Dough — one command
With a fork — by hand
straight talk
We'd rather you choose well than choose us. Here's the honest split.
Start with Dough
Anti-lock and evergreen by design — for vibe-coders who ship more than one thing, and for the dev shops and agencies who ship them for clients. Never bet a business on one provider's goodwill; never rebuild the same base twice.