What do you want to map?
Each dot on the map will be one of these. We pull everything your files say about each one into its own note, so dots that look alike end up near each other.
About the business Optional. Skip it if your files explain themselves.
Add your files and say what each one is
Add each export, folder, inbox or website you want on the map, then write a line about what's in it. That line tells us how to read the file, for example which column is the customer. Nothing is sent anywhere until you press Build.
Sources
Building your map…
Your datamap
Scroll to zoom, drag to move around, and hover over a dot to see what it is. Use the search box on the map to find a word.
For the team: what this page hands to the pipeline
When PIPELINE_URL is set at the top of the script, Build sends POST {PIPELINE_URL}/jobs as multipart form data: a manifest field holding this JSON, plus one files part per uploaded file, named {source id}/{path}. The server returns {"job_id"}. The page then polls GET {PIPELINE_URL}/jobs/{job_id}, which returns {"stage": "okf" | "embed" | "cluster" | "name" | "render", "status": "running" | "done" | "failed", "map_url", "regions": [{"name", "count"}]}. Run uv run datamap serve from the repository root and the page connects to the pipeline on its own; opened any other way, it runs in demo mode.