Product
8 posts in this category.
Six months of the unified tasking fabric
GRIDSCAN customers were migrated onto the shared tasking fabric in November. What broke, what did not.
Read post →Nineteen years and one roadmap
ORBIS, GRIDSCAN, TIDEWATCH and AGRISENSE are converging onto a single tasking and delivery fabric. Why now.
Read post →The economics of a three-year FIELDKIT deployment
The purchase price of an in-situ node is the smallest part of what it costs. Here is the rest of it.
Read post →ORBIS 4 and inference at the edge
Running models on the payload rather than after downlink changes what is possible, and what is sensible.
Read post →ATLAS is public, and the SDKs are open source
Every ORBIS capability is now available programmatically, with a published OpenAPI specification and a free sandbox.
Read post →Why we run our own ground station
Commercial downlink capacity exists and is competent. We are building our own anyway, and the reason is latency, not cost.
Read post →FIELDKIT 2: what we changed after seven years in the field
The second generation is mostly a list of things that broke, and what we did about each one.
Read post →Ten years of ORBIS
ORBIS 1.0 shipped in May 2010. A decade later, some of that original code is still in production — and that is not an accident.
Read post →