Show HN: CSV GB+ by Data.olllo – Open and Process CSVs Locally
Most spreadsheet apps choke on big files. Coding in pandas or Polars works—but not everyone wants to write scripts just to filter or merge CSVs. CSV GB+ gives you a fast, point-and-click interface built on dual backends (memory-optimized or disk-backed) so you can process huge datasets offline.
Key Features: Handles massive CSVs with ease — merge, split, dedup, filter, batch export
Smart engine switch: disk-based "V Core" or RAM-based "P Core"
All processing is offline – no data upload or telemetry
Supports CSV, XLSX, JSON, DBF, Parquet and more
Designed for data pros, students, and privacy-conscious users
Register for 7-days free to pro try, pro versions remove row limits and unlock full features. I’m a solo dev building Data.olllo as a serious alternative to heavy coding or bloated enterprise tools.
Download for Windows: https://apps.microsoft.com/detail/9PFR86LCQPGS
User Guide: https://olllo.top/articles/article-0-Data.olllo-UserGuide
Would love feedback! I’m actively improving it based on real use cases.
I created Buckaroo to provide a better table viewing experience inside of notebooks. I also built a low code UI and auto cleaning to expedite the wrote data cleaning tasks that take up a large portion of data analysis. Autocleaning is heuristically powered - no LLMs, so it's fast and your data stays local. You can apply different autocleaning strategies and visually inspect the results. When you are happy with the cleaning, you can copy and paste the python code as a reusable function.
All of this is open source, and its extendable/customizable.
Here's a video walking through autocleaning and how to extend it https://youtu.be/A-GKVsqTLMI
Here's the repo: https://github.com/paddymul/buckaroo
It‘s interesting to research how capable applications like Lotus123 have been even on low resolutions like 800x600 pixel compared to today’s standard
What are you using for processing (polars)?
Marketing note: I'm sure you're proud of P Core/V Core, but that doesn't matter to your users, it's an implementation detail. At a maximum I'd write "intelligent execution that scales from small files to large files".
As an implementation note, I would make it simple to operate on just the first 1000 (10k or 100k) rows so responses are super quick, then once the users are happy about the transform, make it a single click to operate on the entire file with a time estimate.
Another feature I'd like in this vein is execute on a small subset, then if you find an error with a larger subset, try to reduce the larger subset to a small quick to reproduce version. Especially for deduping.
Speaking personally, "intelligent execution that scales from small files to large files" sounds like marketing buzz that could mean absolutely nothing. I like that it mentions specifically switching between RAM and disk-powered engines, because that suggests it's not just marketing speak, but was actually engineered. Maybe P vs V Core is not the best way to market it, but I think it's worth mentioning that design.
https://graydon2.dreamwidth.org/193447.html