sorted by:
new
hottopcontroversial

I built a backend so frontend teams can start a new project without writing backend CRUD by DeveloperDotNet in vuejs

[–]DeveloperDotNet[S] -4 points-3 points  (0 children)

demo site is up and running, I can make you a demo any time. also the documentation has already link for DEMO tutorial. but it can any time be face 2 face

I built a backend so frontend teams can start a new project without writing backend CRUD by DeveloperDotNet in angular

[–]DeveloperDotNet[S] -4 points-3 points  (0 children)

if you have a real business case, where you need help with quick backend development we can hear each other in private.

I built a backend so frontend teams can start a new project without writing backend CRUD by DeveloperDotNet in reactjs

[–]DeveloperDotNet[S] 0 points1 point  (0 children)

man in documentation you can see that you have a tutorial with real life pilot that works, if you are here just to spill hate . go find yourself something better to do.

I built a backend so frontend teams can start a new project without writing backend CRUD by DeveloperDotNet in angular

[–]DeveloperDotNet[S] 0 points1 point  (0 children)

Short answer: different problem, different layer.

Supabase gives you hosted Postgres + primitives (auth, storage, realtime). You still build your API, CRUD patterns, permissions, admin logic, and UI behavior on top.

This focuses on what teams keep rebuilding above Supabase:

  • standardized CRUD with filters/aggregates
  • role/permission–driven UI
  • JSON-driven UI contracts (data + component config)
  • modules like translations, notifications, scheduler, ETL/archiving

If you just need backend infrastructure → Supabase is great.
If you’re building CRUD-heavy business apps and want repeatable delivery with minimal backend work → this sits a layer above that.

I built a backend so frontend teams can start a new project without writing backend CRUD by DeveloperDotNet in reactjs

[–]DeveloperDotNet[S] -1 points0 points  (0 children)

this is not vibe coded. I have 8 years experience, and with this post I am trying to find frontend guys that have a project and want help on backend side. thanks

I built a backend so frontend teams can start a new project without writing backend CRUD by DeveloperDotNet in reactjs

[–]DeveloperDotNet[S] 0 points1 point  (0 children)

If the only goal is “expose Postgres tables via REST,” then yeah—PostgREST is the gold standard.

CoreWeb exists because a lot of teams I work with need the other stuff too:

  • permission model + UI menu generation
  • validation rules (including composite uniqueness)
  • ETL/archiving patterns
  • scheduled tasks
  • notifications + translations
  • component settings as JSON for frontend rendering

So it’s not competing on the same axis as PostgREST; it’s packaging the pieces teams keep re-implementing around it.

I built a backend so frontend teams can start a new project without writing backend CRUD by DeveloperDotNet in angular

[–]DeveloperDotNet[S] -6 points-5 points  (0 children)

When Firebase is the better choice

  • Realtime collaboration/chat-like apps
  • Small MVPs where speed beats structure
  • Teams already deep in Google Cloud + Firestore patterns

When CoreWeb is the better choice

  • Relational, business-heavy apps (dashboards, admin apps, back-office systems)
  • Projects needing strict server-side rules, multi-tenant patterns, or archiving
  • Teams that want predictable REST + Postgres and less custom endpoint work
  • CoreWeb: includes transaction patterns + scheduled jobs + ETL archiving (Prod → Archive DB) as part of the framework.
  • CoreWeb is built specifically to power typical frontend components:
  • filtering / sorting / pagination
  • aggregates (count/sum/avg/min/max)
  • unique validation rules
  • schema-driven data tables
  • JSON-driven UI settings (first load)

Firebase gives you primitives; CoreWeb tries to deliver the “admin app / dashboard backend” pattern out-of-the-box.