Almighty

Contribute › AIS receivers

Connect an AIS receiver

Send the ship messages your receiver picks up to Almighty, alongside any network you already feed. Ships near you then show on everyone's map.

1. Register in the Almighty app (More › Contribute) and add a station to get its key

There's no sign-up on this website. In the app, open More › Contribute, sign in, accept the Contributor Terms and tap Add a station. Choose AIS receiver, give it a name and put a pin where the antenna is (only you see it).

The app then shows the station key (shown once: copy it somewhere safe) and the station's feed UUID, which Option B and C use. You can also work the feed UUID out on this page.

App Store (iPhone, iPad, Mac) Google Play · coming soon Web app

Almighty only accepts data from stations added this way. Below, STATION_KEY and FEED_UUID stand for yours.

These steps use AIS-catcher, the free decoder for RTL-SDR, Airspy and similar receivers (see its documentation). It can send to several places at once: add Almighty as one more output.

2. Option A: AIS-catcher over HTTP (recommended)

AIS-catcher collects messages and posts them every 30 seconds over HTTPS, compressed. Nothing to open on your router, and the key travels encrypted. Add this to your AIS-catcher command line:

-H https://api.almighty.live/v1/contribute/ais/catcher userpwd station:STATION_KEY gzip on interval 30

For example, with an RTL-SDR dongle:

AIS-catcher -d:0 -H https://api.almighty.live/v1/contribute/ais/catcher userpwd station:STATION_KEY gzip on interval 30

Or, if you run AIS-catcher from a configuration file (AIS-catcher -C config.json), add an entry to its http list:

{
  "config": "aiscatcher",
  "version": 1,
  "http": [
    {
      "active": true,
      "url": "https://api.almighty.live/v1/contribute/ais/catcher",
      "userpwd": "station:STATION_KEY",
      "gzip": true,
      "interval": 30
    }
  ]
}

The word station before the colon stays as it is; only the key after it is yours. Keep interval at 30 seconds or more.

a terminal running AIS-catcher with the -H option above. Every 30 seconds it prints the server's answer for the Almighty output, and the message counter climbs as ships are heard.

AIS-catcher shows each post's answer, so you can see straight away whether the key works.

On a Raspberry Pi set up with AIS-catcher's install script, the command-line options are in /etc/AIS-catcher/config.cmd (and the file in /etc/AIS-catcher/config.json); restart it with sudo systemctl restart ais-catcher. In AIS-catcher's web control panel, add the same settings as an HTTP output.

3. Option B: AIS-catcher over TCP or UDP

If you'd rather stream every message as it arrives, AIS-catcher can send to our receiving server, feed.almighty.live, port 30110 (TCP or UDP). Each message carries your feed UUID so we know it's yours.

TCP:

-P feed.almighty.live 30110 msgformat JSON_NMEA uuid FEED_UUID

UDP:

-u feed.almighty.live 30110 msgformat JSON_NMEA uuid FEED_UUID

In a configuration file, the same goes in the tcp (or udp) list:

"tcp": [
  {
    "active": true,
    "host": "feed.almighty.live",
    "port": 30110,
    "msgformat": "JSON_NMEA",
    "uuid": "FEED_UUID"
  }
]

TCP and UDP aren't encrypted, and the feed UUID is as secret as the key: whoever has it can send as your station. If it leaks, make a new key in the app (that gives a new feed UUID too).

Work out your feed UUID

Paste your station key and the feed UUID is worked out here, in your browser. The key never leaves this page: nothing is sent anywhere, and the page has no analytics.

4. Option C: other software (plain NMEA over TCP)

Any program or receiver that outputs ordinary NMEA sentences (!AIVDM lines), such as rtl_ais, a dAISy or another hardware receiver, OpenCPN or gpsd, can send them over TCP to feed.almighty.live port 30110. The first line on the connection must be AUTH and your feed UUID; then the NMEA lines, one per line:

AUTH FEED_UUID
!AIVDM,1,1,,B,177KQJ5000G?tO`K>RA1wUbN0TKH,0*5C
!AIVDM,1,1,,B,...

If your software can only send to an address, put socat in between. For example, to take the NMEA a receiver serves on local TCP port 10110 and forward it:

( echo "AUTH FEED_UUID"; socat -u TCP:127.0.0.1:10110 - ) | socat -u - TCP:feed.almighty.live:30110

Or from a program that sends NMEA over UDP to port 10110 on the same computer:

( echo "AUTH FEED_UUID"; socat -u UDP-RECV:10110 - ) | socat -u - TCP:feed.almighty.live:30110

Run it under systemd or a loop so it reconnects. Plain NMEA over UDP to us isn't accepted: there's no way to tell who sent it. Use TCP as above, or Option A.

5. Check it's working

What you seeWhy, and what to do
401 "invalid key"Copy the key again from the app; check userpwd is station: then the key, with no spaces.
TCP connection closes straight awayThe feed UUID isn't one we know: work it out again from the current key. With Option C, check the first line is AUTH, a space and the UUID.
Station stays OfflineIs AIS-catcher hearing ships at all (its own counter or web page)? Is the station disabled in the app? Is the computer online?
429 or 503We're busy or you're posting too often. AIS-catcher tries again on its own; keep the interval at 30 seconds.

6. What we do with the data

Is it legal? Receiving AIS is legal in most countries: ships broadcast it openly for safety. A few countries restrict receiving radio messages not meant for you, or sharing them. Check the rules where you live before you share. You're responsible for having the right to send what you send (see the Contributor Terms).

Still stuck? Contact us with your station's name (never the key or feed UUID).