Amperity
amperity.com
organization subprocessor disclosure · Source checked 2026-10-04
Amperity services event-stream processing; not a claim about customer stacks. Current payment and runtime unverified.
← All company lists
Data platforms · October 2026 research
Companies and websites using Confluent
Find companies and properties to review for Confluent services and integrations.
The research date describes the saved package. Inclusion does not confirm present use or a paid subscription.
Choose the Confluent list
100 reviewed company accounts
Package dated
100 reviewed Confluent company accounts. Supplier-described event-streaming use and organization subprocessor disclosures, including conditional authorization. Claims apply to the recorded property, product or workload.
Price and delivery by enquiry
Enquire about this packageDownload the contact-free CSV previewWhat is included
Enquire about the dated 100-account Confluent dataset. Confirm included company fields, source attribution and scope before private delivery.
Organization or website identity
Technology attribution
Recorded source and check dates
Property or workload scope
Reviewed contact-free examples
These approved examples illustrate the 2026-10-05 package. They are not a representative sample of all customers.
AppDirect
appdirect.com
organization subprocessor disclosure · Source checked 2026-10-04
AppDirect monetization services; not marketplace merchants. Current payment and runtime unverified.
Aspect
aspect-hq.com
organization subprocessor disclosure · Source checked 2026-10-04
Aspect recruiting-service subprocessor; not unrelated businesses named Aspect. Current payment and runtime unverified.
Carta
carta.com
organization subprocessor disclosure · Source checked 2026-10-04
Carta platform event streaming and logging; not portfolio companies or fund customers. Current payment and runtime unverified.
What we found in this list
WhosBuilt analysis of the saved October 2026 package. Findings describe this selected cohort, not market share.
Provider inventories and event-streaming workloads
Organization disclosures name roles such as event processing, logging and product hosting. Some authorize a potential provider; supplier stories separately describe named operator use.
Check whether the record describes an implemented workload or provider authorization before treating it as an event-streaming deployment.
Selected dated research cohort; present runtime, paid use, organization-wide deployment and outreach permission remain unverified. Descriptions and supplier claims apply only to their recorded scope and source date.
Package 2026-10-05 · reviewed company accounts · WhosBuilt saved-record analysis
How this list was checked
Original cohort dated 2026-10-05. Retained source-check dates span 2026-10-04 to 2026-10-05 UTC; missing original check or review times remain unknown. Recovery revision reviewed 2026-10-11. Recovery is not a source refresh or a current adoption date. Historical publication dates and account scopes remain attached to delivered rows.
100 reviewed Confluent company accounts. Supplier-described event-streaming use and organization subprocessor disclosures, including conditional authorization. Claims apply to the recorded property, product or workload.
| Source class | Count | Scope |
|---|---|---|
| organization subprocessor disclosure | Not separately counted | Saved scoped organization disclosure; authorization or a publication is not independent runtime proof. |
| supplier customer story | Not separately counted | Supplier-reported relationship at the original source date; present use remains unverified. |
Provider inventories and event-streaming workloads: Qualitative synthesis of retained accepted workload scopes; presence only, with no prevalence or market-share claim. WhosBuilt analysis of saved accepted fields for the dated October research cohort; no source refresh.
Original cohort and source dates are retained. The October 11 revision review does not establish adoption or continued deployment on that date. Missing dates and historical statements retain their original limitations.
- Public sources do not confirm current paid subscriptions, live runtime, organization-wide deployment or purchasing intent.
- Source retrieval dates record access; they do not make older statements or historical deployments current.
- Some accounts have no retained contact. Published routes retain their purpose restrictions and grant no outreach permission or deliverability guarantee.
Source access dates do not refresh historical statements. Static signals do not prove execution, payment or buying intent. Published contacts do not establish deliverability or outreach permission.
Choose the Confluent list
100 reviewed company accounts
Package dated
100 reviewed Confluent company accounts. Supplier-described event-streaming use and organization subprocessor disclosures, including conditional authorization. Claims apply to the recorded property, product or workload.
Price and delivery by enquiry
Enquire about this packageDownload the contact-free CSV previewPaid files are licensed for internal use; no resale or redistribution.