April 18, 2026

Vessel ownership traversal and sanctions matching

Overwatch can now trace vessel ownership chains through corporate layers and automatically match them against sanctions lists. The traversal walks ownership, operator, and ship-manager relationships up to a configurable depth, flagging any sanctioned entity in the chain. Matching uses IMO numbers first to avoid false positives from name-only lookups, and confidence decays with each hop so you can prioritize the most direct exposures. See the risk API for details.

Flag-hopping detection

Overwatch now tracks every flag-state change for each vessel and flags those that switch registries frequently — a common indicator of regulatory evasion. Vessels with high flag churn are surfaced in a dedicated scoreboard, and flagged-vessel status feeds directly into the ownership traversal so sanctions risk scores account for obfuscation patterns.

Port state control detention scoring

Vessel risk scores now incorporate port state control (PSC) inspection data from USCG PSIX. Detention counts and deficiency records over the trailing 24 months are rolled into a 0–100 PSC risk component, tiered from low to critical. Scores update daily, so a vessel that picks up a new detention is reflected in your risk view within a day.

NOAA port water conditions

Overwatch now ingests real-time water level, current, temperature, and salinity observations from NOAA CO-OPS stations near major US ports. Data refreshes hourly and is available for historical backfill up to 30-day windows on demand. This gives you environmental context alongside vessel movements — useful for understanding delays or anomalies tied to tidal or weather conditions. See the ports API for details.

NOAA buoy weather observations

Weather data from approximately a dozen NDBC buoys near major US port approaches is now available in Overwatch. Wind speed, wave height, and temperature readings refresh hourly and provide environmental context for AIS anomaly analysis — helping distinguish weather-driven slowdowns from suspicious behavior.

EPA maritime enforcement data

Overwatch now ingests EPA compliance and enforcement records for maritime facilities — including ports, marine cargo handlers, and petroleum refineries — across US coastal states. Each facility is geocoded and enriched with per-violation enforcement detail (action type, penalty amount, violation description), giving you a facility-level view of environmental compliance risk in and around ports.

Vessel ownership and manager history

Ownership and ship-manager changes detected through enrichment are now tracked as temporal relationships with full history. When an owner or manager changes, the previous relationship is closed and a new one opens — so you can see not just the current owner, but the full chain of custody over time.

AIS behavioral analytics

Overwatch now supports a structured data model for AIS behavioral analytics, covering track gaps, maneuver detection, pairwise vessel encounters, COLREGS assessments, speed profiling, and multi-signal fusion scoring. This lays the foundation for upcoming kinematic anomaly detection features that will flag suspicious vessel behavior patterns.

Expanded API with watchlists, alert channels, and emissions reporting

The Overwatch API now includes a significantly wider set of endpoints. You can manage watchlists in bulk, configure alert rules with Slack delivery, generate emissions reports, look up ultimate beneficial ownership (UBO) chains by IMO number, and run sanctions audit queries — all through the REST API. Locus users also gain API access to portfolio management, custom scoring formulas, and scheduled data exports. See the Overwatch API reference and Locus API reference for the full endpoint list.

Workspace management and team controls via API

New workspace API endpoints let you create and manage team workspaces, configure SSO providers, set resource-level access controls, manage invitation flows, and define permission scopes — all programmatically. This is useful for organizations that need to automate user provisioning or integrate Axiom access management into existing tooling.

Maritime disruption signals in Locus cell scores

Locus cell risk scores now incorporate maritime disruption signals from Overwatch. When a port disruption, congestion spike, or supply chain anomaly is detected, nearby Locus cells automatically reflect the elevated risk. This cross-product signal means your territory assessments stay current with real-world logistics events without any manual adjustment.

Cell detail view and scoring improvements

Locus now includes a fully redesigned cell detail panel. When you click into an H3 cell, you can view median income, notable events, nearby points of interest, score history with sparkline annotations, and rent burden data — all in one place.

The Discover filters have also been expanded with new sort options and CSV export, making it easier to narrow down territories and share results with your team.

AI-powered permit extraction

Building permit records now include AI-extracted work descriptions, so you can quickly understand what construction or renovation activity is happening in a cell without reading raw permit filings. Extraction results stream into the platform as they finish for faster access.

FEMA flood exposure scoring

Safety scores in Locus now incorporate FEMA NFIP flood exposure data. Cells in flood-prone areas are flagged automatically, giving you a more complete picture of location risk when evaluating territories.

311 complaint sentiment signals

