Home/Sectors/Software & platforms
An AIS data API you can build on, and a second source you can fall back to.
Real-time vessel positions from the network we build and operate, delivered over REST, WebSocket or raw NMEA. Built for engineering teams carrying maritime data inside a product their own customers pay for.
100,000+
Vessels tracked / day
49M+
AIS positions / day
40+
Countries covered
<5s
Antenna to your API
One AIS data provider is not redundancy, it is a single point of failure.
Two AIS contracts frequently resolve to a single upstream source, leaving no independent failover path.

Two suppliers can resolve to a single owner.A maritime product typically begins with one feed and adds a second for resilience. Consolidation has eroded that position: several well known vessel tracking APIs now sit inside the same corporate group, acquired there between 2023 and 2025. A failure at that owner propagates to every maritime function in the product.
The free fallback cannot be procured.Open exchanges require you to operate physical AIS receiver hardware before drawing from the pool, which excludes any software team without one. The metering unit, not the headline rate, determines whether a feed remains viable in dense near-shore water, where per vessel and per request counting diverge sharply.
We do not ask to be primary.We operate our own terrestrial and ship-borne receivers, with satellite feeds for open ocean, every station on identical standardised hardware, encrypting each message at the point of capture. That is 49M+ positions a day reaching your API in under 5 seconds, delivered as raw NMEA over TCP, REST, WebSocket or SAPIENT compliant output.
Evaluate it against your own coverageSend the bounding boxes you serve and the throughput you expect, and we will establish what our network returns across that water.
Test the feed in your stackHow to add AIS data to your logistics platform without one point of failure.

A deliberate second source
Run our feed alongside your incumbent provider, on separate hardware, separate ownership and a separate commercial roadmap. Integrated and exercised in advance, so failover becomes a configuration change rather than an incident without remedy.
Data your own customers can see
Redistribution, sublicence and display rights are where most maritime integrations stall at legal review, since standard data terms are commonly non-transferable. Specify what your end customers would see, and we will settle the licensing position before you build.
Corroboration before you serve a position onward
AIS carries no authentication, so a single feed can only report what it received. An independent network observing the same water records manipulation as measurable disagreement, which your pipeline can act on rather than relay unexamined.
The cleaning cost behind any AIS training set
Raw AIS arrives with irregular sampling and uneven noise per vessel, so trajectory imputation and cleaning routinely consume more engineering than the integration itself. Budget for that work, and establish early which gaps are a property of the water and which are introduced by the pipeline.
Continuity when an endpoint is deprecated
Endpoint retirements, forced migrations from REST to GraphQL and repackaged pricing each convert a working integration into unplanned engineering. A second source already wired in means re-integration proceeds on your schedule rather than a supplier’s.
Sizing the integration before you commit
Provide the access pattern you expect in production: bounding boxes, refresh rate, message throughput, and whether you require static messages for vessel type and dimensions or positions alone. We size the integration against those figures, not a vessel count.
How our AIS data API is produced,
from antenna to your endpoint.
Every station runs identical dedicated hardware, encrypting each message at the point of capture.
Monitor
Collected on our own network
100,000+ vessels and 49M+ AIS positions a day across 40+ countries, from terrestrial and ship-borne receivers we own and operate, plus satellite feeds offshore, reaching your API in under 5 seconds.
Verify
Scored before it reaches you
Every position carries a nanosecond timestamp, the station that collected it, and a trust score from our anomaly detection models.
Act
Into your stack, your way
Raw NMEA over TCP, a REST API, a WebSocket stream, or SAPIENT compliant output. Run it beside your existing feed and compare the two on the vessels you care about.
Questions engineering and data teams ask us.
Can I resell AIS data inside my own SaaS product?
This is a licensing question rather than a technical one, and the most common reason a maritime integration fails at legal review, since standard data terms are frequently non-transferable and non-sublicensable. The position is better settled before you build than after. Tell us who your end customers are, what they would see and whether the product is white-labelled, and we will confirm in writing what we can support.
What happens to my platform if my AIS data provider goes down?
It does whatever your architecture does when its only source disappears, which for most maritime products is nothing useful: the map empties, alerts cease, and an outage presents identically to an unusually quiet sea. Single-source maritime feeds do fail: national terrestrial AIS data has been cut off at source before, and public AIS APIs have gone dark for hours at a time. The remedy is not a larger primary feed but a structurally independent second one, integrated and tested before you need it.
Is AIS data metered per request or per vessel?
Both models exist and the difference is material. Per vessel metering scales with vessel density, so a chokepoint can cost many times what the same monitoring costs under per request metering, which instead scales with polling frequency. Establish which model fits your access pattern, then require any provider, including us, to state the metering unit, rate limits and quota behaviour in those terms.
Do you cover the waters our platform serves, and how do we check?
Coverage follows our own network, so the answer is specific to the water rather than a single figure quoted for every ocean. Send the bounding boxes you serve and the vessels your customers care about, and we will state what our network collects across that area and where it is thin, so any gaps surface during scoping rather than halfway through the integration.
How do I verify AIS positions are not spoofed before serving them to customers?
AIS carries no authentication and never has. Any transmitter conforming to the protocol can broadcast any MMSI, course and speed, so a single feed cannot establish that it is being deceived, only what it received. Corroboration by an independent network is what makes manipulation visible: two networks disagreeing on one vessel is itself evidence. Every position we deliver carries a trust score, so you can filter or flag rather than relay it unexamined.
Related sectors
Run us next to the feed you already have.
Send the waters you cover and the delivery method you require, and assess what an independent network returns on the same vessels.
Test the feed in your stack


