Powered by Apache Doris

One SQL surface for real-time analytics.

VeloDB Console
SQL
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
-- Last 7 days of live orders — tagged by region & currency
WITH orders AS (
SELECT
o.id,
JSON_EXTRACT(o.meta, '$.region') AS region,
CAST(JSON_UNQUOTE(
JSON_EXTRACT(o.meta, '$.currency')) AS CHAR(3)) AS currency,
o.gmv,
o.created_at,
JSON_EXTRACT(o.meta, '$.payment_status') AS payment_status
FROM orders o
WHERE o.created_at >= NOW() - INTERVAL 7 DAY
)
-- Compare each region to the same day a week ago
SELECT
region,
SUM(gmv) AS gmv,
LAG(SUM(gmv), 7) OVER w AS gmv_7d_ago,
-- Week-over-week % — the "EU GMV down 12%" headline
ROUND(100 * (SUM(gmv) - LAG(SUM(gmv), 7) OVER w)
/ NULLIF(LAG(SUM(gmv), 7) OVER w, 0), 2) AS gmv_delta_pct
FROM orders o
JOIN mv_checkout_facts_5m f ON f.order_id = o.id
GROUP BY region
WINDOW w AS (PARTITION BY region ORDER BY DATE(created_at))
ORDER BY gmv DESC;
Why did revenue dip in Europe?
EU GMV down 12%
vs prior 7 days
Payment failures up 4.8%
vs prior 7 days
GMV (EU)
$18.7M
-12.0%
Payment Fail Rate (EU)
4.8%
+4.8%
Orders (EU)
312K
-8.6%
GMV by Region (vs prior 7 days)
GMV (Last 7 Days) GMV (Prior 7 Days)
$40M$30M$20M$10M$0MNorthAmerica-12%EuropeAsiaPacificLatinAmericaOther
Checkout Funnel (EU)
vs prior 7 days
Sessions
Add to Cart
Initiate Checkout
Payment Successful
2.4M-6.2%
634K-7.1%
384K-6.8%
293K-12.3%
Results sampled in real time

Trusted in production by teams at

Xiaomi
ByteDance
Tencent
Meituan
JD.com
NetEase
Lenovo
Cisco
Samsung
Pinduoduo
Kuaishou
Vivo
OPPO
Bilibili
Xiaomi
ByteDance
Tencent
Meituan
JD.com
NetEase
Lenovo
Cisco
Samsung
Pinduoduo
Kuaishou
Vivo
OPPO
Bilibili
Why VeloDB

Built for the workloads that
actually break databases.

01 · Performance

Performance under real-world conditions

Sub-second latency under concurrency, heavy updates, and complex joins — all at once.

Most databases benchmark on clean, single-table scans. Real workloads apply three pressures at the same time: thousands of concurrent users, data that changes by the hour, and multi-table joins. VeloDB is engineered to hold sub-second latency through all three, so dashboards, data products, and AI apps stay fast as load grows.

Diagram: concurrency, freshness, and complexity pressures converging into the VeloDB engine while p99 latency stays flat and under one second as load rises.
02 · Unified

Unified engine for analytics, search, and AI retrieval

One engine for every data type, queried in standard SQL.

Structured tables, semi-structured JSON, full-text, and vector embeddings live in one engine and answer to a single SQL statement. You retire the separate search cluster and the standalone vector database, and the pipelines that kept them in sync go away with them. Engineers and AI agents query the same system through the same SQL.

Diagram: one SQL statement combining structured filters, JSON path access, full-text BM25, and vector search in a single VeloDB query — replacing a search cluster, a vector database, and the ETL between them.
03 · Cost

Cost-efficient by design

Lower total cost from the architecture up.

Most analytics spend comes from running and syncing many systems and paying for idle capacity. VeloDB removes both. One engine replaces the search cluster, vector store, and the Redis and ETL layers around them, using built-in caching and materialized views instead. VeloDB Cloud decouples storage from compute, so compute scales elastically, and bursty agent workloads incur costs only while they run. Doris adds columnar ZSTD compression and tiered object storage that cuts storage costs as well.

Before-and-after diagram: five separate systems (OLAP, search cluster, vector DB, Redis, ETL) plus idle compute collapsing into one VeloDB engine with elastic compute that scales to zero — about 60% lower total cost of ownership.
04 · Open

Open by default

Truly open, with full compatibility with open-source Apache Doris.

VeloDB is built on Apache Doris and stays fully compatible with it. You get the same SQL, the same MySQL wire protocol, and the same connectors as the open-source project, so everything you build on Apache Doris runs on VeloDB unchanged and moves back just as easily. VeloDB also supports integration with open catalogs such as Polaris and Unity, and open table formats like Iceberg, Hudi, Delta, and Paimon.

Diagram: VeloDB and Apache Doris joined by a two-way arrow (same SQL, same MySQL wire protocol, same connectors), with spokes to open table formats (Iceberg, Hudi, Delta, Paimon) and open catalogs (Polaris, Unity).

One engine for analytics,
search, and AI context.

Open source, runs in your cloud, proven in production.

Ingest
Streaming
Kafka, Pulsar
Lakehouse Tables
Iceberg, Hudi, Delta
Logs & Events
ClickHouse, OpenTelemetry
App Data / CDC
Databases, SaaS
Vectors & Documents
Files, APIs, Embeddings
VeloDB
Unified Analytical Engine
SQL
SEARCH
VECTORS
AGGREGATE
UNIFIED DATA STACK
Columnar · Vectorized · Disaggregated
DORIS CORE
MPP Execution · CBO · High Concurrency
Serve
Analytics
BI, Dashboards
Search
Keyword, Hybrid
AI Context
RAG, Embeddings
Applications
Real-time APIs
Data Products
Sharing & Monetization
Deploy Anywhere
AWS
GCP
Azure
Kubernetes
On-prem