# Sub-processors

> The providers that process customer data for Keryn Cloud, what each does, and how changes are announced.

Source: https://keryn.dev/subprocessors/

Keryn Cloud uses the providers below. Local scanning (the CLI, the desktop app, the browser app and the extensions) sends nothing to Keryn or to these providers by default. This list was published on 2026-11-16 and is kept in step with the service.

| Provider | What it does for Keryn | Data it handles |
|---|---|---|
| Vercel | Hosting and serverless compute for Keryn Cloud and this site | Everything that passes through requests and responses of the service, including account data and scan targets and results in transit |
| Supabase | Postgres database for Keryn Cloud, scheduled dispatch and secret vault | Account and organisation data, projects, jobs, scan results, credit ledger, usage receipts, audit events |
| Anthropic | Model provider for agentic tasks a customer starts: triage, summary, remediation | The content of those tasks (findings and the code excerpts the task needs), under a token cap per task. Not used by local scans or ordinary scans in Keryn Cloud |
| Stripe | Payments: credit top-ups, the Team plan and the billing portal | Billing contact, organisation reference and payment events. Card details are entered at Stripe and never reach Keryn |
| Metronome | Credit grants, balances and usage mirror | Organisation identifier, credit amounts, usage counts and product labels. No source code or findings |
| Resend | Transactional email: sign-in and verification links, notices | Recipient email addresses and message content |
| GitHub | Sign-in with GitHub when you choose it; reading public repositories, or repositories you name or connect | Account identifier and email for sign-in; the repository contents you point a scan at |

If you sign in with your own identity provider (OIDC or SAML), that provider is your own service and not a Keryn sub-processor.

## Regions

Keryn Cloud runs on Vercel in the `iad1` region (Washington DC, US East) with its database on Supabase in AWS `us-east-1` (N. Virginia, US East). The other providers operate in their own regions, which Keryn does not select. Changes follow the notice rule below.

## Changes

Keryn gives 30 days' notice before a new or replacement sub-processor handles customer data, by email to organisation owners and by updating this page. A customer may object on reasonable data-protection grounds within that period. The data processing terms are drafted per customer and reviewed by counsel before signature.

## Questions

Write to [security@keryn.dev](mailto:security@keryn.dev). See also [privacy](https://keryn.dev/privacy/), [security](https://keryn.dev/security/) and [Keryn Cloud data and limits](https://keryn.dev/docs/cloud/data-and-limits/).
