The no code stack we ship to production
Supabase, TanStack, Lovable. Where each one fits, where it breaks, and the rules we use to keep code paths sane.
Founders and technical leaders picking a stack for the next internal build or services product.
What you will take away
- The three production tools we ship every project on
- The tools we deliberately do not use, and why
- Where each tool stops fitting and what we replace it with
- How to evaluate your own stack against shipping speed, not benchmarks
Agenda
This recording is the deep dive on the stack we ship to every client. The companion piece to the no code stack guide, with more time on the seams and the failure modes.
We walk through every job a serious no code stack has to do, the tool we use for each, the tools we deliberately do not, and the conditions under which we would swap a piece.
What this session is and is not
This is not a tools roundup. It is the production stack we run client work on, with the actual rules we follow when it starts straining at the seams. You will leave with a clear sense of what we would ship for your next build and what we would skip.
It is also not a pitch for any specific tool. If anything, the session is opinionated about what to leave out of a stack. Three production tools is the floor and the ceiling for most builds we ship.
Want the stack evaluated for your project?
If you are picking a stack for a new build and want a second opinion, the call is thirty minutes. We will tell you what we would build on for your specific case.
Frequently asked questions
Is this stack vendor-locked?+
No. The code is standard React, TypeScript, and Postgres. The data is exportable. The deploys are yours. Each piece is replaceable per-feature, not all-or-nothing.
Can you ship without one of the three pieces?+
Yes, but the build slows down. We have done client projects on subsets of the stack. Each substitution costs days of integration work that the default stack absorbs.
Do you self-host any of it?+
Supabase can be self-hosted; in practice every client project runs on managed Supabase because the operational cost of self-hosting beats the per-month savings. The other two pieces are managed by design.
More sessions
Got an idea? We can ship it next week.
30-minute discovery call. We tell you what's possible, what it costs, and when it ships.