MyScaleDB
MyScaleDB is an Apache 2.0 licensed vector database built on ClickHouse that adds high-performance vector search and full-text search capabilities while maintaining full SQL compatibility. It targets developers building AI/RAG applications who want familiar SQL syntax instead of custom APIs.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | myscale/MyScaleDB |
| Owner | myscale |
| Primary language | C++ |
| License | Apache-2.0 — OSI-approved |
| Stars | 1k |
| Forks | 72 |
| Open issues | 10 |
| Latest release | myscaledb-v1.8.0 (2024-10-21) |
| Last updated | 2025-02-05 |
| Source | https://github.com/myscale/MyScaleDB |
What MyScaleDB is
A C++20 ClickHouse fork optimizing columnar OLAP architecture for vector operations, metadata filtering, and hybrid text-vector queries. Supports structured, unstructured, vector, and JSON data in a single system with millisecond-scale latency on billion-scale vectors claimed.
Get the MyScaleDB source
Clone the repository and explore it locally.
git clone https://github.com/myscale/MyScaleDB.gitcd MyScaleDB# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Project created March 2024, latest release October 2024, last push February 2025: relatively young but actively maintained. Verify v1.8.0 stability for production before committing.
- Requires operational expertise in ClickHouse (memory, disk, replication, sharding). Self-hosted deployment is non-trivial; consider managed MyScale Cloud unless you have ClickHouse operations expertise.
- SQL compatibility is claimed but MyScaleDB is a fork with custom vector functions; test application migration and query compatibility thoroughly, especially vector-specific operations.
- Performance benchmarks are provided on myscale.github.io/benchmark but are self-published; independent validation recommended before performance-critical decisions.
- Data consistency guarantees, backup/recovery strategies, and disaster recovery SLAs should be validated for your durability requirements, especially if self-hosted.
When to avoid it — and what to weigh
- High-Frequency Transactional Workloads — ClickHouse is an OLAP database optimized for analytical queries, not OLTP. Row-oriented databases (PostgreSQL, MySQL) are better suited for transaction-heavy, low-latency writes.
- Specialized Vector DB Requirements — If you need proprietary vector algorithms (HNSW variants, custom distance metrics) not exposed by MyScaleDB, or require specialized vector DB tuning that ClickHouse does not expose.
- Lightweight Embedded Vector Search — Overhead of running ClickHouse infrastructure may be unnecessary for small-scale vector workloads. Lighter alternatives (Qdrant, Weaviate, local embedding models) may be more cost-effective.
- Minimal DevOps/Infrastructure Expertise — Self-hosted deployment requires managing ClickHouse infrastructure, configuration, tuning, and operational complexity. Managed cloud service (MyScale Cloud) available but introduces vendor dependency.
License & commercial use
Apache License 2.0 is a permissive OSI-approved license allowing commercial use, modification, and distribution with minimal restrictions (requires license notice and attribution).
Apache 2.0 permits commercial use without warranty or liability. However, verify: (1) whether you will use self-hosted (license applies fully) or MyScale Cloud (separate commercial terms apply); (2) whether ClickHouse upstream code carries any additional restrictions; (3) support and SLA requirements are not covered by the license alone.
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 | Moderate |
| DEV.co fit | Good |
| Assessment confidence | Medium |
Apache 2.0 code audit responsibility is yours. ClickHouse has a security history (review CVEs); MyScaleDB inherits this plus custom vector code. Network security (default config allows localhost only) and access control (users.d XML configuration) require proper hardening. Encryption-at-rest, encryption-in-transit, and secret management are not described; verify before production deployment. No mention of security certifications or penetration testing results.
Alternatives to consider
PostgreSQL + pgvector
Row-oriented transactional database with native vector extension. Simpler operational overhead, strong transaction semantics, but slower on large-scale analytical and filtered vector queries vs. MyScaleDB's columnar approach.
Pinecone / Weaviate / Qdrant
Purpose-built vector DBs with simpler APIs and managed cloud options. Specialized performance for vector-only workloads, but lack unified SQL + structured data capabilities and higher cost at scale.
Elasticsearch + Vector Search
Unified full-text and vector search with inverted index strength. Less efficient for structured metadata filtering and SQL joins vs. MyScaleDB's columnar model; different language and tooling ecosystem.
Build on MyScaleDB with DEV.co software developers
Request a technical deep-dive on deployment architecture, performance validation, and production readiness before committing. Compare with PostgreSQL+pgvector, Pinecone, and Weaviate based on your use case.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
MyScaleDB FAQ
Can I migrate from PostgreSQL + pgvector to MyScaleDB?
What is the cost difference between self-hosted and MyScale Cloud?
Does MyScaleDB support real-time updates?
Are there production deployments and reference customers?
Software development & web development with DEV.co
From first prototype to production, DEV.co delivers software development services around tools like MyScaleDB. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across vector databases and beyond.
Evaluate MyScaleDB for Your Vector Workload
Request a technical deep-dive on deployment architecture, performance validation, and production readiness before committing. Compare with PostgreSQL+pgvector, Pinecone, and Weaviate based on your use case.