Route every workflow
Pick one primary provider for discovery, enrichment, analysis, generation, and delivery. Retries keep the same snapshot.
Provider-routed lead operations
Build pipeline with explicit control, not black-box automation.
Discover, enrich, analyze, and contact leads through the providers you choose. LeadPilot keeps credentials isolated, jobs recoverable, and every route auditable.
- No implicit provider fan-out
- No synthetic production leads
- Modern Supabase key support
One operating layer
Scale providers without scaling confusion.
Credentials, routing, jobs, exports, and outreach share one durable contract across the web and worker runtimes.
Own every credential
Store multiple encrypted keys per provider with priorities, quotas, cooldowns, health, and deterministic request rotation.
Run durable operations
Vercel submits bounded work, Supabase holds authoritative state, and Heroku workers recover abandoned jobs safely.
Designed to fail closed
Secrets stay server-side. Tenant boundaries stay enforced.
Browser requests use publishable keys and Row Level Security. Trusted services use modern secret keys, while user JWTs are verified against Supabase JWKS.