Side by side
DreamFactory vs Supabase
DreamFactory
21 positive (91%) · 2 mixed (9%) · 0 negative (0%)
Trust + time weighted: +91%
Top excerpts
I’ve bounced between Hue, Kasa, and Govee, and used DreamFactory alongside HA and Node‑RED when I needed a simple REST API over a DB for tracking routines.
DreamFactory just to expose the raw client data as read-only APIs so I can remix it without building new dashboards each time.
If you ever bolt AI review or search on later, products like Relativity, CaseGuard, or even DreamFactory‑fronted databases make it easier to expose only scrubbed, read‑only data to those tools.
I’ve used ... DreamFactory as a quick RBAC’d REST layer over the metrics DB when I wanted other tools to poke at firewall data without touching the core backend.
when I needed stricter backend control over a shared DB, DreamFactory gave me quick REST endpoints so I didn’t have to hand-roll a gateway first.
Supabase
41 positive (79%) · 10 mixed (19%) · 1 negative (2%)
Trust + time weighted: +77%
Top excerpts
Your proposed stack is totally fine for this. Next + Supabase is more than enough, especially if you’re solo.
Parent context: supabase + google workspace (smtp.gmail.com) Reply: Ahh yeah that explains it. Try using something like sendgrid and see if you have better results.
I am using Supabase which has OAuth capabilities
On the backend side, I’ve paired SSR apps with Hasura or Supabase for data APIs
One morning you're vibe-coding some small features and sketching designs in Figma, then you wake up a few years later with 306 open Github issues, a team, payroll, infra on Supabase