Agreed

So basically dont use django and vibe code your own framework?

Basically, yes, but:

1. You probably only need a few pieces of the framework;

2. "Vibe code" can mean "get Claude (or whatever) to help you with some AWS (or whatever) service."

Would love to see this.

Django just makes life 1000x easier. Can architect an app with data models, api, openapi, etc. within an hour.

I like mikro orm - cool to see you use that. I do prefer django however.

I see express as the backend. Why not nestjs? And are you using openapi at all for generating your frontend client?

What i've discovered is - any backend + orm should expose an openapi spec'd backend... and your frontend can autogen your client for you. Allows you to move extremely quick with the help of ai.

whats your defacto now?

looks great

you mention hasura - is that open source? you are leaning on a product for migrations that are not open source is my main concern with the above comments.

Yes, it is open source, and Docker containers are freely accessible too

https://github.com/hasura/graphql-engine

https://hub.docker.com/r/hasura/graphql-engine

I run v2.x images myself, not sure what v3 and DDN are, besides monetization efforts for the company*.

Also the migrations are just `up.sql` and `down.sql` files, there is nothing coupling you to a proprietary migration format, the value Hasura offers is generating them for you and tracking their application thru their CLI.

Are you saying you'd start a new project with alembic/sqlalchemy nowadays?

Are you able to share some of the tech stack choices behind the scenes? React, fastapi, django, go, pydantic ai, ag-ui, firecrawl, vertex ai, etc. Would love to see the tools and frameworks others are deploying with.

Yep: NextJS frontend, NodeJS backend, Gemini 2.5 Flash LLM, Firecrawl for crawling, self-hosted SearXNG for web search, and fly.io for hosting. Beyond that everything else is built internally, we don’t use many frameworks.

What about for the db? Prisma? Postgres?

Supabase

awesome!