FMQC — members & activities portal
A public-facing portal with a members area and an admin back-office — a React front-end designed in Base44, running on the self-hosted BurgerBase backend so the organisation's data stays on its own infrastructure.
The challenge
The portal was prototyped quickly in Base44 — public pages, a member area
(profile, activities, activation-by-token) and a protected /admin section — but
it came wired to a hosted backend. The organisation wanted its member and
activity data on its own PostgreSQL, not a third-party SaaS, and a build it
could deploy and run itself.
Approach
- Kept the Base44 React front-end and pointed it at BurgerBase, the self-hosted backend, for JWT auth, a dynamic REST API, file storage and Deno serverless functions.
- Reworked the generated app for a public site with role-gated routes:
/login·/register·/activation/:tokenpublic, a members-only area, and anAdminRouteguard for/admin/*— one codebase, no separate portal. - Wrote down the repeatable fixes needed after each Base44 regeneration (file- upload calls, auth checks, Deno functions) so the app can be re-synced from the designer without breaking.
- One-command deploy:
deploy.shbrings up backend, frontend and the Postgres schema together.
Result
FMQC runs in production as a single React app — public content, member self-serve and admin management — backed entirely by the organisation’s own BurgerBase instance and database.
Add member count, the activities the portal manages, and the go-live date via the admin panel.
Want an outcome like this?
A production member portal (public pages, member area, admin) with authentication, file storage and serverless functions — no third-party SaaS backend.
Book a callTangente — quantitative portfolio analysis