TL;DR
DuckDB has announced Quack, a new protocol allowing multiple DuckDB instances to communicate over a client-server setup. This development enables concurrent multi-process access, broadening DuckDB’s application scope. The protocol is simple to set up and built on proven technologies like HTTP.
DuckDB has officially announced the release of the Quack protocol, enabling its instances to communicate in a client-server setup with multiple concurrent writers. This marks a significant expansion of DuckDB’s architecture, traditionally an in-process database, to support distributed and multi-process workloads, which is expected to broaden its applicability in data engineering and analytics.
The Quack protocol, introduced by the DuckDB team on May 12, 2026, allows multiple DuckDB instances to connect and communicate over a network, supporting both local and remote deployments. It is designed to be simple to set up, leveraging established technologies such as HTTP, and aims to support workloads ranging from bulk data operations to small, transactional queries. To use Quack, users install and load the extension in each DuckDB instance, then establish connections using a straightforward API. This development addresses longstanding limitations of DuckDB’s in-process architecture, which hindered multi-process and remote access, by providing a lightweight, fast, and flexible client-server communication layer.
Why It Matters
This development matters because it enables DuckDB to function effectively in distributed environments, supporting concurrent writes and complex workloads that were previously difficult or impossible. It opens the door for DuckDB to be used in larger-scale data pipelines, multi-user applications, and remote data access scenarios, potentially competing with traditional client-server databases like PostgreSQL. For data scientists and engineers, this means more flexible deployment options and easier integration into existing systems that rely on multi-process or distributed architectures.
DuckDB client-server protocol
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background
DuckDB, first released in 2019, has been primarily an in-process database optimized for data science and analytical workloads, where it runs within the same process as the client application. While this architecture offers simplicity and performance for single-user, local tasks, it limits multi-user and remote access capabilities. Over the years, users have devised workarounds, such as custom RPC solutions or retrofitting protocols like Arrow Flight SQL, to enable client-server communication. The new Quack protocol represents the first native, official client-server solution from DuckDB, designed from scratch without legacy constraints, reflecting a strategic shift to support broader use cases.
“We see DuckDB as a universal data wrangling tool. If this means having a client-server protocol in addition to in-process capabilities – fine. If this unlocks new use cases — excellent!”
— DuckDB team
“Designing Quack from scratch allowed us to learn from existing protocols like Arrow Flight SQL, resulting in a simple, fast, and flexible communication layer.”
— DuckDB developers
Distributed Database Management Systems: A Practical Approach
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What Remains Unclear
It is still unclear how widely adopted Quack will become in the immediate future, or how it will perform under very large-scale workloads. The protocol’s security features and compatibility with existing network infrastructure are still being evaluated. Additionally, it remains to be seen how quickly developers and users will integrate Quack into their workflows and whether alternative solutions will persist alongside it.
Database Systems: Introduction to Databases and Data Warehouses, Edition 2.0
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What’s Next
Next steps include broader adoption and testing of Quack in real-world scenarios, development of more advanced features such as authentication and encryption, and integration with existing tools and workflows. The DuckDB team plans to monitor user feedback and optimize the protocol accordingly. Future updates may include support for more complex query patterns and larger data volumes, as well as community-driven extensions.
Fraud Analytics Using Descriptive, Predictive, and Social Network Techniques: A Guide to Data Science for Fraud Detection (Wiley and SAS Business Series)
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
How does Quack differ from existing DuckDB communication methods?
Quack provides a native, lightweight client-server protocol enabling multiple DuckDB instances to communicate over a network, supporting concurrent writes and remote access, unlike the traditional in-process architecture.
Is Quack secure for production use?
Security features such as authentication and encryption are still under development. Users should evaluate the protocol carefully before deploying in sensitive environments.
Can Quack be used with existing DuckDB versions?
Quack is available starting from DuckDB version 1.5.2, and requires installing and loading the extension in each instance.
What workloads is Quack best suited for?
It is designed to support a range of workloads from bulk data operations to small, transactional queries, suitable for distributed analytics, multi-user environments, and remote data access.
