AI ERP with agents inside the systems you run
AI phone and voice agents for real calls
LLM.coPrivate, self-hosted LLM deployments
Legal AI infrastructure for firms
AI RFP discovery and response drafting
Automatic.coBusiness process automation
CyberAttack.aiThreat detection and defense
Secure AI virtual data roomschdb
chDB is an embedded SQL OLAP engine powered by ClickHouse that runs directly in Python applications without requiring a separate server. It supports pandas-compatible DataStore API and native SQL queries, with I/O support for Parquet, CSV, JSON, Arrow, ORC and 60+ other formats.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | chdb-io/chdb |
| Owner | chdb-io |
| Primary language | Python |
| License | Apache-2.0 — OSI-approved |
| Stars | 2.8k |
| Forks | 125 |
| Open issues | 42 |
| Latest release | v4.2.0 (2026-07-02) |
| Last updated | 2026-07-07 |
| Source | https://github.com/chdb-io/chdb |
What chdb is
In-process OLAP engine using ClickHouse backend compiled to Python bindings; supports DB API 2.0, lazy query evaluation with automatic SQL generation, minimized C++/Python data copying via memoryview, and pluggable query routing to optimal execution engine (ClickHouse or pandas).
Get the chdb source
Clone the repository and explore it locally.
git clone https://github.com/chdb-io/chdb.gitcd chdb# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Python 3.9+ required; macOS and Linux (x86_64, ARM64) only—Windows support not listed in documentation.
- Memory footprint grows with dataset size; no built-in spilling to disk, so large datasets may exhaust RAM.
- Lazy evaluation requires explicit `.compute()` or result fetch to trigger execution; unexpected if users expect eager evaluation.
- DataStore API covers 209 DataFrame methods and 334 SQL functions, but compatibility is not 100%; review specific operations before committing.
- Version 4.2.0 (July 2026) is recent; validate stability and performance in your workload via PoC before production deployment.
When to avoid it — and what to weigh
- Persistent, Multi-User Database Requirements — chDB is in-process and transient by default. If you need durable, multi-user, multi-tenant data access with ACID guarantees, use a dedicated ClickHouse server or other production database.
- Large Distributed Queries — chDB runs in a single process. For massive-scale distributed analytics across clusters, a full ClickHouse cluster is more appropriate.
- Real-Time Streaming Ingestion — chDB is not designed as a streaming sink. If you need sub-second event streaming ingestion, consider Kafka+ClickHouse or alternative stream processing systems.
- Complex Transactions & Relational Integrity — OLAP engines prioritize analytical queries over transactional consistency. If strong ACID guarantees and row-level updates are critical, use PostgreSQL, MySQL, or an OLTP database.
License & commercial use
Apache License 2.0 (Apache-2.0). Permissive open-source license allowing commercial use, modification, and distribution with proper attribution and liability disclaimer.
Apache 2.0 explicitly permits commercial use without licensing fees. Derivative works and proprietary extensions are allowed; include a copy of the license and notice of changes. No warranty or liability assumed by licensor. Verify compliance with your legal counsel for enterprise deployments.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Good |
| Assessment confidence | High |
In-process execution reduces network attack surface but runs all queries in the same Python process—no isolation between queries or tenants. Parameterized queries reduce SQL injection risk; validate input handling in your implementation. No disclosed vulnerability history in provided data; review ClickHouse CVE history separately. File I/O from untrusted sources (S3, remote DBs) requires same vetting as direct network access.
Alternatives to consider
DuckDB
Lightweight embedded SQL engine with C++ backend and Python bindings. Comparable performance for OLAP, native Parquet/CSV support, slightly smaller footprint. No pandas-compatibility layer; requires SQL knowledge.
Polars
GPU-capable dataframe library written in Rust with Python bindings. Faster than pandas for medium-large datasets but requires learning new API (not pandas-compatible). No traditional SQL interface.
ClickHouse Server (Standalone)
Full-featured OLAP database with persistence, clustering, replication. Required for multi-user, distributed, or durable analytics. Higher operational overhead; suitable for production data warehouses.
Build on chdb with DEV.co software developers
chDB brings ClickHouse performance directly into your Python code—no database ops overhead. Start with a quick pip install and explore our pandas-compatible DataStore API.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
chdb FAQ
Can I use chDB for production analytics dashboards?
Does chDB persist data to disk?
What happens if my dataset exceeds available RAM?
Is the DataStore pandas-compatible API fully featured?
From evaluation to production software
Open-source adoption creates integration work. DEV.co supplies the software development services that close the gap between chdb and a running open-source databases system your team can operate.
Ready to Add Embedded Analytics to Your Python App?
chDB brings ClickHouse performance directly into your Python code—no database ops overhead. Start with a quick pip install and explore our pandas-compatible DataStore API.