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.
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.
Vessels, aircraft and satellites land in the same canonical record, so a cohort can span domains instead of forcing three tools side by side.
Layer manager, dossier, alert queue and omnibar in a four-zone shell — the working surface, not a dashboard you look at.
Density, tracks, zones and ports render as real map layers, so the picture scales past the point where individual pins stop being readable.
The time dimension is the product, not a filter bolted onto it — you can put the picture back to any moment and watch it move.
A timeline you scrub, rather than a static export of whatever "now" was when the report ran.
Historical playback runs off a banked archive, so the past is reproducible instead of reassembled from a live feed.
A saved workspace carries its viewport, layers, filters and time position together — send someone the moment, not a screenshot of it.
Convergence is the signal: two things whose paths are about to meet, or one thing that stopped behaving like itself.
Zone entry and exit, and port calls, are detected rather than eyeballed — each event carries the crossing that produced it.
Proximity between two vessels, and gaps where a track should have reported and did not, surface as their own event types.
Events are queryable and streamable, so they can drive an alert in a system you already run instead of a tab someone has to watch.
Plan the passage, see which zones it crosses, and hand the result to the bridge in a format the bridge already accepts.
Port-to-port routing with legs and the zone crossings each leg incurs, cited back to the boundary that caused them.
RTZ export — a route plan the navigation system reads, produced back-of-bridge for planning and review.
An opt-in weather advisory that flags threshold exceedances along the route rather than pretending to be a forecast service.
A route is a number before it is a line — fuel, deviation, and the regulatory cost that attaches to both.
Ranked bunker plans with the remaining-on-board waterfall and the deviation maths made explicit, not buried.
Emissions and scheme exposure computed from the published methods, with the carbon intensity rating alongside.
Any indicative or placeholder input — a price, a factor — is flagged as such in both the API and the interface.
Knowing where a vessel is going matters less if you do not know who it is.
Sanctions screening against the published list, refreshed from source rather than from a stale internal copy.
A screening result attaches to the entity card, so it travels with the vessel through the rest of the picture.
Screening is a finding surfaced for a human to act on — it does not gate, block, or decide anything on its own.
The answer should be able to leave the screen — an agent or a script should be able to ask what an operator would ask.
An MCP server exposes read-only tools, so an assistant can query the picture directly. No tool in it writes or transacts.
A whole workspace — viewport, layers, filters, alerts, annotations — is a strict-validated, versioned document, which is what makes an AI-composed view reproducible.
Everything the interface does, the REST and streaming API does first. The interface is a client, not a privileged one.
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.
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 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.
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.
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.
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.
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.
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.
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.
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.
We will walk Studio through your environment — what it shows today, what it would need from you, and what is still on the roadmap.