LABORATORY DASHBOARD
// Choose the right sandbox before you spend energy exploring
Labs are for hands-on experiments after reading is not enough. Pick the module that matches your current input, expected compute cost, and the kind of feedback you want to get quickly.
Tables and queries point to data labs. Text and notes fit writing or translation workflows. Media files belong in FFmpeg.
DuckDB, FFmpeg, and translation can push CPU harder than Markdown or graph browsing on smaller machines.
If you are exploring, begin with SQL Lab, DuckDB, or Markdown Playground before moving into heavier pipelines.
Good defaults for trust, performance expectations, and local-first workflows.
Most work happens locally on your device instead of a remote backend.
Analytical, media, and inference labs can feel heavier on older laptops.
Some modules get better immediately when you already have a file, note, or query goal.
Choose the intent first, then compare the matching modules
Grouping by intent makes the page easier to scan than one long undifferentiated list.
Data Systems
Use these labs when you want relational practice, analytical querying, or fast dataset exploration in the browser.
SQL LAB.EXE
Persistent PostgreSQL WASM node for relational database exploration and repeatable SQL drills.
OLAP LAB.EXE
OLAP engine powered by DuckDB-WASM for local CSV and Parquet exploration with fast analytical SQL.
Writing & Knowledge
Choose these modules when your workflow starts from notes, articles, docs, or semantic browsing instead of raw tables.
BLOG NETWORKS.EXE
Interactive graph view for browsing semantic relationships across the blog archive and adjacent ideas.
MARKDOWN PLAYGROUND.EXE
Live Markdown editor with preview-first writing, quick formatting loops, and a technical notebook feel.
Media Processing
Use this track when the job is conversion, compression, or browser-side signal processing for media assets.
AI Utilities
Open these labs when you want fast practical AI help without sending content to a remote service.