Locus ingests 311 complaint narratives and converts them into H3-level sentiment signals. This adds a new layer of neighborhood quality data to your cell scores, surfacing areas with recurring resident complaints.

Civic upzoning signals

The dashboard now surfaces civic upzoning activity, helping you spot areas where zoning changes may signal future development or shifts in land use.

12 new federal and public data sources

Locus now ingests data from 12 additional public sources, expanding coverage across housing, transit, employment, environment, and community health. New sources include HUD subsidized housing, FTA transit ridership, H1B employer data, FEC campaign contributions, CDFI community development awards, SAM.gov veteran-owned businesses, NPI healthcare provider locations, IRS exempt organizations, NFIRS fire incidents, EPA Toxics Release Inventory, and USDA crop data. These feed directly into cell scoring for richer, more accurate territory assessments.

OSHA workplace safety data

Locus now incorporates over 200,000 OSHA severe injury records — including amputations, hospitalizations, and fatalities — into cell-level risk scoring. This data is publicly available and refreshes annually, giving you a clearer picture of workplace safety conditions in the territories you evaluate.

Health and employment scoring signals

Cell scores now include two new signal types: health indicators and employment density. These signals enrich the scoring model with public health and workforce data, helping you identify areas with strong economic activity or emerging health-related risks.

Audit log

Layer now includes a tenant-scoped audit log that records every significant action in your workspace — integration connections, asset changes, user role updates, data exports, and more. Each entry captures who performed the action, what was affected, and when it happened. Events are immutable and retained for six years to support HIPAA and SOC 2 audit requirements. View the log at Settings → Audit log.

One-click OAuth for Google Workspace and Microsoft 365

Connecting Google Workspace and Microsoft 365 to Layer no longer requires creating a service account or registering an Azure AD app. Admins now click Connect, sign in once, and grant consent — Layer handles the rest through a streamlined OAuth flow.

The same one-click experience extends to Intune, Microsoft Teams, and M365 Mail connectors.

HRIS integrations

Layer now connects to popular HRIS platforms including Rippling, Gusto, BambooHR, Deel, HiBob, and Workday. Employee lifecycle events, department mappings, and workforce status flow directly into your asset graph — so onboarding and offboarding workflows stay in sync with your HR system. See integrations for setup details.

Integration health banner on dashboard

The Layer dashboard now displays a health banner at the top of the connections grid whenever any integration is failing or needs re-authorization. The banner shows the number of affected connectors along with an amber Resolve button that takes you straight to the integrations page to fix them.

Daily integration health email

Layer now sends a daily email digest to workspace admins whenever integrations are failing or need re-authorization. The email lists each affected connector with its status and a direct link to resolve the issue in your integrations dashboard. No setup is required — the digest is sent automatically at 09:00 UTC each day and only goes out when there are connections that need attention.

Reconnect prompt for expired integrations

Connectors that need re-authorization now display a colored status badge and an amber Reconnect button directly in the integrations page. Clicking it reopens the OAuth flow so you can re-authorize in one click — no need to delete and re-add the connection.

Top employees by spend on dashboard

The Layer dashboard now highlights your top three employees by cost, giving you a quick snapshot of where the highest spend is concentrated without navigating away from the main view.

Brand icons and setup hints on integration cards

Connector cards in the integrations page now display real brand logos. Credential forms for popular connectors — including Okta, AWS, Slack, Jamf, and GitHub — now show placeholder examples and info tooltips that explain what each field expects and where to find the value.

Cross-product navigation bar

The Axiom navigation bar now appears at the top of every dashboard page, so you can switch between Layer, Overwatch, Locus, and Codex without leaving your current session. The bar matches the marketing site layout and stays pinned as you navigate.

Guided onboarding on the integrations page

The integrations page now shows a guided onboarding prompt when you haven't connected any integrations yet. It recommends starting with Google Workspace or Microsoft 365 — both one-click OAuth, no API tokens required — and highlights key trust signals: no agents on devices, read-only by default, and tokens encrypted at rest. The prompt disappears automatically once your first integration is connected.

Port Authority Governance v1.0 schema

Codex now includes a Port Authority Governance dataset covering board meetings, agenda items, claims, facts, minutes, and tariffs from five major US port authorities — Oakland, Long Beach, Los Angeles, JAXPORT, and the Port Authority of New York & New Jersey. Each port uses a purpose-built adapter that normalizes records into a consistent schema for cross-port queries. Tariff items include bitemporal supersession tracking, so you can query rates in effect at any point in time and trace how rates changed between versions. The dataset joins to AIS Maritime Positions via UNLOCODE and terminal-level H3 cells, and to Civic Intelligence via jurisdiction_slug.

