Skip to content

systems

Claude edited this page Sep 23, 2026 · 1 revision

Systems

Active contributors: ferdiiskandar

The systems lens covers the shared infrastructure behind the desktop shell and the three product tools. Each system is optional at runtime: Transform runs with nothing configured, the guest Optimizer path needs one provider key, and the data, billing, auth, and email paths activate only when the desktop shell has the matching credentials.

System One-line purpose
LLM providers Provider adapters, scoped OpenAI overrides, readiness resolution, encrypted user keys, and token estimation
Authentication Supabase password auth, desktop session storage, and Supabase-to-Prisma user resolution
Billing and subscriptions Four tiers and their limits, atomic quota tracking, Xendit invoices, and webhook activation
Email and rate limiting Idempotent welcome-email queue with retries, plus shared auth abuse counters
Embeddings and search OpenAI embeddings and pgvector cosine similarity for prompt search
Data and Prisma The PostgreSQL schema, model relationships, enums, and the Prisma client singleton

Cross-cutting context lives in Architecture, Data models, Configuration, and Security.

Clone this wiki locally