Building @ts_saas - TypeScript SaaS boilerplate for indie founders Skip 8 weeks of setup. Ship your idea in days. ↳ https://xitter.gq/t.co/f7dvml7iZv
Varanasi, India
Joined March 2020
- Tweets20.4K
- Following326
- Followers548
- Likes66.5K
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. 👇
I’m reviewing TS-SaaS beyond the happy-path demo.
What happens when:
- a session expires
- a payment fails
- permission is missing
- an env variable is absent
- a webhook arrives twice
Production-ready matters most when something goes wrong.
2027 could be the year you launch your first SAAS.
And you don't need to start from zero.
With our SaaS boilerplate, you can skip months of repetitive development and focus on launching your product.
The sooner you launch, sooner you can start growing your MRR 💵💵💵
40% OFF for #BlackFriday
ts-saas.com
Imagine launching your SaaS 3 months ahead of schedule.
That's 3 extra months to find customers, improve your product, and grow your MRR.
Stop building everything from scratch.
Start with our SaaS boilerplate.
40% OFF this Black Friday.
ts-saas.com
Step away from @X for a month, and the algorithm shows no mercy. 🥲
Had to take an unexpected break due to some unforeseen circumstances, but I’m finally back. Hope everyone’s been building and doing great.
Learned a ton while being offline unpacking the thoughts and lessons one by one soon. 🌱
Currently sitting in the 41% tier, but actively pushing to break into the top 17%.
The gap between average and top tier comes down to consistency.
Where are you at right now? 😅
No way someone made launching a SaaS this clean.
If you’re building your next product with TypeScript, stop wiring auth, billing, and databases from scratch.
ts-saas.com makes shipping feel effortless.
Talk to 10 potential users before you write a single line of code.
It will save you 3 months of building something nobody actually wants.
Hey indie founders, I've been building and learning from all of you.
If we're not connected yet, let's connect and build more together 🤝
Krishna Singh retweeted
Our #neatHack submission
Self Improving Software Factory for your Github
Built with @arithecfo @EntireHQ @neatlogs
xitter.gq/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. 🌱
