Reversibility Policy for the Unified Data Platform product
69 visualizaciones
08.07.2025 
Reversibilidad
Objective
This document describes the reversibility policy for the Unified Data Platform product covering the OVHcloud Data Platform offer.
This policy aims to implement the general reversibility principles and our compliance with the SWIPO IAAS Code of Conduct for cloud providers.
List of features
The features of the product line fall into three categories:
- Core features for which we guarantee migration capacity.
- OVHcloud implementations that require adaptation to a new migration environment.
- Specific features that cannot be guaranteed for migration as they are related to the OVHcloud environment or involve custom developments.
1 - Core features
| Function | Description | Available formats | Migration model | Available documentation |
|---|---|---|---|---|
| Data Catalog | Integration of more than 60 connectors to centralize data sources | CSV, JSON, XML, Parquet, Avro, JDBC, Kafka, REST, FTP, etc. | Inbound: configuration of standard connectors via web interface. Outbound: export metadata and data via API. | Data Catalog documentation |
| Lakehouse Manager | Unified storage based on Apache, Iceberg and Trino | Parquet, ORC, Avro, Iceberg | Inbound: manual configuration via a web interface Outbound: export via Trino, Spark, or API. | Lakehouse Manager documentation |
| Data Processing Engine | ETL/ELT pipeline orchestration with Spark and Python. | Python, PySpark | Inbound: manual configuration via web interface or git repository connection. Outbound: export workflows via Git or API. | Data processing engine documentation |
| Analytics Manager | Create dashboards with no-code or SQL (Trino) editor. | SQL, JSON | Inbound: manual configuration via the web interface. Outbound: export requests/visualizations via API. | Analytics Manager documentation |
| Applications Services | Web application deployment and APIs (Node.js, Python, Docker). | Node.js, Python, Docker, REST | Inbound: manual configuration via web interface or via git repository. Outbound: export via Git or API | Applications services documentation |
2 - OVHcloud implementations
| Function | Description | Available formats | Migration model | Available documentation |
|---|---|---|---|---|
| Data Processing Engine | ETL/ELT pipeline orchestration with Spark and Python. | OVHcloud platform-specific format, no standards deployed | Inbound: Data imported from data catalog with manual or automatic configuration of jobs Outbound: No export possible | Data processing engine documentation |
| Identity and access management | Account management and user access on the platform | NA | Inbound: Configuration via the web interface Outbound: Export user accounts in CSV format | DATAP IAM documentation |
3 - Specific features
| Function | Description | Available formats | Migration model | Available documentation |
|---|---|---|---|---|
| Integrated monitoring | Monitoring and centralized performance management developed by OVHcloud. | NA | Inbound: Default integrated tracking interface on platform Outbound: Logs and monitoring information cannot be exported | Control center documentation |
List of architectures
OVHcloud Unified Data Platform service is based on open-source technologies such as Trino, Apache Iceberg, and Kubernetes. It is compatible with OVHcloud Public Cloud architectures.
Partner Services
The OVHcloud partners concerned are listed in the OVHcloud partners directory under the "Data center expansion and migration" keywords.
OVHcloud also has a dedicated service: OVHcloud Professional Services.
Costs and fees
Features described in the tables are available at no cost, unless otherwise specified and are freely usable.
OVHcloud uses pay-as-you-go pricing, with no egress fee. Billing is interrupted immediately when the service is canceled, allowing flexible cost control.
Data retention after service termination
Once the service is canceled, all data are irreversibly deleted. It is the client’s responsibility to carry out a full backup or migration before termination.
Global Reversibility Policy (EN)
171