Locusbench
A team geospatial API workbench for STAC, WMS, WFS, OGC API, ArcGIS services, and GeoJSON with safe requests, spatial rendering, versioned assertions, drift alerts, CI runs, and agent-accessible test tools.
General API clients can send requests but do not make coordinate systems, layers, tiles, features, extents, temporal coverage, geometry validity, or OGC conformance easy to inspect. Quetzly validates a free desktop geospatial client while leaving team collaboration, CI, monitoring, and agent tooling open. Locusbench's product is a spatial contract test system: it preserves request and credential boundaries, renders responses with their declared semantics, distinguishes empty valid results from failures, and versions fixtures and assertions for teams.
The geospatial engineer, platform team, data product owner, or QA lead maintaining spatial APIs and upstream service dependencies.
The 2026 launch validates present developer interest.
Geospatial engineering and QA teams have a concrete protocol-testing job.
The input has several links but moderate grounded convergence.
A clear geospatial developer buyer, a validated desktop primitive, an open team-and-CI gap, and mature spatial standards support a focused commercial workbench.
The market signal is small, generic API clients can expand, protocol breadth creates long-tail complexity, and arbitrary endpoint testing introduces security and data licensing risk.
Discussion
No comments yet — be the first to weigh in.