Supabase Integration

How Supabase is used throughout the 360 platform.

Services

Supabase Service	Usage
Authentication	User authentication and session management.
PostgreSQL	Primary application database.
Edge Functions	Backend APIs, AI requests, crawler endpoints, automation.
Realtime	Live chat synchronization.
Storage	Application assets and uploaded content.

Platform Integration

Supabase is used across multiple parts of the 360 platform rather than being limited to a single application. Frontend applications communicate with Supabase services for authentication, backend processing, data storage, and realtime updates.

Most server-side operations are performed through Supabase Edge Functions. These functions provide APIs used by search services, AI features, crawler systems, user operations, and other platform components.

Database

Supabase PostgreSQL stores platform data used throughout 360.

Data Type	Description
User Accounts	Authentication and profile information.
Search Indexes	Indexed crawler results and search metadata.
Chat Messages	Conversation history and message records.
Platform Configuration	Application settings and internal configuration.
Application Data	Data used by platform services and tools.

Search

Search services rely on Supabase for storage and backend processing. Indexed content is stored in PostgreSQL and accessed through backend APIs rather than direct database connections from clients.

AI

AI features use Supabase Edge Functions as the backend layer. Requests are received by an Edge Function, processed server-side, and returned to the frontend application.

Chat

The messaging system uses Supabase Realtime to synchronize conversations between connected clients. New messages are delivered through realtime subscriptions as they are written to the database, where they are then saved in tables for history.

Client │ subscribe() │

🔽🔽🔽

Supabase Realtime │ database change │ broadcast │

🔽🔽🔽

Connected Clients

Typical Request Flow

Frontend Application │

🔽🔽🔽🔽🔽

Supabase Auth │

🔽🔽🔽🔽🔽

Edge Function │ ├─ PostgreSQL ├─ Storage ├─ Realtime |-> External Services │

🔽🔽🔽🔽🔽

JSON Response

Security

Database credentials are not exposed to frontend clients.
Protected operations execute through Edge Functions.
Authenticated requests are validated before accessing protected resources.
Third-party API credentials remain server-side.