AVE.ai evaluated ClickHouse and Snowflake for real-time token analytics, then chose VeloDB. It now sustains close to 1,000 QPS with data landing in under 5 seconds.
Real-Time Analytics
Sub-second dashboards and data products on petabytes of data at any concurrency
Data Warehousing
Sub-second analytics on open lakehouse formats with no vendor lock-in
Observability in the AI Era
The most cost-effective alternative to Elasticsearch observability
Context Engineering
Hybrid search and fresh context for RAG, agents, and LLMs
Trading venues, payment platforms, and crypto businesses run on data that changes by the second: prices, positions, balances, and risk signals. VeloDB, the real-time analytics and search database from the creators of Apache Doris, serves banking, capital markets, fraud detection, and digital-asset workloads in one engine, built for the concurrency and update pressure financial data brings.
Submit your product and service requirements,
our team will respond within 1 business day.
AVE.ai evaluated ClickHouse and Snowflake for real-time token analytics, then chose VeloDB. It now sustains close to 1,000 QPS with data landing in under 5 seconds.
Advance.AI moved its log system from OpenSearch to VeloDB and unified log analysis with analytics on one engine.
ADIA unified PostgreSQL, TimescaleDB, and a separate analytics tier into VeloDB for its fully automated trading operation.
Powering real-time data for 10,000+ teams
When markets move or tokens launch, three things happen at once: query concurrency spikes, every price and balance update rewrites hot rows, and analytics queries join tables that are changing mid-query. General-purpose OLAP engines slow down at the moment the business needs them most.
Time-series data lands in one store, point lookups run on an OLTP database, and aggregations get their own analytics tier. Every seam adds data movement, drift between copies, and one more system to operate, and each team ends up with its own version of the truth.
Logs and text sit in a search engine while metrics sit in an OLAP store, so teams pay to store the data twice, maintain two query languages, and join across systems to answer one question.
Four ways one engine fits how financial data actually behaves.
Merge-on-write updates keep tables current under heavy writes, so balances, positions, and prices are queryable the moment they change. Point queries reach 30,000 QPS per node, complex joins run distributed across the cluster, and high-concurrency dashboards stay responsive through peaks. ASOF JOIN, available in Doris 4.1, pairs each trade with the latest quote for execution analytics and trade surveillance.
One engine handles streaming market data, aggregations over any window, and OLTP-style entity lookups, so analysts share a single up-to-the-second view instead of reconciling per-team stores. Native CDC ingests from PostgreSQL; Kafka delivers streaming events.
The next use case is a new table, not a new database.
Inverted indexes serve full-text queries next to SQL aggregations, so log search, entity lookup, and metric analysis run on one copy of the data. Doris 4.1 adds BM25 scoring and Elasticsearch-compatible search syntax, with billion-scale vector retrieval for AI workloads.
Deploy as managed cloud, BYOC in your own account, or on-premises for full data residency control. Storage-compute separation scales for market peaks without paying peak capacity all year. VeloDB also queries Iceberg and Paimon tables in place, so lake data joins the analysis without another pipeline.
Pick a workload. Every one runs on the same engine, on the same live data.
ADIA streams L1 market data and trade execution records through Kafka into VeloDB, giving every analyst one consistent, up-to-the-second view of markets, positions, and strategy performance. Story publishing soon.
ADIAAVE.ai runs trading-behavior analytics, volume, large trades, and fraud detection, on the same engine that serves its market analytics. Read here
AVE.aiA top crypto exchange serves 80M+ users on VeloDB at 5,000 peak QPS with P95 latency under 500ms. Story publishing soon.
Crypto exchangeAdvance.AI unified its log system on VeloDB and cut costs by more than 50%. Read here
Advance.AIVeloDB is a real-time analytics and search database from the creators of Apache Doris. One engine handles point lookups, complex joins, high-concurrency aggregations, and full-text and vector search on data that changes by the second.
Fraud scoring needs fresh aggregates and fast entity lookups at the same time. VeloDB ingests transaction streams continuously, keeps aggregates current under heavy updates, and serves point queries at up to 30,000 QPS per node, so decisioning flows read live data instead of a batch from the night before.
Yes. AVE.ai ingests roughly 5,000 records per second from major blockchains with end-to-end latency under 5 seconds, and serves close to 1,000 QPS with P99 under 1 second during peak trading.
Time-series analysis, OLAP aggregations, OLTP-style point lookups, log search, and vector retrieval run in one engine. ADIA consolidated three systems into one; Advance.AI unified log analysis with analytics.
Managed cloud, BYOC in your own cloud account, or on-premises, with storage-compute separation for elastic scaling and full control over data residency.