AIS DATA OPTIONS
Two practical reasons to consider Pelyr: share your receiver feed without putting its registered station details on the public coverage map, and use AIS data through an account even if you run no receiver.
Pelyr publishes this comparison and is independent of AISHub. Sources and review date appear below.
Add Pelyr as another output. Its public map shows coverage, but no registered station coordinates, name or ID. Coverage may still hint at a location.
Start with a free account for the JSON API, live WebSocket Stream and vessel map. Non-commercial terms and plan limits apply.
SIDE BY SIDE
Use this to choose a starting point. For coverage and suitability, check the vessels and areas your project actually needs.
| Question | AISHub | Pelyr |
|---|---|---|
| Getting access | The combined-data API is for contributors whose own AIS receiver feed meets AISHub’s station standards. Every member can use the map and their station statistics. | A free account gives you limited map, HTTPS API and WebSocket Stream access for non-commercial use. You do not need to run a receiver. |
| Developer interface | A queryable webservice returns XML, JSON or CSV. Its published API instructions say to call it no more than once per minute. | A JSON HTTPS API provides vessel snapshots, details and recorded tracks. A separate WebSocket Stream delivers incoming AIS reports. Plan and endpoint limits apply. |
| Commercial use | AISHub’s published terms permit commercial work built from its data with visible contributor credit. Passing on raw AIS messages, positions or tracks is prohibited. | The Free plan is non-commercial. Paid developer plans permit commercial use of API and stream data under Pelyr’s data licence and attribution rules. |
| Contributing data | A station and its feed are the basis for joining. API access requires at least 10 vessels in coverage and 90% uptime (both 7-day averages), at most 60 seconds downsampling and 10 seconds message delay. | Sharing a receiver feed is optional. Station operators may apply for Community access; contributing does not automatically grant a plan. |
| Public station details | AISHub says a member station’s location and statistics appear on its map. Its terms say the contributor’s name and email address are not public. | Pelyr’s public coverage map omits station ID, registered coordinates, station name and contributor name. Coverage patterns can still suggest where reception comes from. |
AISHub details are from its join page, API documentation and terms. Pelyr details are in our Free plan guide, pricing and data licence and Contributor Terms.
WHY PELYR?
Add Pelyr to an existing receiver setup through AIS-catcher, docker-shipfeeder or UDP on request. Your other feeds can keep running. The public coverage map omits your registered station coordinates, name and ID; coverage itself can still hint at a receiver’s location.
Explore station sharingCreate an account for the JSON HTTPS API, incoming reports over WebSocket and recent tracks within your plan’s limits. Free access is for non-commercial projects; paid developer plans permit commercial use under the data licence.
Explore Pelyr developer toolsAISHub remains an option if you operate a qualifying station and want its XML, JSON or CSV webservice. Pelyr reviews new stations before activation. Contributions are unpaid and do not automatically grant a plan; Pelyr’s licence for data already sent continues after you stop sharing. Read the Contributor Termsbefore connecting.
COMMON QUESTIONS
The public coverage map does not show your registered station coordinates, station ID or name. Coverage patterns may still suggest where reception comes from. Read the Contributor Terms for the exact scope.
For the combined-data API, yes. AISHub says applicants need an operational receiver feed. API access then depends on its published quality thresholds, including vessel coverage and uptime. See its joining requirements.
AISHub’s published terms permit commercial work built from the data. Visible contributor credit is required where customers or the public see the data or work based on it, and raw data cannot be passed on. Read the full terms for the scope and effective dates.
Yes. Create an account for the Free map, HTTPS API and WebSocket Stream. The Free plan is for non-commercial use and has published limits. You can also contribute a receiver, but Community access is granted only after an application and review.
Coverage changes with active receivers, geography and time. We do not claim that either network covers every vessel or area. Test the places and vessel types you need before relying on either service.
SOURCES & SCOPE
Reviewed 28 October 2026. AISHub’s terms say they apply to new members from joining and to existing members from 1 January 2027. This page describes published access and licence rules, not a measured comparison of coverage, latency or uptime.
AIS reports can be missing or delayed. Neither service’s data should be used for navigation or safety decisions.
START WITH PELYR
Open the map or create a free API key. Check the available coverage and plan limits before you build around them.