Who builds it
Driades is built by Carlos Vivar Rios. All of it. Instead of filling this page with job titles nobody holds, here are the five kinds of work it actually splits into. They share one pair of hands and one week. That is the honest part, and it is also why the roadmap stays short and why the things that do ship are finished.
The biologist
Comes from genomics, microscopy and satellite imagery, and keeps asking the question the tool is answering: which of these can you not ask today, and what is stopping you?
Genomics · Microscopy · Remote sensing · Research design
The data engineer
The part that makes a continent-scale archive cost you the tiles in view: range requests, cloud-native formats, and refusing to build an import step.
PMTiles · COG · GeoParquet · Zarr · DuckDB · SPARQL
The coder
CRDTs, peer-to-peer sync and the unglamorous work of making an edit from a phone in a forest merge cleanly with one from a laptop that was offline.
TypeScript · CRDTs · WebRTC · MapLibre · WASM
The artist
The grove in the logo, the contour lines behind the map, the colour a cursor takes when somebody joins. Drawn, not templated.
Identity · Interface · Cartography · Motion
The product one
The hat that says no. Decides what ships, what waits, and which feature would quietly cost the project the thing that makes it worth using.
Scope · Pricing · Roadmap · Saying no
Five hats is still one point of view. The board is where that gets corrected: people who know a field far better than the person building the tool, and who are willing to say when a design is wrong.
