The full list. Always current.
We publish every vendor that touches customer data - name, purpose, region, status. You get 30 days' advance notice before any new subprocessor is engaged, no email required to see who is on the list.
- VercelA
- AWSA
- E2BA
- ClerkA
- ConvexA
Where the register stands today.
A live snapshot of the vendors processing customer data on our behalf and how recently the list moved.
Transparency, by default.
Public by default
Every subprocessor is named on this page. No NDA, no support ticket, no email gate. If we use them, you see them.
30-day advance notice
Before we engage a new subprocessor, customers get at least thirty days to review it, raise concerns, or object.
Right to object
If a proposed subprocessor doesn't work for you, you can object in writing. We will work with you on a remediation or honour your termination right under the DPA.
All subprocessors processing customer data.
Filter by category or region. Click a vendor name to visit their public website. Status pills mark whether a vendor is live, pending or sunset.
Everything that moved on this page.
An append-only log of additions, removals and material changes. Anything new appears here at least thirty days before it ships.
- 2026-Q2AddedPostHog
Pending addition - product analytics with EU residency.
- 2025-Q2AddedStripe
Subscription billing rollout.
- 2025-Q2AddedAnthropic
AI model inference for the Claude family.
- 2025-Q1AddedSentry
Error tracking and release health.
- 2025-Q1AddedResend
Transactional email delivery.
- 2025-Q1AddedConvex · Clerk · E2B
Database, authentication and sandbox runtime onboarded together.
- 2025-Q1AddedVercel · AWS
Core infrastructure platform at launch.
Get 30-day advance notice.
Drop us an email and we'll add you to the subprocessor notification list. You will hear from us only when this register is about to change.
Notification cadence: only when there are changes.
How we vet every vendor before they land here.
A vendor only joins the register once it has cleared the same review every customer would run themselves.
Security review
We read the vendor's SOC 2 / ISO 27001 reports and confirm their posture matches the data category we will entrust to them.
DPA in place
A signed Data Processing Agreement covers every onboarded vendor before any production data moves.
Data residency check
We pin the processing region and confirm EU customer data stays in EU regions wherever the vendor supports it.
Insurance verification
We verify cyber liability cover sufficient to absorb a vendor-side incident and re-check it on contract renewal.
Backup coverage
We confirm backup, retention and restore capabilities so a vendor outage cannot become a customer-data outage.
Exit plan ready
Every vendor has a documented exit plan - export format, retention window, deletion confirmation - written before we sign.
Anchored in our DPA.
Engagement of subprocessors is governed by Article 28(2)–(4) GDPR and Section 5 of our DPA. We rely on prior general written authorisation paired with a notification duty whenever the register changes.
You retain the right to object to any new subprocessor. If we cannot accommodate your objection through a mitigation, the DPA gives you a termination right for the affected service.
Every subprocessor on this page has agreed to data protection obligations no less protective than the ones we owe you. Where transfers leave the EU/EEA, EU Standard Contractual Clauses and supplementary measures apply.
Subprocessor specifics.
How often is this page updated?
What if I object to a new subprocessor?
Do subprocessors see my source code?
Where do you publish historical versions of the list?
Are sub-subprocessors covered?
Can I require additional vendor commitments?
Hire your first AI engineer.
Ship by lunchtime.
5 minutes to onboard. First PR within an hour. Cancel anytime.