Theme 1: Appreciation of humor / fake testimonials
“I love the (well‑disclosed) fake testimonials. Hilarious!” – phren0logy
“So good. I laughed out loud at this.” – adamddev1 (quoting the testimonial: “I’ve told four separate therapists about Typebase. Two stopped taking me as a client. The other two are now shipping an app with it.”)
“I love your approach, fake testemonials and all.” – desireco42
Theme 2: Interest in technical ergonomics, deployment clarity, and comparison to existing tools
“I like the idea of the db defined api like postgraphile and hasura but had trouble with testing and ergonomics. This looks pretty nice though, it’s cool that you’re thinking about ergonomics for working with coding agents.” – rgbrgb
“though the deploy wasnt clear if i can just run migration on some pg url. and it wasnt clear if i can bind some middleware into my existing app server (like express)” – bosky101
“when you deploy there, does Typebase use D1 for the DB, or does the Postgres/Neon backend stay the same regardless of which server target you pick (Vercel/Workers/Deno)?” – SifatAhmed
“Seems much more human‑maintainable to have a classic spring/golang backend.” – k4rli
Theme 3: Skepticism about over‑engineering and preference for traditional backends
“Looks an awful lot like a orpc, just built on top of drizzle instead of raw queries… it seems like gross duct tape that will bite you in three years.” – ramon156
“It’s like next.js but for backend… But the wheel needs to be reinvented on how to do everything.” – pyrolistical
“that’s likely the promise but it’s so confusing and high cognitive overhead to maintain that backend <-> frontend relationship… nextjs dx is a special kind of hell.” – apsurd
“Enterprise software, stuff that you expect to scale exactly because it has queues and distributed computing.” – SillyUsername (implying a poor fit)