Open Data Infrastructure (ODI) Implementation Architecture
Partner Capabilities: Delivery
November 4, 2026
Session 1: 3:00 PM GMT / 10:00 AM EST Session 2: 4:00 PM PST / 9:00 AM AEST (next day)
Virtual
Angel Hernandez
Martin Knazovicky
The architecture pattern: how Fivetran lands data as Iceberg and Delta Lake tables in the client's own cloud storage, how Snowflake and Databricks query it externally, and how bronze and silver layers in the lake feed the warehouse gold layer without reloading or re-ingesting data.
The "yes, and" delivery motion: how to position open data infrastructure as complementary to existing cloud platform contracts rather than a rip-and-replace, and what that means for how you scope and price the engagement.
Security and governance in practice: private networking, write credentials, and how governance stays with the client's existing compute engine catalogs, so you can deliver this in regulated, compliance-heavy environments.
You're all set, [Name].
Registration closed.
This session is a technical walkthrough of how data moves from source systems into open Iceberg and Delta Lake tables stored in the client's own cloud account, with Fivetran managing ingestion, schema evolution, deduplication, and table maintenance. Fivetran fills the gaps the major cloud platforms leave open: one governed copy of data that Snowflake, Databricks, and AI tooling can all query natively, without the client paying to re-ingest per engine. The session covers the full architecture, the security model, and the "yes, and" framing that makes this a conversation you can have in any account, regardless of what cloud contract they already have.
Who should tune in:
Solution architects and delivery consultants building or scoping data platform engagements who want to add open data infrastructure as a concrete deliverable, not just a positioning conversation.
The architecture pattern: how Fivetran lands data as Iceberg and Delta Lake tables in the client's own cloud storage, how Snowflake and Databricks query it externally, and how bronze and silver layers in the lake feed the warehouse gold layer without reloading or re-ingesting data.
The "yes, and" delivery motion: how to position open data infrastructure as complementary to existing cloud platform contracts rather than a rip-and-replace, and what that means for how you scope and price the engagement.
Security and governance in practice: private networking, write credentials, and how governance stays with the client's existing compute engine catalogs, so you can deliver this in regulated, compliance-heavy environments.
Angel Hernandez
Martin Knazovicky
Angel Hernandez
Martin Knazovicky
This session is a technical walkthrough of how data moves from source systems into open Iceberg and Delta Lake tables stored in the client's own cloud account, with Fivetran managing ingestion, schema evolution, deduplication, and table maintenance. Fivetran fills the gaps the major cloud platforms leave open: one governed copy of data that Snowflake, Databricks, and AI tooling can all query natively, without the client paying to re-ingest per engine. The session covers the full architecture, the security model, and the "yes, and" framing that makes this a conversation you can have in any account, regardless of what cloud contract they already have.
Who should tune in:
Solution architects and delivery consultants building or scoping data platform engagements who want to add open data infrastructure as a concrete deliverable, not just a positioning conversation.