Manage data in Iceberg-native, open standard formats, between any pair of catalogs, across vendors, clouds, and on-premises, without compromise or lock-in.
Iceberg is the open table format every cloud and every vendor now supports. None of them offer a clean way to move tables between each other. Ice Flow is the vendor-neutral mobility layer that sits in the middle, one extension, one operator surface, every catalog.
Source from:
Hive Metastore · AWS Glue · Iceberg REST · Project Nessie · JDBC (PostgreSQL, MySQL, others) · Hadoop / HDFS
Target to:
Any of the above. Either direction. Cross-cloud, cross-vendor, or on-prem-to-cloud.
Lift an on-prem Hive estate into a cloud Iceberg catalog incrementally, source stays live, target catches up, cutover happens with rollback available.
Keep production in one cloud catalog and a DR copy in another, with location mappings handling the cross-storage path rewrite and snapshot history preserved end-to-end.
Answer DORA, Basel III, NYDFS, and APRA CPS 230 with rehearsable failover ceremonies, per-table consistency proof, and full audit trails — without building any of it yourself.
Push a producing team's catalog into a consuming team's catalog with provable consistency, the producing side keeps authority, the consuming side gets verified currency.
Register source and target catalogs side-by-side in the Symphony sidebar.
Pick tables with reusable scopes, set location mappings for cross-storage targets, choose latest-snapshot or all-snapshots mode.
Continuous or one-time replication runs; the consistency check proves the target matches the source, table by table.
