Hi Iceberg Community,

I am reaching out on behalf of *Dataddo* to request an update to our
company’s definition/description listed on the official Apache Iceberg
Vendors page ([
https://iceberg.apache.org/vendors/](https://iceberg.apache.org/vendors/)).

To better reflect our current capabilities and integration with Apache
Iceberg, we would like to update the text as follows:

   -

   *Current Description:* *Dataddo is a fully managed data integration
   platform for moving enterprise data across cloud, on-prem, and hybrid
   environments, with first-class support for open table formats including
   Apache Iceberg. * Architecture - Dataddo runs a single control plane that
   orchestrates data planes on AWS, Azure, GCP, sovereign clouds or
   on-premises Kubernetes and OpenShift, so sensitive data never leaves your
   network. * Transport patterns - Dataddo supports ETL/ELT, CDC, streaming,
   reverse ETL, and batch delivery from hundreds of fully maintained
   connectors. * Iceberg support - Dataddo writes to Apache Iceberg via
   catalogs such as AWS Glue, REST and others, and automatically detects
   source schema drift so downstream tables don't silently break. See
   the Dataddo Platform for details.*
   -

   *Proposed Description:* *Dataddo is the enterprise data integration
   platform built to eliminate the operational ownership risk of data
   movement. *



* Acting as the connective backbone of your organization, we provide a
   fully managed connective layer that moves data to, from, and between AI
   agents and systems, databases, ERPs and SaaS. Our platform automatically
   handles API changes, schema drift, and sensitive data protection, providing
   full, granular visibility into every data flow across complex environments,
   including on-premise, hybrid, and cloud infrastructures.  By treating data
   movement as mission-critical infrastructure rather than a project, Dataddo
   enables your engineering teams to deploy with total reliability, allowing
   them to focus on high-value AI outcomes instead of ongoing pipeline
   maintenance.*

Could someone please help us update this on the website, or let us know if
we should open a specific GitHub issue/PR for it?

Thank you for your time and for maintaining such a great community.

Best regards,
Carmen Torremocha.

Reply via email to