VeloDB

velodb.io

VeloDB declares 7 subprocessors in its subprocessor list, which we last checked on Nov 12, 2026 (evidence). They include Amazon Web Services, Google Cloud and Microsoft. No published changes since we first read it on Nov 6, 2026.

Subprocessors CSV of VeloDB's subprocessors · Atom feed of VeloDB's subprocessors DORA draft CSV of VeloDB's subprocessors as declared by VeloDB what's this? · 

7 third parties.

NamePurposeLocationListed since
Amazon Web Services AICloud hosting and infrastructure; Provides cloud hosting, infrastructure, control plane hosting, and AI model hosting through AWS Bedrock.Customer selected
Atlassian Customer support ticketing; Processes customer support requests, ticket communications, and related attachments.United States
Google Cloud Platform Cloud hosting and infrastructure; Provides cloud hosting and infrastructure services for VeloDB Cloud deployments.Customer selected
Microsoft Azure Cloud hosting and infrastructure; Provides cloud hosting and infrastructure services for VeloDB Cloud deployments.Customer selected
Office 365 Customer support email; Processes customer communications submitted through support channels.United States
Slack Customer support messaging; Supports customer communications and support operations.United States
Stripe Payment and billing processing; Processes customer billing and payment transactions.United States

Web TechnologiesCSV of VeloDB's web technologies · Atom feed of VeloDB's web technologies

VeloDB's homepage made 127 requests to 19 domains, and 7 services controlled by another company.

Analytics (4): Google Cloud, Reo.Dev, LinkedIn; usually detected as Analytics: posthogAdvertising (1): usually detected as Advertising: MicrosoftMarketing automation (1): HubSpotOther (1): reviewed as Development: GitHub

7 third parties by category: Analytics 4Advertising 1Marketing automation 1Other 1

Third parties 7 · 44 requests
Google Cloudsubprocessor Google Analytics Google Tag Manager 10% of the page's requests 13
HubSpot HubSpot 7% of the page's requests 9
Microsoftsubprocessor clarity.ms 6% of the page's requests 7
posthog posthog.com 5% of the page's requests 6
Reo.Dev Reo.Dev 4% of the page's requests 5
LinkedIn Linkedin Insight Tag 2% of the page's requests 3
GitHub github.com <1% of the page's requests 1
First party 1 · 83 requests
VeloDB Ant Design Emotion HSTS Microsoft Clarity Next.js 15.5.18 Next.js App Router PWA Priority Hints React Recharts Swiper Vercel Vercel Analytics Webpack 65% of the page's requests 83

4 tracked companies loaded by the homepage are not in VeloDB's subprocessor list. A website can use a service without it processing customer data.

ComplianceCSV of VeloDB's compliance · Atom feed of VeloDB's compliance

Certified
Says it complies with

Certifications as VeloDB's trust center lists them; reports are usually shared on request (evidence)

Service statusCSV of VeloDB's status page incidents · Atom feed of VeloDB's status page incidents

Aug 15: before our history of this status pageAug 16: before our history of this status pageAug 17: before our history of this status pageAug 18: before our history of this status pageAug 19: before our history of this status pageAug 20: before our history of this status pageAug 21: before our history of this status pageAug 22: before our history of this status pageAug 23: before our history of this status pageAug 24: before our history of this status pageAug 25: before our history of this status pageAug 26: before our history of this status pageAug 27: before our history of this status pageAug 28: before our history of this status pageAug 29: before our history of this status pageAug 30: before our history of this status pageAug 31: before our history of this status pageSep 1: before our history of this status pageSep 2: before our history of this status pageSep 3: before our history of this status pageSep 4: before our history of this status pageSep 5: before our history of this status pageSep 6: before our history of this status pageSep 7: before our history of this status pageSep 8: before our history of this status pageSep 9: before our history of this status pageSep 10: before our history of this status pageSep 11: before our history of this status pageSep 12: before our history of this status pageSep 13: before our history of this status pageSep 14: before our history of this status pageSep 15: before our history of this status pageSep 16: before our history of this status pageSep 17: before our history of this status pageSep 18: before our history of this status pageSep 19: before our history of this status pageSep 20: before our history of this status pageSep 21: before our history of this status pageSep 22: before our history of this status pageSep 23: before our history of this status pageSep 24: before our history of this status pageSep 25: before our history of this status pageSep 26: before our history of this status pageSep 27: before our history of this status pageSep 28: before our history of this status pageSep 29: before our history of this status pageSep 30: before our history of this status pageOct 1: before our history of this status pageOct 2: before our history of this status pageOct 3: before our history of this status pageOct 4: before our history of this status pageOct 5: before our history of this status pageOct 6: before our history of this status pageOct 7: before our history of this status pageOct 8: before our history of this status pageOct 9: before our history of this status pageOct 10: before our history of this status pageOct 11: before our history of this status pageOct 12: before our history of this status pageOct 13: before our history of this status pageOct 14: before our history of this status pageOct 15: before our history of this status pageOct 16: before our history of this status pageOct 17: before our history of this status pageOct 18: before our history of this status pageOct 19: before our history of this status pageOct 20: before our history of this status pageOct 21: before our history of this status pageOct 22: before our history of this status pageOct 23: before our history of this status pageOct 24: before our history of this status pageOct 25: before our history of this status pageOct 26: before our history of this status pageOct 27: before our history of this status pageOct 28: before our history of this status pageOct 29: before our history of this status pageOct 30: before our history of this status pageOct 31: before our history of this status pageNov 1: before our history of this status pageNov 2: before our history of this status pageNov 3: before our history of this status pageNov 4: before our history of this status pageNov 5: before our history of this status pageNov 6: no incident reportedNov 7: no incident reportedNov 8: no incident reportedNov 9: no incident reportedNov 10: no incident reportedNov 11: no incident reportedNov 12: no incident reported

90 days agotoday

No incidents reported since Nov 6, 2026

As VeloDB's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)

Incidents reported by VeloDB's subprocessorsCSV of incidents reported by vendors VeloDB lists · Atom feed of incidents reported by vendors VeloDB lists

10 reported incidents in the last 30 days, by 1 of the vendors VeloDB lists as a subprocessor.

A subprocessor list names a company, not the service an incident touched. This does not show that VeloDB was involved.

DateCompanyIncidentImpactLasted
StripeElevated Instant Payouts failures no impact stated2 h 5 min
StripeElevated Issuing errors from 17:13 - 20:41 UTC minor4 h 36 min
StripeElevated Blik errors no impact stated1 h
StripeElevated Bancontact errors no impact stated3 h 35 min
StripeElevated Bancontact errors no impact stated2 h 25 min
StripeSpike in cancellations and expired errors with PayByBank payments no impact stated2 h 17 min
StripeElevated Revolut Pay errors no impact stated9 h 32 min
StripeElevated declines on Mastercard no impact stated2 h 18 min
StripeElevated declines on Visa no impact stated53 min
StripeElevated Amazon Pay errors no impact stated12 min

Who is around them.

ChangesCSV of VeloDB's changes · Atom feed of VeloDB's changes

See the list as we read it on any date: Time machine

None since tracking began.

Rating badge for VeloDB's site

VeloDB transparency rating

It updates with the rating.

<a href="https://thirdpartyindex.com/vendors/velodb"><img src="https://thirdpartyindex.com/badge/velodb.svg" alt="VeloDB transparency rating on Third Party Index" height="20"></a>
[![VeloDB transparency rating on Third Party Index](https://thirdpartyindex.com/badge/velodb.svg)](https://thirdpartyindex.com/vendors/velodb)