Envelope coverage dashboard

Codex now includes an envelope coverage dashboard at Admin → Codex coverage that tracks APRS record_id adoption across every catalog table. The dashboard shows summary cards (tables tracked, fully compliant, empty, in progress), a color-coded sortable table with per-table row counts and backfill status, and an overall compliance percentage. Data refreshes nightly at 05:00 UTC.

APRS data envelope

Codex now applies a standardized data envelope (APRS) across all ingested records. This ensures consistent shape and metadata compliance for audit evidence, making exports and compliance checks more reliable.

Automatic APRS backfill for existing records

Codex now automatically backfills existing data sources with the APRS envelope, so historical records are wrapped in the same standardized format as new ingestions. Backfill jobs run on staggered schedules to avoid load spikes, and each record receives a unique URN for traceability. No manual migration is required — your full dataset will be APRS-compliant without any action on your part.

Data source catalog tracking

Codex now maintains a live catalog of every active data source across the platform. The catalog tracks record counts and last-loaded timestamps, refreshing automatically each night. Any ingestion source that isn't registered in the catalog is flagged so gaps are caught early — you no longer need to audit data coverage manually.

Redesigned Overwatch landing page

The Overwatch landing page has been refreshed with an interactive hero map featuring live vessel markers, location shortcuts for major shipping lanes (Gulf Coast, English Channel, Singapore, Bosphorus), and a video walkthrough. The page now gives a clearer overview of the platform's capabilities before you sign in.

Improved cargo estimation accuracy

Hydrostatic cargo estimates now use vessel-class-specific displacement thresholds tuned from industry standards (IMSBC for bulk, OCIMF for tankers). Previously, uniform thresholds placed most observations into a single bucket. Vessel type sampling is also stratified so less-common classes like chemical tankers and LNG carriers are properly represented in cargo validation models.

Self-healing enrichment pipeline

The vessel enrichment pipeline now automatically detects and recovers stuck jobs. Previously, a crash during enrichment could leave records in a stalled state until someone manually reset them. Overwatch now sweeps for stalled jobs every 30 minutes and requeues them, so enrichment data stays current without manual intervention.

Refreshed Locus landing page

The Locus landing page has been redesigned with a cleaner light theme, larger typography, and a new video hero section. The signal journey now uses a vertical timeline with story cards for a more intuitive walkthrough of the product.

OSHA data source updated

The OSHA workplace safety data feed has been migrated to the current bulk data source, replacing the retired API. Score calculations that depend on OSHA data are now up to date.

Adaptive cell resolution by population density

Locus now automatically adjusts H3 grid resolution based on population density. Dense urban areas use finer-grained cells for more precise scoring, while rural areas use larger cells to avoid noise from sparse data. This means scores better reflect the character of each area without any configuration on your part.

Richer point-of-interest data

Points of interest in Locus now include photos and review summaries alongside the existing name and category data. This gives you more context when evaluating what's on the ground in a given cell, without leaving the platform.

40+ integrations

The Layer integration catalog now spans 40+ connectors across identity, device management, cloud infrastructure, ITSM, security, finance, HRIS, and collaboration categories. Most connectors use admin-consent OAuth, so there are no API tokens to copy or service accounts to configure.

Redesigned dashboard and core pages

The Layer dashboard has a new layout with spend trend charts, sparkline metrics, and a two-column view for savings opportunities and upcoming renewals. The apps, people, spend, contracts, and renewals pages have also been refreshed with updated card layouts, filters, and urgency indicators across the board.

Improved integrations grid

The integrations page now uses colored tiles with status rings so you can quickly see which connectors are active, pending, or disconnected.

Automatic token refresh for OAuth integrations

Google Workspace, Microsoft 365, Intune, and M365 Mail connections now automatically refresh their access tokens in the background. Previously, tokens could expire after the initial OAuth setup, causing syncs to fail silently. Layer now detects expired tokens and refreshes them on every sync, so your integrations stay connected without any manual intervention.

Live last-synced timestamps

The "Last synced" label on the integrations page now refreshes automatically every 30 seconds. Previously, the timestamp could go stale if the tab stayed open.

Continuous APRS compliance validation

Every change to Codex data collectors and ingestion pipelines is now automatically validated against the APRS standard before it goes live. If a data source falls below the compliance threshold, the update is blocked until the issue is resolved. This guarantees that all records flowing into Codex maintain consistent envelope metadata, so your audit exports and compliance checks stay reliable over time.

Source provenance on entity relationships

