QAREEB
™
Tech Architecture
← Command Center
Technical Architecture
System layers, data flow, and component relationships.
🖥️
Frontend (React + Tailwind)
Vite + React SPA. Hosted on Base44. Responsive, mobile-first.
▼ details
⚙️
Backend / API Layer
Serverless functions on Deno runtime. Base44 BaaS handles entities, auth, and storage.
▼ details
🗄️
Database Layer
Base44 Entities (JSON schema, hosted DB). Scales to Supabase/Postgres at volume.
▼ details
🤖
AI Engine
Base44 InvokeLLM integration. JSON schema outputs for deterministic AI decisions.
▼ details
🔌
External Services (Planned)
Real integrations required for public launch. Currently simulated in UI.
▼ details
Key Data Flows
User registers
Auth + Base44 Entity
Profile created in DB
User completes interview
InvokeLLM → QareebInterview entity
AI scores 8 categories
User browses matches
InvokeLLM → QareebMatch entity
AI compatibility report generated
Mutual interest expressed
QareebMatch status update
Communication unlocked
Family invited
Family invite entity + wallet check
Meeting room access granted
Payment made
Stripe webhook → Base44 function
Wallet credited
📌 Architecture Notes
• All data currently stored in Base44 Entities — no custom backend database needed at MVP
• AI calls are client-side via Base44 InvokeLLM — move to server-side for production cost control
• External service integrations (Stripe, Twilio, Daily.co) should be implemented as Base44 backend functions
• File uploads need a CDN (Cloudinary recommended) — store file_url in entity fields