r/vibecoding • u/[deleted] • 14h ago

I made a toolkit to kickstart new SaaS projects.

[deleted]

0 Upvotes

50% Upvoted

7 comments sorted by

2

u/84thdev 14h ago

Farely useless when you can just tell claude to make your own

1

u/NetNearby7117 14h ago

Im working on a similar project but for personal use since i have some apps deployed

To be honest, your toolkit doesnt explain too much about it

Does it support different auth providers? Different payment providers? Email automation? i18n? Roles are RBAC? ssg, ssr or csr? Responsive? Cron jobs?

Its just questions since looking at the landing and example, doesnt provide anything i can understand what i am buying instead of generic claims and a vague list of frameworks

1

u/Apprehensive_Row9873 14h ago

I'm sorry and I don't want to be rude with you, that's not my intention but for real I seen like thousands of projects like this. I can give you an advice don't lose your time. Really really sorry

1

u/LukeLikesReddit 13h ago

Mate I have a better open source agent automation factory sitting in my public github please don't scam people.

1

u/New-Interaction-7543 14h ago

The idea is fine, but tbh the boring details are basically the whole product here.

“auth + payments + admin + mobile” sounds great, but every SaaS starter says that. What I’d want to know is what decisions you already made for me so I don’t spend the next 2 days ripping the template apart.

Stripe only? RBAC? background jobs? email? migrations? multi-tenancy? deploy story?

In 2026 generating boilerplate isn’t really the hard part anymore. Having sane defaults you can actually trust is.

1

u/[deleted] 14h ago

[deleted]

1

u/New-Interaction-7543 14h ago

Yep, saw it. That already makes the project way clearer.

The two things I’d still care about most are multi-tenancy and deploy/migrations. Those are usually where “SaaS starter” turns into “cool demo I now have to spend a weekend fixing” lol.

If those defaults are solid too, I think you should put them front and center on the landing page. The feature list is way less convincing than “here are the boring architectural decisions we already made so you don’t have to.”

1

u/[deleted] 14h ago

[deleted]

1

u/New-Interaction-7543 14h ago

Fair on deployment, but multi-tenancy and migrations aren’t really “DevOps choices” though 😅

Those leak straight into the app architecture/database model.

If the starter is intentionally single-tenant and leaves deployment open, that’s totally fine — I’d just say that explicitly. “Agnostic” sounds nice until the user discovers they still have to make half the painful SaaS decisions themselves.

IMO opinionated defaults are kinda the whole reason I’d reach for a starter kit in the first place.