Why This Workbench Exists
In everyday software testing and data engineering, engineers routinely receive files that cannot safely be uploaded to third-party servers: columnar .parquet exports, embedded .sqlite stores, oversized .csv or .jsonl logs, and DevTools .har captures containing live session cookies.
All 12 tools on Boloop Tools operate strictly client-side. Static pages are served from edge cache while file parsing—hyparquet & hyparquet-writer for Parquet, self-hostedsql.js WebAssembly for SQLite 3 queries, and pure TypeScript scanning for CSV/JSONL/HAR—runs inside your own browser tab.
Engineering Principles
- Verifiably offline-capable: After loading any tool page once, disconnect Wi-Fi or inspect Chrome DevTools → Network before dropping a file—zero network requests fire for file inspection or conversion.
- No hidden storage or file telemetry: File names, SQL statements, schemas, and HAR payloads stay in volatile browser memory and vanish when you reload or close the tab.
- Honest workstation handoffs: Every tool page pairs its browser workbench with native CLI equivalents (DuckDB CLI,
sqlite3,jq, Polars) for multi-gigabyte batch jobs.
Explore the author’s main studio site, open-source work, and technical writing on getboloop.com.