kimo
Intelligence

AIS Maritime + Kimo

Vessel positions and voyage data from AIS, with gap detection and port-call history ready for maritime analysis.

Auth
API key
Sync
Real time
Setup
≈ 3 min
Request access

Live demo workspace with fictional data · no signup, no credentials needed

kimo / connectors / aisSyncing
Sync logreal time
  • Succeeded:positions+1,295 rowsnow
  • Succeeded:port_calls+2,076 rows2m ago
  • Succeeded:vessels+2,133 rows4m ago
  • Succeeded:positions+514 rows6m ago
Rows synced · 30 days
58.8M
Workspaces
15%
Simulated demo data
What you can do

What teams build with AIS Maritime

AIS Maritime on its own answers half the question. Joined with the rest of your stack in Kimo, it answers the other half.

01

Vessel tracks and port calls

Replay tracks, port calls and loitering for any vessel or area over time.

Track replay
02

Dark vessel detection

Flag AIS gaps longer than a threshold near sensitive areas.

Gap > 6 h
03

Fuse with other feeds

Correlate vessel positions with OSINT reports and ADS-B traffic in one map.

Multi-INT
Objects & tables

Exactly what gets synced

Kimo maps AIS Maritime into clean, typed tables with primary keys and incremental cursors, so syncs stay fast and joins just work.

3 tables · 15 fields

positions

Streaming≈ 56,600 rows
FieldTypeNotes
mmsistring
tstimestampIncremental cursor
latdecimalMeasure
londecimalMeasure
sog_knstring
cog_degstring
Custom fields and extra objects are discovered automatically on each sync. Row counts are illustrative.
Sample model

From raw AIS Maritime tables to a certified metric

This model ships with the Defense Intelligence demo. Open it to see every join and measure.

Threat correlation

OSINT signals and SIEM events correlated by entity, zone and time window.

In the demo
  • OSINT Feeds
    signals
  • Splunk
    events
  • AIS Maritime
    positions
Model
entity = asset
Measuressignalseventsalerts
Signals ingested · last 30 days
216.3K+3.1% wk/wk

Fictional data · hover the chart for daily values

Setup

Connect AIS Maritime in 3 min

No engineers, no pipelines to maintain. Kimo asks for the minimum access it needs and tells you exactly what it will read.

  1. 1

    Create a read-only key in AIS Maritime

    Use a dedicated key scoped to read access, so it can be rotated independently.

  2. 2

    Paste it into Kimo

    Keys are encrypted with a per-workspace key and never shown again.

  3. 3

    Choose streams

    Pick which objects to sync, starting with positions.

  4. 4

    Validate and sync

    Kimo tests the key, backfills history and keeps it fresh (real time).

Read-only, encrypted, revocable. Credentials are encrypted with a per-workspace key, never logged, and can be rotated without breaking your models.

Connect AIS Maritime
Step 2 of 3 · Kimo demo workspace
  • Reaching host
  • Authenticating
  • Reading schema
Read-only access
Illustration only · placeholder values, never real secrets
FAQ

AIS Maritime questions, answered

AIS Maritime is ingested as a stream. New records typically appear in models and maps within a few seconds.

AIS Maritime · API key · Real time

See your AIS Maritime data in Kimo in 3 min.

Try it on the live demo workspace first, then connect your own account when you are ready.

Request access