Ceros
Ceros declares 27 subprocessors in its subprocessor list, which we last checked on Nov 20, 2026 (evidence). They include Amazon Web Services, Google Cloud and OpenAI. No published changes since we first read it on Sep 29, 2026.
Not listed by any tracked vendor.
Subprocessors CSV of Ceros's subprocessors · Atom feed of Ceros's subprocessors DORA draft CSV of Ceros's subprocessors as declared by Ceros what's this? ·
27 third parties.
| Name | Purpose | Location | Listed since |
|---|---|---|---|
| Amazon Web Services | AWS Redshift, AWS API Gateway, AWS Kinesis Stream, AWS Lambda, AWS Data Pipeline, AWS ElasticSearch Relevant Customer Data: Content created within the Studio and included in published experiences is processed by this Sub-processor. In addition, the Sub-processor may process User information such as IP addresses, login credentials, and names provided to the application.; Cloud Provider | AWS US East (N. Virginia) | |
| Anthropic AI | AI Service Provider; Relevant Customer Data: AI Features are optional and may be disabled by customers. When AI Features are disabled, Anthropic will not process any Customer data in connection with such features. If Customers elect to use AI Features, Anthropic will process only the data included in the applicable user inputs for the purpose of generating AI outputs. Such data will not be used to train Anthropic’s large language models or to provide services to any other customers of Anthropic or Ceros. | United States | |
| appcues | Relevant Customer Data: IP address and user name associated with login credentials, based on authentication information provided by the customer or via SSO.; User Tracking and Analytics | Unites States | |
| ClickUp | Project Management Software; Relevant Customer Data: Manages project-specific information provided by a customer in conjunction with the purchase of professional services from Ceros. If the customer does not work with Ceros in this capacity, this Sub-processor will not process any customer data. | United States | |
| Cloudflare | Content Delivery Network; Relevant Customer Data: Content included in all Ceros applications will be processed by this Sub-processor. | United States | |
| Digital Ocean | Automated Pilot Signup; Relevant Customer Data: Business and contract details related to the purchase of a Pilot with Ceros. | United States | |
| Google Cloud (Google Vertex APIs) AI | AI Service Provider; Relevant Customer Data: AI Features are optional and may be disabled by customers. When AI Features are disabled, Google will not process any data in connection with such features. If a customer elects to use AI Features, Google will process only the data included in the applicable user inputs for the purpose of generating AI outputs. Such data will not be used to train Google’s large language models or to provide services to any other customers of Google or Ceros. | United States | |
| Google Tag Manager | Relevant Customer Data: The IP address used at login and the username associated with each login. The specific data processed will depend on the authentication method chosen by the customer, including whether single sign-on (SSO) is used.; Tracking User Sign-ons | United States | |
| Grafana | Relevant Customer Data: IP address associated with login credentials. AI Features are optional and may be disabled by customers. When AI Features are disabled, Grafana will not process any data in connection with such features. If a customer elects to use AI Features, Grafana will process only the data included in the applicable user inputs for the purpose of generating AI outputs. AI interactions may be stored within Grafana for debugging purposes for a period of three (3) months, after which such data will be permanently deleted. Grafana will not use AI feature data to provide services to any other customers of Grafana or Ceros.; System Monitoring, AI Traffic Routing and Debugging | United States | |
| Intercom | Email and Chat Support; Relevant Customer Data: IP address and user name associated with login credentials, based on authentication information provided by the customer or via SSO. | United States | |
| Lacework | Network Security Monitoring; Relevant Customer Data: IP address and user name associated with login credentials, based on authentication information provided by the customer or via SSO. | United States | |
| LogRocket | Relevant Customer Data: IP address and user name associated with login credentials, based on authentication information provided by the customer or via SSO.; User Tracking and Analytics | United States | |
| Metronome | Relevant Customer Data: AI Features are optional and may be disabled by customers. If a customer elects to use AI Features, Metronome will be used solely to track AI usage, calculate usage-based credits, and generate related billing. Metronome will process only the data necessary for these purposes; Usage-Based Billing | United States | |
| Mixpanel | Relevant Customer Data: IP address and user name associated with login credentials, based on authentication information provided by the customer or via SSO.; User Tracking and Analytics | United States | |
| Okta | Identity provider; Relevant Customer Data: Primary authentication service for Ceros applications, processing user names, email addresses, passwords, and IP addresses based on customer-provided authentication information or SSO. | United States | |
| OpenAI AI | AI Services; Relevant Customer Data: Optional AI features; if used, OpenAI processes only the user’s input. No data is used to train OpenAI’s models or shared to provide services to other customers. | United States | |
| Openrouter AI | AI Traffic Routing; Relevant Customer Data: AI Features are optional and may be disabled by customers. When AI Features are disabled, Openrouter will not process any data in connection with such features. If a customer elects to use AI Features, Openrouter will process only the data included in the applicable user inputs for the purpose of generating AI outputs. Such data will not be used to train Openrouter's large language models or to provide services to any other customers of Openrouter or Ceros. | United States | |
| Pinecone | Relevant Customer Data: Gong call transcripts may be processed by this Sub-processor. If a customer requests that Gong not be used, no customer data will be processed.; Vector Database | United States | |
| Postmark | Engineering; Relevant Customer Data: The name and email provided by a customer during Pilot acceptance. | United States | |
| Remove.bg | Image Processing; Relevant Customer Data: Any images uploaded to Ceros. | Austria | |
| Replicate AI | AI Image Generation; Relevant Customer Data: AI Features are optional and may be disabled by customers. When AI Features are disabled, Replicate will not process any data on behalf of Ceros in connection with such features. If Customers elect to use AI Features, the data processed will be limited to the data included in the applicable user inputs. Such data will not be used to train Replicate’s large language models or to provide services to any other customers of Replicate or Ceros. | United States | |
| Rollbar | Error Tracking Service; Relevant Customer Data: If an error is logged it will displace partial information from the username associated with the login generating the error along with IP address. The information processed will therefore depend on the user authentication information provided by the customer and/or if SSO is utilized. | United States | |
| Sentry | Cloud monitoring; Relevant Customer Data: If an error is logged it will displace partial information from the username associated with the login generating the error along with IP address. The information processed will therefore depend on the user authentication information provided by the customer and/or if SSO is utilized. | United States | |
| Stripe | Payment Processing; Relevant Customer Data: The limited Customer Data necessary for Stripe to provide credit card payment processing. Stripe will process data only when a customer elects to pay by credit card and solely to provide the applicable payment services, comply with legal obligations, prevent fraud, and perform reconciliation or reporting. | United States | |
| Urlbox | Relevant Customer Data: The URLs submitted, any parameters or metadata included in a request, and the page content temporarily needed to render screenshots (HTML, images, CSS, and JavaScript).; Website Screenshot Service | United States | |
| Xara | PDF Processing; Relevant Customer Data: The files and content that a customers submit for PDF import, including the text, images, and metadata contained in the PDF. Xara will process this data solely for the purpose of performing the requested PDF import. | Germany | |
| Zencoder | Relevant Customer Data: Any video uploaded to Ceros.; Video Transcoding | United States |
Web TechnologiesCSV of Ceros's web technologies · Atom feed of Ceros's web technologies
Ceros's homepage made 253 requests to 24 domains, 8 services controlled by another company, and 1 domain not identified.
8 third parties by category: Analytics 3Marketing automation 2Advertising 1Other 2
cr-relay.com
6 tracked companies loaded by the homepage are not in Ceros's subprocessor list. A website can use a service without it processing customer data.
ComplianceCSV of Ceros's compliance · Atom feed of Ceros's compliance
- Certified
Certifications as Ceros's trust center lists them; reports are usually shared on request (evidence)
Service statusCSV of Ceros's status page incidents · Atom feed of Ceros's status page incidents
90 days agotoday
- 0 incidents in 90 days
- 0 major or critical
| Began | Incident | Impact | Lasted |
|---|---|---|---|
| Degraded Performance with Content Creation | minor | 2 h 58 min | |
| User Access Disrupted | major | 3 h 48 min |
Incidents per month
critical major minor no impact stated
As Ceros's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)
Incidents reported by Ceros's subprocessorsCSV of incidents reported by vendors Ceros lists · Atom feed of incidents reported by vendors Ceros lists
109 reported incidents in the last 30 days, by 15 of the vendors Ceros lists as subprocessors.
A subprocessor list names a company, not the service an incident touched. This does not show that Ceros was involved.
And 84 more. All of them: CSV · Who is around them.
ChangesCSV of Ceros's changes · Atom feed of Ceros's changes
See the list as we read it on any date: Time machine
None since tracking began.