The Forge suite is now a product you can run. Seaglass Control Center™ — one download that installs, configures, and operates the suite. ForgeGIS Studio™ — the operator surface where you see it work: a live map, a pipeline canvas, and a natural-language agent acting on both. Beneath them, the engines: ForgeGIS™, ForgeMind™, and ForgeData™.
Three engines. One surface. One download.
Where you see the Forge suite work — and shape it to your mission.
ForgeGIS computes, ForgeData catalogs, and ForgeMind reasons — but each speaks only libraries and machine protocols. Studio is the browser workspace that unifies them: data loaded through one catalog, raster/vector/mixed pipelines composed on a node canvas and run in batch, and a natural-language agent acting on a live map — the one the operator is looking at, not a copy. Single-user, single-host by design: loopback-bound, air-gap capable, bundled with the suite.
The human-visible layer that makes the Forge suite one product, not three.One download that installs, configures, and operates the Forge suite.
A single installer that is also a living dashboard. One download lays down a private Java runtime and the full Forge suite, makes API-key setup trivial, runs the services, manages data, and lets an operator chat with the agent — all from one window, with no prerequisites on the target machine. For Windows x64; v1.2.0 was the first coordinated suite release.
Built for people who would rather evaluate a running system in minutes than assemble one over an afternoon.Three engines built for each other — surfaced by Studio, delivered by the Control Center.
239 user-facing operations across 11 categories. 237 callable by AI agents through a native MCP server.
ForgeGIS runs raster, hydrology, visibility, spectral, ML, and point-cloud workloads on the GPU through Java-side compute kernels, alongside a large vector and topology surface in pure Java — and exposes 237 of its 239 operations to AI agents through a native Model Context Protocol server. Distributed as pure-Java Maven artifacts with no first-party native code, no GDAL native bindings, and no separate native install step — GPU dispatch is via the JOCL OpenCL bindings (JNI bridge bundled in the JOCL JAR). Release 1.1 adds a non-linear DAG pipeline engine that imports QGIS models and runs branching raster/vector workflows, with the raster data plane GPU-resident end to end.
As of May 2026, the only commercially-supported GPU-accelerated geospatial MCP server we have been able to identify. Watch the unedited 62-operation demonstration vs GDAL — methodology biased against us. →Natural language to validated GPU pipelines — or an honest refusal
The natural-language control plane for ForgeGIS. It compiles a spoken or typed request into a validated, executed pipeline on the GPU-accelerated engine, and refuses by construction when a request cannot be honored correctly. Zero confident-wrong results across 79 conversations and 6,696 validated turns — at roughly 25× lower model cost than an agent loop.
Learn more Forge Suite · Data layerThe data-intelligence layer — ask for data by intent
Cost-aware routing, a portable single-file GeoPackage catalog, and a 49-tool MCP surface that turn thirteen heterogeneous sources into one ranked answer — the best-fit correct dataset, with access cost as the deciding tiebreaker.
Learn moreSeaglass Foundry builds a small number of things, carefully — GPU-accelerated software for technical workloads where speed and correctness both matter. The Forge suite is our geospatial stack for the agent era: ForgeGIS (the GPU-accelerated compute engine), ForgeMind (the GIS Intent Compiler), and ForgeData (the data-intelligence layer) — made one product by ForgeGIS Studio (the operator surface) and delivered by the Seaglass Control Center (one download that installs, configures, and operates the suite). We also ship SwingToPDF™ (vector PDF output from Java Swing), and maintain Worldwind Reforged, a community modernization of NASA's WorldWind released as open source under our Cannonforge banner.
Our standalone developer library, alongside the Forge suite.
Worldwind Reforged is our modernization of NASA's WorldWind — not a commercial product we ship, but a community contribution maintained under our Cannonforge banner. We modernized the toolkit for Java 17+, shader-based rendering, and a clean Maven build, then released the work openly so the WorldWind community can keep building on it.
A modernized Java 17+ build of NASA WorldWind, given back to the community
Shader-based rendering, GPU-accelerated surface shapes, full Maven build, and backwards compatibility with the original WorldWind Java API — a drop-in modernization for anyone still building on WorldWind. Source and releases on GitHub under our Cannonforge banner.
Learn moreLicensing questions, evaluation access, partnership inquiries — we read every email.
rich@seaglassfoundry.com