Building @ts_saas - TypeScript SaaS boilerplate for indie founders Skip 8 weeks of setup. Ship your idea in days. ↳ https://teapaw.org/t.co/f7dvml7iZv
Varanasi, India
Joined March 2020
- Tweets20.2K
- Following315
- Followers516
- Likes65.9K
Pinned Tweet
Building a SaaS shouldn't mean rebuilding the same 300 hours of infrastructure.
Meet @ts_saas
Auth. Billing. Email. Multi-tenancy.
Already built.
Ready to customize.
Ready to ship.
Your next SaaS starts here. 👇
Krishna Singh retweeted
Our #neatHack submission
Self Improving Software Factory for your Github
Built with @arithecfo @EntireHQ @neatlogs
teapaw.org/bettersayAJ/status/210…
building agents is easy
getting them to production is hard
today we’re launching @neatlogs to fix that
TanStack Start v1 is stable 🎉
TS-SAAS.com has been built on TanStack Start from day one, so I’m excited to update the templates for v1.
The goal stays the same: flexibility to build, infrastructure bills under control, and a great developer experience.
TanStack Start 1.0 is officially stable! 🎉
A full-stack web framework for React and Solid, already used to build millions of apps, from Fortune 500 companies to your favorite tools and weekend projects.
tanstack.com/start
Building TS-SaaS exposed a skill I underestimated.
I can spend days making an architecture decision better and still struggle to explain why a developer should care in 3 sentences.
Engineering asks whether it works.
Distribution asks whether anyone understands why it matters.
It’s Friday.
If you’re starting a SaaS this weekend, spend your time building what customers will pay for not rebuilding auth, payments, organizations, and permissions.
Start with a production-ready TypeScript foundation:
ts-saas.com
Building a SaaS?
Start with a foundation you won’t need to rebuild after launch.
Authentication, payments, organizations, permissions, infrastructure, and more ready for your product.
Build on ts-saas.com/
I found a simple way to make TS-SaaS documentation less likely to drift:
A workflow change isn't finished until its documentation changes with it.
Otherwise the codebase moves forward while the docs slowly describe a product that no longer exists.
My top supporters on X 🏆
🥇 @samongaro_
🥈 @vineerpasam
🥉 @HashamBuilds
Thank you for always showing up 🙏
I’m deliberately saying no to some TS-SaaS integrations.
Every provider I add means more configuration, documentation, testing, edge cases, and future upgrades.
Supports 12 providers sounds good on a feature page.
I’d rather properly support the paths I ship 🌱
I’m building a SaaS boilerplate, so I’m biased toward foundations, but curious what developers actually value most when choosing one.
1️⃣ Faster setup
2️⃣ Production-ready foundations
3️⃣ Maintainable architecture
What makes you keep using it after week one?
Building TS-SaaS exposed a skill I underestimated
I can spend days making an architecture decision better and still struggle to explain why a developer should care in 3 sentences
Engineering asks whether it works
Distribution asks whether anyone understands why it matters. 🌱
Your SAAS needs file storage, not another infrastructure project.
AWS S3 is powerful, but its hidden complexity can cost you more engineering time than expected.
I wrote about when S3 makes sense and when simpler alternatives might be enough 👇
my creator page is live, brands can book a post on it in two clicks unfair.so/@krishnasinghdev
If tenant isolation depends on developers remembering a filter in every query, I consider that fragile.
Where do you primarily enforce tenant scope?
1️⃣ Middleware
2️⃣ Service layer
3️⃣ Database/RLS
Maintaining reusable SaaS code has changed how I think about done.
A security fix isn't done when I merge it into TS-SaaS.
I also need to know the single-tenant and multi-tenant foundations received it without silently changing their behavior.
Distribution of improvements is part of the architecture🌱
I’m increasingly using small and understandable as a requirement for AI-generated changes.
What gives you the most confidence before merging AI-written code?
1️⃣ Tests pass
2️⃣ Manual review
3️⃣ Small isolated diff
Your SaaS idea shouldn’t spend its first few weeks becoming another auth + billing project.
TS-SaaS gives you the TypeScript foundation already built.
Auth, orgs, RBAC, payments, email, storage, deployment + more.
Start with your product, not the plumbing. 🌱
You can spend months building a beautiful SaaS that nobody needs.
Before writing code, understand the problem, the customer, and why they would pay.
I wrote about what developers should understand before building a SaaS 👇
Krishna Singh retweeted
Building a SaaS shouldn't mean rebuilding the same 300 hours of infrastructure.
Meet @ts_saas
Auth. Billing. Email. Multi-tenancy.
Already built.
Ready to customize.
Ready to ship.
Your next SaaS starts here. 👇