An extensible, state of the art columnar file format. Formerly at @spiraldb, now a Linux Foundation project (@LFAIDataFdn). Apache-2.0

Github
Joined May 2025
Vortex support in the HF Dataset Viewer coming soon ! 😁
1
3
91
fast, distributed determinism is hard. really cool work from our friends at @datologyai! (also... integrates with @vortexdotdev 👀)
At @datologyai we run thousands of data experiments. Two things keep biting us: - Same run on 16 vs 8 GPUs → different evals - Every pipeline change → re-materialize the dataset Introducing Zephon, the data loader we built to process data on the fly, deterministically. 🧵
7
42
1,320
vortex retweeted
We've always called it software engineering, but we've actually been builder...gineers. In civil engineering, aerospace, or architecture, the people who do the engineering and the people who do the building are obviously different. But in software, we collapsed them into the same role. With agents, we're finally separating the jobs. We're going to specify and encode more upfront, add more guardrails, and design architectures that bias agents toward success. In many ways, we're finally starting to look like actual engineers.
18
24
6
266
10,075
9ms point lookups without running your own database in every region That's what @goldskyio built with Tigris, @vortexdotdev, and SlateDB Get our side of the story 👇
2
3
9
762
vortex retweeted
Cayenne stores data in @vortexdotdev, which computes directly on compressed data. Pretty cool! Many operations skip decompression. And when a decode is needed, bytes land straight in Arrow arrays with no intermediate copy. spice.ai/blog/vortex-at-spic…
1
4
279
More like Hugging Fast 🚀🚀 @vortexdotdev
Datasets 5.1 is out, largely carried by @b_azarkhalili ! New formats - Vortex, cc @Robert3005 - Harbor for RL environments, cc @adithya_s_k - Not one but five (!!) Bio molecules and proteins formats 🧬, cc @cgeorgiaw
1
2
13
770
The DAVE stack: the age of domain-optimized analytical databases on Datafusion, Arrow, and Vortex, Embedded sequenceandsilicon.substack.…
1
10
52
2,095
vortex retweeted
AI agents and real-time apps increasingly need analytical answers from data that was written seconds ago. Pointing those queries straight at an operational database slows production and widens security risk. The usual alternative, an ETL pipeline into a warehouse, is costly to operate and can lead to data that's stale by hours or days. Spice 2.0 offers a new approach, and is now available. It stands up a sandboxed analytic replica beside your operational store and keeps it current with high-throughput change data capture directly from those sources. You point Spice at a database and start running analytical queries in minutes, while production never carries the analytical load. High-throughput CDC replication is complemented by the rest of the 2.0 platform: multi-node distributed compute on @ApacheDataFusio Ballista for petabyte-scale queries, Spice Cayenne columnar acceleration on the open @vortexdotdev format, a cluster-sidecar architecture that pairs isolated local sidecars with a shared cluster, and enterprise security enforced in the engine with OIDC, Cedar policies, PII masking, and mTLS. "Spice is the data plane behind Summation. Every connector we ship, from Snowflake to a generic REST-as-a-table, collapses into one SQL surface, which is what makes our AI agents portable across a customer's stack. 2.0's distributed query takes the scaling concern off the table." -Ramachandra Ramarathinam, CTO at @summation   It's open source, portable, scalable, and fast. Read the launch blog for more details: hubs.ly/Q04p5pFw0 And, check out the thread ⬇️ for breakdowns of the major features in 2.0.
6
6
2
11
2,521
so cool to see another blazing fast database built on vortex!
Just announced at Interrupt! SmithDB. Agent traces have outgrown the databases built to hold them. That’s why we built SmithDB, a purpose-built distributed database for agent observability. Read the announcement from Co-Founder @ankush_gola11 → langchain.com/blog/introduci…
6
32
71,096
We leveraged two amazing open source projects when building SmithDB. One is @ApacheDataFusio: an extensible Rust based query engine. We built custom execution plans specifically tuned for our workloads and storage backend, and DataFusion made it straightforward to plumb everything together. The other is @vortexdotdev: an extensible file format that allows you to build custom layouts with specific encoding and chunking strategies for different columns. I would highly recommend checking out both of these projects if you're interested in modern data systems.
We built SmithDB: the database purpose built for agent observability workloads that now powers many parts of LangSmith. Agent observability presents a challenging data problem. Agent traces can contain tens of thousands of intermediate spans and large, unbounded payloads. These characteristics are a direct result of agents running for longer time horizons and LLM context window sizes growing. Traditional data infrastructure was not built to handle the complexities associated with storing and querying this data. SmithDB brings LangSmith up to 12x performance improvements across access patterns most important for agent observability. I’ve been working on SmithDB directly with an amazing team over the past few months, and I’m incredibly proud of the results we’re seeing. I wrote a bit more about the story and engineering challenges behind SmithDB in this blog. Additionally, if you’re a systems engineer interested in building the future of agent observability, please reach out!
2
18
3
105
18,274
vortex retweeted
The Research Behind Modern Data Compression & @vortexdotdev When we chose Vortex as the storage layer for Spice Cayenne (the data accelerator engine in Spice), we were betting on decades of database research finally reaching production-ready maturity. Here's the research behind Vortex: 📄 BtrBlocks (SIGMOD 2023) - The core algorithm from the Technical University of Munich. Cascading multiple lightweight encodings outperforms monolithic compression. Optimize for decompression speed, not just compression ratio. 📄 FastLanes (VLDB 2023) - Hardware-friendly integer compression. Structures bit-packing to maximize SIMD utilization across AVX-512, AVX2, and ARM NEON. Near-memory-bandwidth decompression. 📄 FSST (VLDB 2020) - Fast Static Symbol Table for strings. Near-LZ4 ratios at 5-10× faster decompression. Critical for string-heavy columns. 📄 ALP (CWI Amsterdam) - Adaptive Lossless floating-Point compression. Exploits real-world float patterns (prices with 2 decimals, sensor readings with limited precision). 📄 MonetDB/X100 + Morsel-Driven Parallelism - Foundations for vectorized, NUMA-aware query execution that Vortex builds on. The result? Compression that is tailored to your data: • Integers via FastLanes bit-packing • Floats via ALP adaptive encoding • Strings via FSST symbol tables • Timestamps via delta encoding • Sorted columns via run-length encoding Why does this matter for production systems? 1️⃣ Query performance scales with decompression speed. Focus on decode performance translates directly to faster queries. 2️⃣ Automatic encoding selection means zero configuration. The algorithm samples your data and picks optimal strategies per column. 3️⃣ SIMD acceleration is baked in. FastLanes was designed for vectorized, hardware accelerated execution from day one. 4️⃣ Zero-copy Arrow access. Data decompresses directly to Arrow arrays with no intermediate copies. Vortex is now a Linux Foundation AI & Data project, and researchers are building on it (Anyblox, F3). You get SOTA research in production systems. The future of data storage is exciting. To learn more about our Vortex implementation, check out the blog: hubs.ly/Q04bGfvf0 #datafusion #ai #data #vortex #spiceai #arrow #parquet
1
6
415
Connor Tsui & I just merged a first cut of TurboQuant into @vortexdotdev , already validated on production embeddings 🚀🚀🚀
1
5
2
12
2,434
vortex retweeted
CASE-WHEN support coming to @vortexdotdev Guess I'm a Vortex contributor now!
1
8
407
vortex retweeted
🌪️ Why LF Vortex for hot data? @ApacheParquet great compression, slow decode @ApacheArrow instant decode, no compression Vortex: encoding-efficient compression with SIMD decode to Arrow 80% of Parquet's compression, 10x faster decode
1
5
1
11
832
Happy to share that I've been nominated to the @vortexdotdev Technical Steering Committee! It's been fun and productive switching to Vortex from Parquet as our storage format at Polar Signals and I'm excited to continue contributing to the Vortex project.
1
1
4
363
Super cool, they forked @DeltaLakeOSS to replace Parquet (for data) with Vortex and JSON (for metadata) with Vortex. Huge performance gains! Maybe we should upstream this one 😁 @vortexdotdev
🧊 New on the Polar Signals Blog — Our Delta Lake Fork Purpose-built for our continuous profiling product. In our latest post, we walk through how Delta Lake works, and the changes we've made to improve performance for our product. 👉 Read the full post: buff.ly/KwHINtO
4
5
65
7,801
So cool!! Polar Signals reduced query runtimes by 70% switching from Parquet to Vortex 🤯🚀
We completed a major project to switch our storage file format from Parquet to Vortex 🌪️ resulting in 70% average query performance improvement across the board 🚀 Learn more about how rethinking interface-imposed limitations unlocked these gains in our latest blog post 👇
3
24
2,428
We completed a major project to switch our storage file format from Parquet to Vortex 🌪️ resulting in 70% average query performance improvement across the board 🚀 Learn more about how rethinking interface-imposed limitations unlocked these gains in our latest blog post 👇
2
7
2
27
3,753