Most teams end up shipping their lakehouse data twice: once into Delta, then again into a relational database so Power BI and Tableau can render a chart. The DeltaForge ODBC driver removes the second copy entirely.
BI tools want ODBC. Lakehouses historically offered notebooks and SDKs. The path of least resistance was to copy data into a relational database. DeltaForge closes that gap with a native ODBC driver.
Delta in cloud storage plus the same data in a relational store: two bills, two formats, two failure modes. Removing the copy removes one of each.
When Power BI reads Delta directly through the driver, there is no refresh window. The number you see is the number that exists in the table right now.
RBAC and the audit log are enforced at the ODBC layer by the same engine that governs every other access path. No second GRANT list in a separate database to keep aligned.
A driver that looks like every other ODBC driver to the tool on the other end
Standard ODBC, so the tool only needs to know how to speak ODBC. No bespoke connector, no plugin, no managed gateway.
Passwords and tokens are kept in the operating system keychain, not in a plaintext config file. Corporate proxies are supported.
Decimals, timestamps, unicode strings, and exact column names land in the BI tool the same way they exist in the Delta table.
Install the driver, point Power BI at Delta, and delete the pipeline that was only there to feed a chart.