KX and Row64

KX makes kdb+ and KDB-X, time-series and vector database technology that capital markets firms have long relied on for high-volume data and fast analytics, on-premises or in the cloud. Row64 adds a live command center for the trading, payments and risk operations teams who need to act on that data as it changes, without writing q.

Reviewed November 2026

Keep KX for

  • High-volume time series.

    Years of tick and transaction data, stored and queried at very high speed.

  • Quant research in q.

    Quants and engineers model and query data directly in q and KDB-X.

  • Vector and time series together.

    KDB-X combines vector search and time series in one engine.

Add Row64 for

  • A live view for people who don't write q.

    Operations, risk and support teams work from a live command center built in Row64 Studio.

  • Risk controls moved mid-attack.

    Rules on live data raise risk scores, open tickets and send REST calls the moment a pattern appears, and the result comes back live.

  • More desks, same license.

    Row64 is priced per server, so adding trading, payments or risk desks doesn't raise its license cost.

In practice

Which merchants are being card-tested right now?

With Row64, a payments team running KX can spot a card-testing attack across thousands of merchants while it is still running.

Just after midnight, small declined authorizations jump at 140 online merchants, most of them behind one gateway. Row64 flags the pattern, raises those merchants' risk scores through a REST call and opens a ticket for the fraud desk. The analyst on shift opens the worst merchant, watches its declines on the map and in the transaction table, and decides whether to block the card range.

In the morning, the full history is in kdb+ for the quants to study.

Row64 Fraud Watch view with flagged transactions on a US map, fraud by category, transactions by risk and a detailed transaction table, updating as transactions arrive.

How they work together

Keep kdb+ for the analysis. Add a screen to act from.

01

KX keeps the history.

kdb+ and KDB-X stay where your quants and engineers store and query time series in q.

02

Row64 reads the live feeds.

Row64 reads streams published over Kafka or MQTT, next to warehouse and database data.

03

Row64 acts on it.

Alerts, tickets and REST calls go out automatically or from an operator's screen, and the result comes back live.