Every relationship in the Codex entity graph — ownership chains, flag history, sanctions links — now carries provenance metadata showing which data feed and system produced it. This makes it easier to trace the origin of any connection during audits or investigations.

Overwatch bug fixes

• Fixed an issue where vessel departures could go undetected for several days due to a silent failure in the event processing pipeline. Departure detection is now handled by a dedicated scheduled job for improved reliability.
• Fixed hydrostatic cargo estimates returning empty results for all vessel visits due to a data type handling issue.
• Fixed vessel visit draft readings sometimes arriving as text instead of numbers, which could cause downstream cargo estimates to fail silently.
• Improved vessel enrichment reliability by reducing batch sizes and adding timeout safeguards to prevent failures on large fleets.

Locus bug fixes

• Fixed an issue where the maintenance risk score endpoint returned a 404.
• Resolved a bug in the council legislation monitor where recent updates could be missed.
• Extended transit data retention from 30 days to 90 days, so historical transit patterns are available for longer-term analysis.

Atlassian connector fixes

• Fixed an issue where the Jira/Atlassian connector form collected the wrong credentials, causing all syncs to fail with a 401 error. The form now asks for the correct Organization ID and Org Admin API Token.
• Fixed pagination for large Atlassian organizations so all users are synced, not just the first 200.

Layer bug fixes

• Fixed an issue where the Apps page incorrectly redirected to the login screen when an organization was not yet linked. It now shows a helpful message instead.

Smarter compliance checker with per-table introspection

The Codex compliance checker now dynamically discovers which envelope columns each table has before running validation checks. Previously, the checker assumed every table used created_at for ordering, which caused false failures on tables like AIS positions, events, building permits, and vessels that use different timestamp columns. Optional envelope fields that aren't present on a table are now skipped instead of flagged -- absent-optional no longer counts as non-compliant.

Civic records data quality improvements

Fixed data quality issues in the civic records dataset: 3,106 records now have properly synthesized source_uri values (Granicus URNs, ELMS and YouTube URLs), 121 records with incorrectly-cased record_id URNs have been lowercased, and 16 records with future-dated occurred_at values have been corrected. These fixes ensure civic records pass APRS compliance checks and are properly traceable to their original sources.

Codex backfill performance fix

Fixed a timeout issue where APRS backfill jobs on large tables would progressively slow down and eventually fail. Backfill now uses an efficient cursor-based approach, so job runtime stays constant regardless of table size.

Codex index rebuild reliability fix

Fixed an issue where index rebuilds on large Codex tables could deadlock when running in parallel, causing data processing to stall. Index operations are now serialized automatically, so rebuilds complete reliably without manual intervention.

Curated integration catalog

The Layer integrations page now only shows connectors that have a working backend — placeholder entries that accepted credentials without syncing data have been removed. If you need a connector that isn't listed yet, click Request a connector at the bottom of the catalog to let us know. The most-requested integrations are prioritized on the roadmap. See the integrations overview for details.

Command palette

Press ⌘K (or Ctrl+K on Windows/Linux) to open a new command palette that lets you jump to any page, search across your workspace, and run common actions without leaving the keyboard. Results update as you type with live search, so you can navigate the entire app in a few keystrokes.

Self-service billing

Layer now supports self-service plan management. Upgrade, downgrade, or update your payment method directly from Settings → Billing — no need to contact support. You can also view past invoices and manage your subscription from the billing portal.

In-app support chat

A live support chat is now available on every page across the Layer dashboard and marketing site. Click the chat icon in the bottom-right corner to ask questions, report issues, or request help — conversations are tied to your account for faster resolution.

Smoother page transitions

Navigating between pages in the Layer dashboard now shows a slim progress bar at the top of the screen and per-route loading skeletons, so you always know something is happening. Previously, route changes could feel unresponsive on slower connections.

Refreshed product marks

All four Axiom product logos — Layer, Overwatch, Locus, and Codex — have been redesigned with bolder, more distinct silhouettes so they're easier to tell apart at small sizes and across the platform.

Smarter per-table compliance checks

The APRS compliance gate now introspects each table's actual schema before running validation, instead of assuming every table shares the same column layout. Tables that use different timestamp columns — like timestamp, started_at, or loaded_at — are now handled correctly. Optional temporal columns that aren't present on a given table are treated as acceptable rather than flagged as non-compliant, so you'll no longer see false failures after schema changes or on tables with intentionally minimal envelopes.

Civic records data quality backfill

