Infrastructure overview
Where VisibleMax runs: Vercel, Supabase, Trigger.dev, Polar, and AI provider APIs.
Updated 2026-08-06
VisibleMax is a managed SaaS product. Customer workloads run on a small set of cloud platforms chosen for reliability, auth, durable jobs, and payments.
Core stack
| System | Role |
|---|---|
| Vercel | Application hosting, serverless/edge delivery, and production web surface |
| Supabase | Authentication, Postgres database, and row-level product data |
| Trigger.dev | Durable background jobs for crawl, probe, analysis, and related pipelines |
| Polar | Checkout, subscriptions, invoices, and customer billing portal |
| AI provider APIs | OpenAI (ChatGPT), Anthropic (Claude), Google (Gemini), Perplexity, xAI (Grok), DeepSeek — probes and Gemini structural analysis |
High-level data flow
- 1
You connect a site
Project metadata is stored in Supabase under your workspace.
- 2
A scan starts
Auth and entitlements are checked; Trigger.dev runs crawl → probe → analysis stages.
- 3
Providers are called
Keyed AI APIs receive prompts; Gemini powers structural analysis of the crawl corpus.
- 4
Results land in the app
Scores, findings, and assets are written to the database and shown in the Vercel-hosted UI.
- 5
Billing stays separate
Polar manages payment state; entitlements sync back so plan limits stay accurate.
Dependency implications
- If an AI provider API is down or unkeyed, that probe skips; other stages can still complete.
- Database or auth incidents on Supabase affect login and persisted reports.
- Job delays on Trigger.dev can make scans take longer than usual.
- Polar outages can delay checkout or portal access without deleting existing entitlements already synced.
Related
Still stuck? Contact support with your project URL and what you already tried.