Hex vs Fulcrum
Side-by-side trajectory, velocity, and editorial themes.
Hex is remaking its notebook into an agent that both uses and plugs into MCP
Hex is converting its analytics notebook into an AI agent platform. It now runs as an MCP client, is invocable from Codex, and ships generative data apps built from prompts, while keeping its model roster current with Kimi K2.7 and Fable 5 and giving admins default-model and branding controls. Integration and governance work — a Figma connector, AWS IAM-role support, signed embedding — rounds out the core.
The arc points at Hex as connective agent infrastructure: consuming external context and tools via MCP, distributing itself into other agent surfaces like Codex, and letting analysts assemble apps and dashboards from prompts. Expect the agent, rather than the notebook grid, to become the primary interface, with model choice and governance layered on top.
Likely next steps deepen the agent's tool-use over MCP connections and push generative apps further toward production embedding and governance controls.
Fulcrum keeps hardening field GIS capture on a steady weekly cadence.
Fulcrum ships on a predictable weekly rhythm across web, iOS, and Android, and the work is concentrated on field mapping and ArcGIS interoperability. Recent releases center on map annotation, geometry rendering, and offline reliability rather than new product surface.
The arc is incremental hardening of the mobile GIS workflow — WMS and ArcGIS connectivity fixes, map scale bars, background GPS tracking — punctuated by occasional field-UX additions like sketching on a captured map. It reads as a mature product optimizing its core rather than changing direction.
Expect the weekly web and mobile cadence to continue, with more map-annotation and ArcGIS-integration refinements. Nothing in these entries points to a larger platform shift.
See more alternatives to Hex →
See more alternatives to Fulcrum →