Ragbag
AI apps
Next.js RAG starter: upload documents, chat with citations, bill by usage
SaaS starter kits, tested
Every SaaS needs auth, billing and a settings page, and none of them sell it. Pick a starter that already has them and spend the month on the part customers pay for.
Featured
Hand-picked by the editors this month.
AI apps
Next.js RAG starter: upload documents, chat with citations, bill by usage
Mobile
Expo and Supabase starter with RevenueCat paywalls and push notifications
Rails & Phoenix
Rails 8 starter with Hotwire, Solid Queue and the Pay gem, ready for teams
SvelteKit & Astro
SvelteKit and Supabase starter with teams, billing and a tidy admin
Next.js & Remix
Next.js App Router starter with orgs, roles, Stripe and an admin that's actually done
PHP & Laravel
Laravel 12 with Livewire, Filament admin and Cashier for Stripe or Paddle
Just added
48 starters in 7 categories, newest first.
AI apps
Django pipeline starter for AI document extraction, priced per page
Mobile
Flutter and Supabase starter with realtime chat and maintained releases
Python & Django
Schema-per-tenant Django kit for B2B products with strict data isolation
AI apps
Next.js RAG starter: upload documents, chat with citations, bill by usage
PHP & Laravel
Headless Laravel API with a Nuxt front end, built for web and mobile clients
SvelteKit & Astro
SvelteKit, Turso and Polar for edge-hosted subscription apps
Python & Django
Django and Wagtail starter for paid newsletters, courses and memberships
Next.js & Remix
Next.js SaaS with Payload CMS for the blog, docs and changelog
Rails & Phoenix
Rails backend with an Inertia and React front end, no separate API
AI apps
Credits, metered billing and rate limits for AI products, on Next.js
FAQ
Can't find what you need? Read about how we work.
We clone or buy the kit, follow its own setup docs on a clean machine and time how long it takes to run locally. Then we deploy it to the host it recommends, sign up, reset a password, pay with a Stripe or Paddle test card, cancel, invite a second user to a team and check the admin panel. Anything that breaks goes into the listing.
Some paid kits pay us an affiliate commission, usually 20–30% of the sale, when you buy through our link. Those listings are marked on the detail page. Affiliate status never changes the order, the rating or the limitation we write, and kits without an affiliate program are listed the same way.
Every listing is re-checked at least every 90 days: price, license, last commit date and whether the demo still works. Kits with no meaningful commit for six months get a warning, and after a year without updates we remove them.
Start with the stack you already know, not the one with the nicest landing page. Then check three things: does it handle teams if you sell to businesses, does it support your billing provider and country, and can you read the code in an afternoon. A smaller kit you understand beats a large one you fight.
Sometimes. Paid kits tend to have better docs, a support channel and more polished billing flows. Open-source kits are easier to audit and have no license limits on how many products you build. If you plan to ship several products, check whether a one-time license covers unlimited projects.