1. n8n (Self-Hosted) — The Brain 🧠
What I use it for:
Business logic
Automations
Background jobs
API orchestration
AI workflows
Data syncs
n8n replaces:
Backend cron jobs
Glue code
One-off scripts
Most “custom backend logic”
Once you self-host it, you stop worrying about execution limits and start thinking in systems.
2. Supabase (Self-Hosted) — Database, Auth, Realtime
Supabase gives me:
PostgreSQL
Auth
Realtime subscriptions
Row-level security
Storage (if needed)
Self-hosting Supabase means:
Fixed cost
No vendor lock-in
Full control over schemas and policies
I use Supabase as:
The single source of truth
Realtime state layer for frontends
Auth provider for tools and Micro-SaaS
3. Lovable — Frontend Without Friction
Lovable is where speed really compounds.
Instead of:
Designing UI from scratch
Writing frontend boilerplate
Fighting CSS
I describe the product and logic, and Lovable generates:
Clean UI
Dashboards
CRUD flows
Forms
Tables
This lets me focus on product thinking, not pixels.
For MVPs and internal tools, this is a massive advantage.
4. Netlify — Free, Boring, Reliable Hosting
Frontend hosting should be:
Invisible
Cheap
Stable
Netlify does exactly that.
CI/CD out of the box
Custom domains
SSL
Zero infra thinking
I deploy and move on.
How Everything Fits Together
Here’s the real magic:
Lovable → UI & frontend
Supabase → Data, auth, realtime
n8n → Logic, automation, AI, workflows
Netlify → Hosting
This separation gives me:
Fast iteration
Replaceable components
No monolith
Clear ownership per layer
If something breaks, I know exactly where to look.
Why This Stack Works So Well
Low fixed costs
Minimal mental overhead
Easy to explain to clients
Easy to maintain
Easy to scale when needed
Most importantly:
It lets me ship.
Not plan.
Not refactor endlessly.
Not over-engineer.
Just ship → get feedback → improve.
Final Thoughts
You don’t need a massive stack to build serious products.
You need:
Clear use cases
Fast feedback loops
A stack that stays out of your way
Top comments (0)