Feedback wanted: a framework where Postgres is the entire backend (no ORM/API layer)

Hi all,
I've been building pgapp (https://github.com/aadishajay/pgapp) a small
Rust project that takes an unusual approach to a fairly generic problem —
building multi-user web apps (forms, reports, charts, auth) — and wanted to
get this list's opinion, since the whole design leans on Postgres more
heavily than most tools do.

The idea: you describe the app in one plain-text file. A single binary
parses it, keeps the app's own definition as metadata inside Postgres (not
just the app's data), and serves the whole thing straight off that — no
ORM, no separate API layer, no JS build step.

I'd genuinely value critique from people who know Postgres well: does
storing an app's structural metadata alongside its data like this hold up
under real concurrent load? Are there patterns here that fight against how
Postgres wants to be used? Happy to answer questions about the internals.
Repo (README has a short GIF of the edit → run → live-app flow):
https://github.com/aadishajay/pgapp

Thanks, Aadish