Show HN: DataKit, your all in browser data studio is open source now
Show HN (score: 6)Description
GitHub: https://github.com/datakitpage/datakit Live demo: https://datakit.page
DataKit is a browser-based data analysis platform that processes multi-gigabyte files (CSV, Parquet, JSON, Excel) entirely client-side using DuckDB-WASM. Your data never leaves your browser.
What it does: • Process large files (tested up to 20GB) without any server • Full SQL interface powered by DuckDB compiled to WebAssembly • Python notebooks via Pyodide for data science workflows • Connect to remote sources (PostgreSQL, MotherDuck, S3) with optional proxy • AI assistant that only sees column schemas, not actual data
I was done with having to choose between cloud tools and heavy local installations. I wanted something that just works in a browser tab but has real power.
It's AGPL licensed with commercial licenses available for enterprises.
I've been building this solo as a side project for the past few months. Would love your feedback on: - Performance bottlenecks you encounter - Features you'd need for your workflows - The architecture decisions (all client-side vs hybrid)
More from Show
Show HN: Control Claude permissions using a cloud-based decision table UI
Show HN: Control Claude permissions using a cloud-based decision table UI We’ve been building visual rule engines (clear interfaces + API endpoints that help map input data to a large number of outcomes) for a while and had the fun idea lately to see what happens when we use our decision table UI with Claude’s PreToolUse hook.<p>The result is a surprisingly useful policy/gating layer– these tables let your team:<p>- Write multi-factor, exception-friendly policies (e.g. deny rm -rf / when --force; allow cleanup only in node_modules; ask on network calls like curl/wget; block kubectl delete or SQL DROP, each with a clear reason)<p>- Roll out policy changes instantly (mid-run, flip a risky operation from allow → ask; the next attempt across devs and agents is gated immediately– no git pull, agent restart, or coordination)<p>- Adopt lightweight governance that is somewhat agent agnostic and survives churn (MCP/skills/etc)- just add columns/rules as new tools and metadata show up<p>- Get a quick central utility to understand which tools are being used, which tools get blocked most often, and why
Show HN: Claude Code Scheduler
Show HN: Claude Code Scheduler I found myself frequently wanting to schedule tasks in Claude Code (both one-time and recurring) so I built a CC plugin to help with that.<p>To install: /plugin marketplace add jshchnz/claude-code-scheduler /plugin install scheduler@claude-code-scheduler<p>Then just tell Claude what you want (some examples):<p>Every Wednesday at 3am find dead code: unused functions, unreachable branches, commented-out code, and unused imports. List by file with line numbers.<p>Schedule a code review every weekday at 9am. Review commits from the last 24 hours, check for bugs, security issues, error handling gaps, and code that needs comments. Summarize with file:line references.
Show HN: Webctl – Browser automation for agents based on CLI instead of MCP
Show HN: Webctl – Browser automation for agents based on CLI instead of MCP
Show HN: Tsonic – A TypeScript to native code compiler via CLR and NativeAOT
Show HN: Tsonic – A TypeScript to native code compiler via CLR and NativeAOT
No other tools from this source yet.