Source URIs, normalized record IDs, and corrected timestamps have been backfilled across civic records in the data catalog. Specifically, records now carry proper provenance URIs, identifiers are consistently formatted, and future-dated timestamps have been corrected. If you export civic records for audit purposes, your audit packages will reflect cleaner, more traceable data without any action on your part.

APRS envelope applied automatically on new civic ingestions

New civic records from Chicago ELMS and YouTube sources are now wrapped in the APRS data envelope at ingestion time, so they arrive fully compliant without waiting for a backfill job. This means fresher compliance coverage and fewer gaps in the envelope coverage dashboard.

Polished Layer landing page

The Layer landing page has been refreshed with smoother animations and more interactive elements. The hero section now features animated text and ambient gradient effects, pricing cards respond to mouse movement with a subtle 3D tilt, and call-to-action buttons have a magnetic hover effect. These changes make the page feel more responsive and give you a better first impression of the platform before signing in.

Refreshed product brand marks

All four product logos — Layer, Overwatch, Codex, and Locus — have been redesigned with bolder, more distinct silhouettes. Each mark now has a unique shape that's easier to distinguish at small sizes, such as in the navigation bar and favicon contexts. You'll see the updated marks across Axiomancer.io and in the cross-product navigation bar.

Docs link in the navigation bar

The Axiom navigation bar at the top of every product now includes a direct link to the documentation. This makes it faster to jump to API references, guides, and changelogs without leaving your current workflow.

Custom 404 page

Visiting a broken or outdated link on Axiomancer.io now shows a designed 404 page with navigation shortcuts back to each product, instead of a generic error screen. This helps you find what you're looking for faster when a page has moved.

Interactive constellation hero

The Axiomancer.io hero section now features an interactive constellation field that responds to your cursor. This is a visual-only enhancement — the constellation particles connect and drift as you move your mouse, adding a more dynamic feel to the landing page.

Port authority governance data

Codex now ingests structured governance data from five major US port authorities — Oakland, Long Beach, Los Angeles, JAXPORT, and the Port Authority of New York and New Jersey. Board meeting agendas, minutes, resolutions, and attachments are collected automatically and stored with full APRS envelope compliance. Each port uses a purpose-built adapter that understands its specific publishing format (Legistar, Granicus, or custom CMS), so records arrive normalized and ready for cross-port queries. See the data catalog for the full list of port authority tables.

Tariff version tracking and diff engine

Codex now tracks port tariff documents across revisions and automatically detects rate changes between versions. When a new tariff is published, the platform extracts individual line items and compares them against the previous version — flagging new, modified, and removed items with full supersession linkage. JAXPORT tariffs are supported at launch, with additional ports to follow. This gives you a structured, auditable view of port pricing changes over time without manually comparing PDF documents.

AI-enriched agenda classification

Port authority agenda items are now automatically classified using AI into categories like tariff changes, lease actions, capital projects, contract awards, and procurement — along with extracted counterparty names and terminal locations. This makes it easier to filter governance records by action type and quickly find the items that matter to your workflow.

Claim and fact separation for governance records

Port authority records now use the claim/fact layer to separate what was proposed (staff recommendations, agenda items) from what was decided (board votes, adoption outcomes). This distinction makes it straightforward to query for approved actions versus pending proposals, and feeds downstream compliance and audit workflows.

In-app chat now available in Locus

The live support chat previously available in Layer is now available across Locus as well. When you're signed in, the chat widget identifies you automatically for faster support. Anonymous mode is also supported for pre-login questions.

Flood exposure data cleanup

Removed 97,000 orphan NFIP flood claims that had no date information and were skewing cell-level risk scores. A new validation constraint prevents dateless records from being ingested in the future, so flood exposure scores are now based entirely on properly dated claims.

Security hardening

Resolved several API authentication and input validation issues across the platform. Rate limiting is now more resilient to transient errors, filter parameters are sanitized against injection, and internal diagnostic endpoints require proper authentication. These changes strengthen the platform's security posture — no action is required on your part.

Verified in-app support chat

The in-app support chat now verifies your identity when you're signed in, so support conversations are automatically linked to your account. This means faster resolution — the support team sees your workspace and plan context without asking you to identify yourself. Unauthenticated visitors on the marketing site still have access to anonymous chat.

More reliable vessel visit tracking

Fixed an issue where concurrent AIS events could create duplicate open vessel visits at the same port, leading to phantom "in port" records that departure events couldn't close. A uniqueness constraint now prevents duplicate visits at the database level, and departures correctly close all matching records. If you noticed vessels stuck in an "in port" state, this should resolve it.