Navigation

System Architecture Map

Complete integration diagram with subdirectories: Base44 + Supabase + External Services

Base44 - Primary Platform

Core Capabilities:

  • Entity API (CRUD operations)
  • Authentication & RLS
  • Backend Functions (Deno Deploy)
  • Integration routing layer
  • Real-time query caching

External Integrations (Click to expand):

Critical Architecture Questions

❓ If we keep functions on Base44, is data integrated with all services?

✅ YES - Base44 acts as integration router. All external APIs (Stripe, Google Cloud, Firebase, Sentry) are accessed via Base44 backend functions. Data flows: Frontend → Base44 Functions → External API → Supabase/Response.

❓ Does Supabase automatically sync with Google/Firebase/Stripe?

✅ NO - Supabase is just the database. Integrations happen via Base44 backend functions. Example: Stripe webhook → stripeWebhook function → updates Supabase users table.

❓ What happens if we migrate entities to direct Supabase?

✅ You keep Base44 functions for integrations, but access data directly via Supabase client for CRUD. Best of both worlds: Simple queries = Supabase RLS, Complex operations = Base44 functions.

Data Flow Architecture

Entity Operations:

Current: Frontend → base44.entities.* → Base44 Platform → Supabase/Cache

Hybrid: Frontend → Supabase Client (direct) OR base44.entities.* (complex ops)

Future: Frontend → Supabase RLS (simple) + Base44 Functions (complex)

Integration Flow:

All external integrations route through Base44 backend functions

Frontend → base44.functions.invoke() → Deno Function → External API

  • Stripe checkout: Frontend → createCurrencyPackCheckoutSupabase → Stripe API
  • Firebase notification: Frontend → sendFirebaseNotification → Firebase Admin SDK
  • Google Cloud: Frontend → uploadToGCS → Google Cloud Storage API
  • Sentry: Frontend → Error Boundary → sentryReporter → Sentry API
Integration Status Summary

Fully Integrated

  • Stripe
  • Google Cloud
  • Firebase
  • Sentry

Partially Integrated

  • Supabase (40% migrated)
Supabase (PostgreSQL)
hybrid migration

Access: Via Base44 SDK OR direct Supabase client

Stability: stable

Recommendation: Continue migration - 40% complete. Keep Base44 for complex operations.

Base44 Entities
legacy active

Access: Via base44.entities.* SDK

Stability: stable

Recommendation: Use for admin operations, complex queries, migrations

Google Cloud Storage
active

Access: Via Base44 functions (uploadToGCS)

Stability: stable

Recommendation: Primary media storage - fully integrated

Firebase
active

Access: Via Base44 functions (sendFirebaseNotification)

Stability: stable

Recommendation: Active for notifications - requires FIREBASE_ADMINSDK secret

Stripe
active

Access: Via Base44 functions (createCurrencyPackCheckoutSupabase, stripeWebhook)

Stability: stable

Recommendation: Fully integrated - webhook connected

Sentry
configured

Purpose: Error tracking & performance monitoring

Integration: Active - SENTRY_DSN secret set

Data Flow: Errors → Sentry dashboard

Access: Via sentryReporter component

Mixpanel
not configured

Purpose: User analytics & behavior tracking

Integration: Not configured - no secret/SDK found

Data Flow: N/A - requires setup

Access: Would need mixpanel SDK + secret

Vercel
deployment candidate

Purpose: Standalone crossword hosting

Integration: Planned for specific features

Data Flow: Static export → Vercel Edge

Access: Via vercel CLI deployment

GitHub
indirect

Purpose: Version control

Integration: Indirect - Base44 may use for deployments

Data Flow: Code → Base44 → GitHub (possibly)

Access: Not directly accessible from app