Work in SQL, not in browser tabs.
Use a Monaco-enhanced editor, example queries, schema context, local query history, shareable query URLs, and result views designed for inspection.
A browser-first SQL workspace
SQL for the data you actually have.
DataDock turns databases, spreadsheets, exports, maps, and matching work into one local SQL workflow. Run one Go process. Open a browser. Keep moving.
go run .
one Go process | embedded tinySQL | no desktop client required for users
datadock / local / spatial
datadock> SELECT district, COUNT(*)
FROM permits
WHERE GEO_WITHIN_BBOX(geometry, ...)
GROUP BY district;
districtcount
Neukoelln184
Wedding129
Prenzlauer Berg87
- LOCAL OR LOCAL-SERVER
- FIVE RELATIONAL ENGINES
- FILES AND MAPS IN SQL
- OPEN SOURCE GO SERVICE
Why DataDock
It starts before your data is tidy.
DataDock is a serious SQL client when the job begins with a database. It is more useful when the job also includes exports, local files, location data, uncertain matches, and a team that should not have to install a desktop IDE.
One desk for local and live systems.
Start in embedded tinySQL, then use managed connections for SQLite, PostgreSQL, MySQL/MariaDB, and Microsoft SQL Server.
Give the file a table before judging it.
Bring in delimited files, office files, structured data, archives, contacts, calendars, databases, and map data without a conversion maze.
Choose the view that answers the question.
Move among datasheets, cards, JSON or XML trees, pivots, profiles, charts, schema graphs, notebooks, maps, and export-ready results.
Reconcile records that almost agree.
Compare customers, articles, addresses, or any two datasets across spellings and formats, then save confirmed links as a queryable crosswalk.
Hand off data without another tool.
Export a table or query result as CSV, TSV, XLSX, JSON, NDJSON, XML, HTML, SQLite, GeoJSON, KML, GPX, or Shapefile ZIP.
One workbench
From unknown input to useful answer.
The shortest path from an uncooperative export to a useful decision should not require a new desktop client, spreadsheet cleanup, and a separate GIS tool.
Bring it in.
Import a file, open a local table, connect a database, or load map and routing data.
Interrogate it.
Browse the shape, write SQL, inspect the schema, and turn results into the view that makes the anomaly obvious.
Prove it.
Use import provenance, quality reports, matching review, local audit records, and read-only modes when control matters.
Hand it off.
Export the result, migrate a table, share the query URL, or package a repeatable read-only pipeline.
Sources
The database is only one kind of input.
Keep a normal database workflow, then add the real-world inputs that normally force a context switch: exports, files, locations, tiles, and routing graphs.
Query the engines your team already runs.
Every browser session can select its active connection while the local workspace stays available for imported data and portable work.
- Embedded tinySQL
- SQLite
- PostgreSQL
- MySQL and MariaDB
- Microsoft SQL Server
- Cross-connection table migration
From common exports to unusual source files.
Normalize practical file formats into queryable tables. Columnar and database artifacts can remain deliberate manifests when no row decoder is bundled.
- CSV, TSV, XLSX, SQLite
- JSON, NDJSON, YAML, XML, HTML tables
- MessagePack, CBOR, BSON
- iCalendar and vCard
- Parquet, Arrow, Feather, DuckDB manifests
- Optional watched import directory
Keep spatial work inside the query loop.
Map files become SQL tables with geometry columns. Tiles stay local, and routing analysis returns GeoJSON ready for visual inspection or export.
- GeoJSON, GeoPackage, GPX, KML
- OSM XML and OSM PBF
- Shapefile ZIP, MBTiles, PMTiles v3
- TileJSON and XYZ tile endpoints
- Shortest path and reachable area analysis
- Geometry, bounds, and quality reports
Use cases
Not just for broken data.
Use DataDock for routine database work, clean analytical datasets, local operational tooling, map analysis, and the awkward joins that appear between otherwise good systems.
A lighter SQL Server companion.
Run a local or local-server DataDock instance for browsing, SQL, table migration, export, and shared access without requiring every user to install SSMS or a full desktop client.
Give every export a SQL landing zone.
Turn delimited files, spreadsheets, structured records, compact binary formats, calendars, contacts, database files, and map sources into local tables before you join, inspect, or hand them off.
Clean data deserves a good cockpit too.
Explore a well-modeled warehouse extract, profile columns, chart a query, open a map, and export an answer without pretending the data must first be "messy."
Ask location questions in the same SQL session.
Bring GeoJSON or OSM data into local tables, analyze routes and reachability, inspect geometry quality, and hand results off in geographic formats.
Turn probable matches into durable links.
Compare exports or live tables across systems, review the likely matches, and retain approved pairs as crosswalks other queries can trust.
Move a result without another conversion step.
Export a table or result as spreadsheet, database, web, or geographic formats, or stream a one-time table migration between registered relational connections.
Make local work repeatable on purpose.
Use scheduled tinySQL jobs, immutable read-only pipelines, watched local imports, and definition bundles when an answer must be repeatable and inspectable.
Ask for a draft, keep the decision.
Use optional AI for reviewable SQL drafts, independent reviews, result explanations, quality signals, chart specs, and next questions. Nothing runs by default.
Keep shared access explicit.
Roles, maintenance mode, audit logging, encryption options, and Admin-protected snapshots support an intentional local-server deployment.
Operate deliberately
Useful power should stay visible to its operator.
DataDock keeps advanced local capabilities optional, explicit, and bounded so a shared browser workspace does not become an opaque data service.
A data workspace should make the fast path safer, not make the safe path impossible.
ADMIN CONTROLS
Roles, maintenance mode, audit logging, and read-only serving give operators a clear way to limit changes without stopping inspection.
PORTABLE STATE
Admin-protected snapshots use a backend-independent writer/reader format. Restore is intentionally not exposed as an unbounded web endpoint.
ENCRYPTED STORAGE MODES
tinySQL disk, JSON, hybrid, and index modes can encrypt data at rest. Keys come from the environment; storage metadata remains visible.
OPTIONAL AI AND RETRIEVAL
An optional OpenAI-compatible assistant drafts, fixes, optimizes, and reviews SQL for your approval, plus result explanations, quality signals, and follow-up prompts. Local vector search uses bounded, vector-free cache entries and admin-only analytics.
Versioned SQL pipelines run only validated read statements. Their portable bundles exclude credentials, runs, and raw result values; run lineage records structure, timing, status, columns, row count, and statement digests instead.
Choose the fit
Different tools solve different SQL jobs.
DataDock is not a claim to replace every enterprise admin console or driver catalog. It is the practical choice when browser delivery, local files, maps, matching, and a self-hosted workspace matter as much as the connection itself.
| Tool | Best fit | DataDock advantage | Use the other tool when |
|---|---|---|---|
| DataDock | Browser-first SQL work across databases, files, map data, and operational handoffs. | One Go service, no desktop installation for users, imported local data, spatial output, matching, routing, provenance, and portable exports in one workspace. | You need a connector outside its five relational engines or a specialist database-administration workflow. |
| JetBrains DataGrip | Developer-centric desktop SQL IDE with deep introspection, navigation, and refactoring. | DataDock adds a shared web workspace, direct spatial file and tile workflows, entity matching, routing, and embedded local tables for files. | You need DataGrip's broad JDBC support, IDE-grade refactoring, schema diff, or desktop-first developer experience. |
| DBeaver | Broad JDBC/ODBC connectivity across relational, NoSQL, cloud, and analytical platforms. | DataDock removes client setup for browser users and keeps imported files, maps, matching, local query work, and exports together. | You need its wider connector catalog, driver manager, cloud or NoSQL access, or enterprise integrations. |
| Microsoft SSMS | Windows-oriented administration and development for SQL Server and related Microsoft services. | DataDock is a lighter local-server alternative for SQL browsing, export, matching, file integration, and SQL Server table migration. | You need SQL Server-specific administration, execution-plan tuning, backups and restores, Always On, or SSIS/SSAS/SSRS management. |
Start with the small version of the decision
Open the data. Ask the question. Keep the answer moving.
Run DataDock on a workstation or a local server, then give people a browser instead of another installer. The source, quick start, and full capability list are in the repository.