VGI Documentation

VGI — the Vector Gateway Interface — lets you add functions, tables and catalogs to DuckDB from an ordinary separate program, in whatever language you like. No native extension to compile, no DuckDB release cadence to wait on. Data crosses the boundary as Apache Arrow record batches.

Every SDK implements the same protocol, so the Concepts pages are written once and shared. Read them first if you want the model before the syntax; otherwise jump straight into a language.

Concepts The protocol, the worker model, and the five function shapes — whichever SDK you use.

• Python
• Go
• TypeScript
• Rust
• Java

Still deciding? Language SDKs compares them side by side — install command, feature parity, repository, and the RPC layer underneath each one.

Elsewhere on the site

• VGI overview — what it is and who it’s for.
• Architecture — the engineering case: why out-of-process, what it costs in latency, how it compares to native C++ extensions, Airport and ADBC.
• Getting started — install the extension and attach your first worker.
• vgi-rpc — the transport-agnostic RPC layer underneath, and its wire-protocol specification.