Updated September 10, 2026
Subprocessors & Service Providers
WageComply uses the providers below for the current federal V1 architecture. The production database is in the United States; WageComply is operated from India. Provider processing may involve other locations. Roles differ: Paddle handles purchases as merchant of record rather than acting only on customer payroll-processing instructions.
Supabase
Database, authentication and private object storage. WageComply uses PostgreSQL row-level security and tenant-scoped records as primary customer-data authorization boundaries.
Vercel
Application hosting, deployment and server-side runtime infrastructure for the Next.js application.
Paddle
Merchant-of-record checkout, one-time purchases, subscription billing and customer billing management. Paddle sends signed transaction and subscription lifecycle webhooks to WageComply. WageComply does not need to store raw payment-card numbers.
Resend
Transactional email delivery for account onboarding, team invitations, support/inquiry notifications and verified payroll/deadline notifications.
Google Gemini
Optional non-authoritative spreadsheet-header mapping suggestions. Gemini is not used to select wage determinations, select labor classifications, calculate payroll, decide compliance, certify a report or sign a Statement of Compliance. Deterministic application logic and human review remain authoritative.
Changes
A material provider change affecting customer data handling will be reflected here before or as the production service changes. Integrations displayed as Coming Soon are not current subprocessors merely because their names appear on the roadmap.