Data Sources
Maritime, sanctions, ownership, and behavioural data powering Peloryn intelligence.
Peloryn combines multiple maritime, regulatory, and open-source intelligence signals to help operators understand vessel risk across the Antwerp–Rotterdam–Amsterdam corridor.
Our platform is not built around one data feed or one isolated risk score. Peloryn connects vessel movement, sanctions exposure, ownership context, port geography, AIS behaviour, and historical vessel patterns into a clearer operational view.
The goal is simple:
Help maritime teams understand whether a vessel, voyage, or counterparty deserves further review before risk becomes exposure.
Our Data Philosophy
Maritime intelligence is only useful when the data behind it is reliable, explainable, and responsibly handled.
Peloryn is built around three principles:
1. Multiple Signals Are Stronger Than One Feed
A single AIS position does not tell the full story. A sanctions match does not always explain operational risk. A vessel name alone can be misleading.
Peloryn combines different source types to build a more complete picture of vessel behaviour and exposure.
2. Context Matters
The same vessel behaviour can mean different things depending on where it happens.
A vessel waiting near a normal anchorage may be routine. A vessel going silent near a high-coverage corridor, reappearing after a suspicious route gap, or meeting another tanker offshore may deserve closer review.
Peloryn focuses on regional context, especially around the ARA corridor, North Sea approaches, English Channel routes, and connected European maritime flows.
3. Data Must Be Handled Responsibly
Maritime data can come with licensing, retention, attribution, and usage restrictions.
Peloryn is designed to treat data governance as part of the intelligence process. Data sources are reviewed, permissions are tracked, and customer-facing outputs are designed to remain clean, explainable, and audit-ready.
Source Categories
AIS Vessel Movement Data
AIS data provides the foundation for vessel movement intelligence.
Peloryn uses AIS signals to understand vessel position, speed, heading, course, destination, identity, and movement history.
AIS data helps Peloryn detect and analyse:
- Vessel location and movement
- Route history
- AIS gaps and dark periods
- Unusual speed or course changes
- Suspicious loitering
- Potential ship-to-ship transfer behaviour
- Reappearance after signal loss
- Movement around high-risk zones
AIS is powerful, but it is not perfect. Signals can be missing, delayed, manipulated, duplicated, or switched off. This is why Peloryn does not treat AIS as a simple map layer. It is analysed as part of a wider behavioural intelligence system.
Sanctions and Watchlist Data
Peloryn uses sanctions and watchlist information to help identify vessels, companies, owners, and related entities that may create compliance exposure.
These sources may include official and regulatory lists such as:
- OFAC sanctions data
- European Union sanctions data
- United Kingdom sanctions data
- United Nations sanctions data
- Other public or regulatory watchlist sources where appropriate
Sanctions screening is an important part of maritime compliance, but it is only one layer.
A vessel may not appear on a sanctions list today, but its behaviour, ownership structure, recent contacts, or voyage history may still deserve review.
Peloryn connects sanctions data with vessel behaviour to support more practical risk analysis.
Ownership and Corporate Data
Vessel risk is not always visible from the hull.
Ownership, management, beneficial ownership, corporate structure, and related entities can all affect compliance exposure.
Peloryn uses corporate and registry-style data to help understand:
- Registered owners
- Managers and operators
- Corporate relationships
- Beneficial ownership indicators
- Legal entity information
- Ownership opacity
- Recent ownership or management changes
This helps users move beyond basic vessel identification and ask a deeper question:
Who is behind the vessel?
Port, Zone, and Geospatial Data
Maritime behaviour cannot be understood without geography.
Peloryn uses port, corridor, anchorage, waterway, and geofence data to interpret vessel activity in context.
This may include:
- Port areas
- Inland waterways
- Anchorage zones
- High-risk maritime zones
- Operator-defined monitoring zones
- Sanctioned or sensitive geofences
- North Sea and ARA corridor operating areas
Geospatial context helps reduce false positives.
For example, low-speed vessel movement inside a port may be normal. Similar behaviour outside a normal operating zone may require review.
Behavioural and Anomaly Signals
Peloryn generates behavioural signals from vessel movement, historical patterns, and operational context.
These signals may include:
- AIS gaps
- Dark activity indicators
- Ship-to-ship transfer patterns
- Kinematic spoofing signals
- MMSI cloning indicators
- Suspicious loitering
- Abnormal destination changes
- Draft change indicators
- Target zone incursions
- Tainted vessel contact
- Implied dark port-call risk
These signals are not designed to replace human judgement. They are designed to help analysts, operators, and compliance teams identify which vessels deserve attention.
Historical Vessel Memory
A vessel’s current position is only one part of its risk profile.
Peloryn builds vessel memory by analysing past behaviour, previous routes, dark periods, zone visits, anomalies, and operational patterns.
Historical vessel memory helps answer questions such as:
- Has this vessel gone dark before?
- Does this route match its normal behaviour?
- Has it previously met risky vessels?
- Has it shown repeated anomaly patterns?
- Is its current behaviour unusual for this vessel type or corridor?
- Has it been connected to suspicious activity before?
This turns vessel monitoring from a live map into a more useful intelligence layer.
Regional Behaviour Baselines
Peloryn is focused on the ARA corridor and connected European maritime routes.
This regional focus allows the platform to build a better understanding of what normal behaviour looks like in specific areas.
Regional baselines help interpret:
- Normal waiting times
- Typical vessel speeds
- Common route patterns
- Anchorage behaviour
- Expected AIS visibility
- Zone-specific movement patterns
- Vessel-type behaviour differences
This matters because risk is not universal. A pattern that is normal in one place may be unusual in another.
Peloryn is designed to understand maritime behaviour in context.
How Peloryn Uses Data
Peloryn uses data to support four core intelligence workflows.
1. Vessel Screening
Users can review a vessel before a charter, supply operation, port service, or counterparty decision.
Peloryn helps surface relevant sanctions, ownership, behavioural, and historical risk indicators.
2. Corridor Monitoring
Peloryn monitors vessel movement across important maritime areas connected to the ARA corridor.
This helps identify suspicious activity before it becomes a commercial or compliance problem.
3. Anomaly Detection
Peloryn analyses movement behaviour to detect signals such as AIS gaps, spoofing, suspicious loitering, ship-to-ship activity, and abnormal route changes.
4. Explainable Risk Scoring
Peloryn does not only produce a number.
Risk scores are connected to evidence, context, and event history so users can understand why a vessel was flagged.
Compliance-Safe Intelligence
Peloryn is designed with data responsibility in mind.
Not every data source can be used in the same way. Some sources may be suitable for internal analysis but not for customer-facing reports. Others may require attribution, retention limits, or restricted handling.
Peloryn’s data architecture is designed to support:
- Source permission tracking
- Data lineage
- Retention controls
- Usage restrictions
- Auditability
- Compliance-safe exports
- Clean customer-facing summaries
This helps ensure that intelligence is not only useful, but also responsibly produced.
What Peloryn Does Not Do
To maintain clarity and trust, Peloryn does not present every data point as certainty.
Maritime intelligence often involves incomplete information, delayed signals, ambiguous behaviour, and changing legal context.
Peloryn does not claim that every alert proves wrongdoing.
Instead, Peloryn identifies reviewable risk.
A vessel flagged by Peloryn should be understood as a vessel that may require further analysis, documentation, or compliance review based on available signals.
Data Quality and Limitations
All maritime intelligence systems depend on the quality and availability of their data sources.
AIS signals may be incomplete. Ownership records may be delayed. Sanctions lists may change. Corporate structures may be opaque. Port and zone definitions may require updates.
Peloryn works to reduce uncertainty by combining multiple signals and presenting risk in context.
Where data is incomplete or uncertain, the platform is designed to show that uncertainty rather than hide it.
Why This Matters
The modern maritime risk environment is becoming harder to read.
A vessel may look clean on a live map but carry hidden exposure through its recent movements, ownership links, AIS gaps, ship-to-ship contacts, or sanctions-adjacent activity.
Peloryn’s data approach is built to connect those signals.
By combining vessel movement, sanctions data, ownership context, port geography, regional baselines, and behavioural intelligence, Peloryn helps maritime teams make faster, clearer, and more defensible decisions.
Data Sources Disclaimer
Peloryn uses maritime, regulatory, public, licensed, open-source, and derived intelligence sources where appropriate.
Availability, coverage, update frequency, and permitted use may vary by source. Peloryn continuously reviews data quality, licensing terms, and compliance requirements as part of its intelligence process.
Peloryn’s outputs are intended to support maritime risk analysis and compliance workflows. They should not be treated as legal advice, sanctions advice, insurance advice, or a substitute for professional due diligence.