ChronGeo Studio

The room where the data becomes a decision.

ChronGeo is the API-first spatial-time platform. Studio is the applications layer on top of it — one common picture for what moves on the water, in the air, and overhead, with the time dimension attached and the convergences called out.

Three domains · one pipeline Decision support · never transacts
Concept render
ZONE · ANCHORAGE A MV · SURFACE ACFT · AIR SAT · TLE PASS CONVERGENCE T+4h
Common Operating Picture — ConceptChronGeo Studio
The difference

A map is a noun. Studio is a verb.

What a map gives you

Position, and your own inference

  • Where each thing was when it last reported.
  • One domain at a time — a vessel tool, a flight tool, a satellite tool.
  • Now, or a static export of some earlier now.
  • A picture you read, then re-type into the system that actually does the work.
  • Provenance in a footnote, if at all.
What Studio gives you

Trajectory, intersection, and the cost of it

  • Where each thing is heading, and what it meets when it gets there.
  • Surface, air and orbit in one shell, off one canonical record.
  • A timeline you can scrub — the same picture at any point you choose.
  • An API and an agent surface, so the answer moves without a human retyping it.
  • A licensing manifest inside the product that names every source on screen.
3
Domains through one canonical record — vessel, aircraft, satellite.
6
Live ingest paths that need no paid contract, including your own AIS tower.
10
Read-only tools exposed to agents over MCP. None of them writes.
0
Endpoints that transact. Studio recommends; your systems commit.
1
Versioned workspace grammar — the deterministic spec the AI writes against.
Capabilities

Seven things it does, and what each one is for.

Each capability gets one sentence and three claims — no more. If something is on the roadmap rather than in the product, the panel says so.

One shell that holds what moves on the water, in the air and overhead — because the thing you are worried about is rarely confined to one of them.

  • 01

    Vessels, aircraft and satellites land in the same canonical record, so a cohort can span domains instead of forcing three tools side by side.

  • 02

    Layer manager, dossier, alert queue and omnibar in a four-zone shell — the working surface, not a dashboard you look at.

  • 03

    Density, tracks, zones and ports render as real map layers, so the picture scales past the point where individual pins stop being readable.

Status — in the product.
The discipline

What it refuses to do.

These are constraints in the code, not intentions in a policy document. They are the reason a buyer in a regulated seat can put this in front of an auditor.

It does not transact

Studio is decision support. There is no endpoint that orders, buys, or commits, and the request-for-quote path is a deliberately disabled stub. Recommendations leave Studio; obligations are created in your systems.

It does not claim to be an ECDIS

It supports voyage planning under SOLAS V/34 and exports a route the navigation system can read. It is a back-of-bridge planning and review tool. Anyone telling you a web application is a type-approved ECDIS is selling you something else.

It does not use data it is not licensed to use

Feeds are free-first and licensing-clean. Sources whose terms do not permit this use are excluded by name, not quietly included and hoped over. Attribution obligations are rendered in the interface, driven by a manifest the API serves.

It does not present placeholders as measurements

Where a value is indicative — an unpriced input, a factor still under revision — it is marked in the API response and on screen. A number you cannot trace is a number you should not act on.

It does not let an agent write

The agent surface is read-only by construction. An assistant can compose a view, query the picture, and explain what it found. It cannot change state, and there is no tool available to it that could.

It does not pass concept art off as product

Every render on this site is labelled a concept visualization, including the one at the top of this page. When a capability is on the roadmap rather than in the build, we say roadmap.

Where it sits

ChronGeo is the data. Studio is the decision.

ChronGeo ingests, models and forecasts trajectories from the sources you already run, and exposes convergence as a queryable signal. Studio is what an operator works in — and the marketplace surface for tools built on the same data.

If your team already has a control tower, take the API and leave Studio alone. If it does not, Studio is the one we built so you do not have to.

Bring your own sources

Your own AIS receiver is a first-class feed, not an integration project — the same path the public feeds use. Nothing about Studio assumes the data has to come from us.

Early-stage, and specific about it

Studio is in preview and access is arranged directly. Ask us what is built, and you will get the list — including the parts that are not.

Request a briefing

See it against your own operating picture.

We will walk Studio through your environment — what it shows today, what it would need from you, and what is still on the roadmap.