Evidence-first anomaly radar

Global awareness.
Independent evidence.
Local relevance.

VIRON Signal federates authoritative public data, Android GNSS diagnostics, and sensor observations into one calm, transparent radar — showing confidence, provenance, and uncertainty alongside every event.

Join the beta Explore how it works
Android app Build verified Web app Build verified iOS In development
47 Watchful 4 active incidents · fixture

Demonstration data

A prioritization score, not a declaration of danger. Provenance stays visible beside every number.

The product

One radar. Multiple independent sources.

VIRON Signal collects, normalizes, and correlates observations from independent sources — showing you what happened, what is developing, and what remains uncertain.

Global event awareness

The platform normalizes official, scientific, sensor, and developing observations. Each event carries its source, evidence class, confidence, and possible explanations. Public views currently use labeled fixtures.

Implemented

Multi-source evidence model

Events can contain multiple independent observations from different source classes. Correlation raises confidence; it does not confirm cause. Every score exposes its components.

Implemented

Watch Zones

Define geographic areas you care about. Watch Zones filter the global signal to what is locally relevant — matching incidents by category, severity, confidence, and distance from your area.

Android · local storage

Mobile application

Android app delivering the full radar — Global Status, Radar map, developing hunts, GNSS Scanner, Watch Zones, and Source Status — built in Flutter. iOS in development.

Android build verified iOS in development

GNSS anomaly Scanner

User-started Android sessions that measure satellite count, signal quality, clock behavior, and pseudorange consistency. Contribution is off by default and requires explicit per-session consent.

Local mode device-tested Contribution gated

Active Hunts

Events that are developing or correlated but not yet authoritatively explained. The hunt shows competing explanations, calm factors, and how new evidence changes confidence over time.

Implemented

Incident + evidence model · demonstration

Serious when confirmed. Curious when unexplained.

Every event separates confidence, severity, novelty, and impact. These cards use fixed demo fixtures — not current events.

Official factConfirmed05:12 UTC

Moderate earthquake in the Adriatic

A reviewed magnitude 5.2 earthquake fixture. Source precision and attribution remain visible alongside the score.

Confidence96
Severity47
Novelty66
Impact38
Algorithmic anomalyCorrelated07:22 UTC

GNSS conditions degraded north of Ljubljana

Four independent fixture sensors aligned. The cause is not confirmed; interference, weather, and receiver issues remain competing explanations.

Confidence72
Severity54
Novelty81
Impact43
Community reportUnverified07:29 UTC

Community boom reports under review

Private demonstration reports await moderation or independent correlation. Low scores and unverified state are shown, not suppressed.

Confidence24
Severity22
Novelty39
Impact13

Demonstration data Fixed fixture incidents generated 28 July 2026 · not current conditions

Source network

Every source labeled. Every state honest.

Browse source registry

VIRON Signal maintains a global federation of public, scientific, and first-party sources. Each source carries an explicit implementation state — reflecting what has actually been built and verified, not what is merely planned.

LIVE / IMPLEMENTED

No external provider is live or enabled in the public product. Implemented adapters remain operator-gated and fail closed.

  • NOAA SWPC adapter — implemented, disabled
  • USGS network path — implemented, shadow-only, disabled
SHADOW / VALIDATION

Durable earthquake observations and correlation are engineering-validation paths only. They cannot create confirmation, legacy incidents, or Global Status changes.

  • USGS durable shadow ingestion — disabled
  • Wave 1 correlation — explicit command only
REVIEW-GATED / PLANNED

Registry identification is not implementation. EMSC and GEOFON have deterministic parser/storage foundations, but no runnable network poller. Other candidates remain research entries.

  • EMSC SeismicPortal — network policy review required
  • GEOFON / GFZ — network policy review required
  • Additional worldwide sources — registry research only
DEMO / FIXTURE

Deterministic local incidents and federation records keep the site and app demonstrable without provider calls. Every fixture view is labeled and must not be read as current conditions.

  • Marketing preview and evidence cards
  • Local federation registry and coverage fixture

The public marketing views use a bundled, incomplete fixture and make no browser request to a third-party provider. “Implemented” never means enabled, healthy, complete, or live-verified. No provider is currently enabled in production.

Earthquake correlation · experimental

Cross-catalogue comparison. Not a confirmation.

Shadow-only · beta

VIRON Signal includes an experimental earthquake correlation engine that compares stored USGS, EMSC, and GEOFON shadow observations to form candidate groups that may describe the same physical event.

Status Shadow-only. Results never alter Global Status, incident confidence, or public alerts.
Purpose Engineering beta for deterministic stored-fixture and repository evaluation. No live provider request is required.
Validation Deterministic test scenarios pass. This is not a seismological methodology or scientifically validated.
Confirmation Matching two catalogue records never confirms a real earthquake beyond what the source already states. Provenance remains separate.

Correlation is triggered by an explicit operator command, not automatically. All beta limits — time window, comparison budget, candidate ceiling, and command timeout — are engineering resource parameters, not science.

Illustrative fixture
USGS · M5.2 · 05:12 UTC
EMSC · M5.1 · 05:11 UTC
GEOFON · M5.2 · 05:13 UTC
Shadow cluster · not confirmed

Three records, one candidate group, separate provenance. Correlation is a grouping hint, not a truth claim.

Watch Zones

Focus on what matters to you.

Define any number of named areas you care about — home, family, travel destinations. Watch Zones filter the global signal down to incidents that match your location, category, and severity preferences.

  • Define by name, radius, and category
  • Set minimum severity and confidence thresholds
  • Distance matching against the app's current incident data
  • Local signal level per zone
  • Enable or disable zones individually

Watch Zones are stored locally on your device. They are not synced across devices in the current release.

Ljubljana region Active
50 km radius · all categories · severity ≥ 30
1 match GNSS conditions degraded north of Ljubljana 12 km from zone centre
Local signal level 54

Demonstration data

GNSS anomaly Scanner

Receiver evidence, handled with restraint.

Scanner Mode turns your Android phone into a brief GNSS observer. It analyzes combinations of degraded satellite use, signal quality, clock discontinuities, and pseudorange-rate inconsistencies — with honest limits about what a single device can conclude.

User-started, foreground-only. Never silent or automatic in the background.
Contribution is off by default. Requires explicit per-session consent.
Anomaly-only upload. Normal windows, acquisition, and baseline never enter the contribution queue.
No exact position, no raw GNSS history, no stable device identity in any contribution payload.
Contribution transport remains disconnected until secure per-install credentials and production privacy controls are operational.
Scanner demonstration Read limitations
USER-STARTED SCANFixture
18visible
11used
27.8dB-Hz mean
3constellations

No anomaly detected. Satellite use and mean C/N0 remain above local baseline thresholds.

Contribution OFF (default)

Scanner sessions remain foreground-only and do not contact emergency services. One phone cannot confirm jamming or spoofing.

Mobile application

The full radar in your pocket.

Android · build verified
iOS · in development
Global Status
47 WATCHFUL
AnomalyGNSS degraded · Ljubljana
OfficialM5.2 · Adriatic
Radar
Scanner
18visible sats
27.8dB-Hz mean
Normalstatus
Contribution OFF
Watch Zones
Ljubljana region54
Home12
Sources
Fixture providersDEMO
USGSDISABLED
NOAADISABLED

Illustrative UI · demonstration data

What the app delivers today

01

Global Status

Aggregate signal level gauge with the strongest active incidents, confidence contributors, and calm factors.

02

Radar

Interactive map with incident markers, category filters, verification state, and severity slider.

03

Active Hunts

Developing and correlated events with confidence progress, competing explanations, and source evidence.

04

GNSS Scanner

User-started local satellite diagnostics with live metrics, anomaly monitoring, and privacy-safe export.

05

Watch Zones

Personal geographic areas with configurable matching and local signal level display.

Join beta updates

Android builds are verified for internal evaluation. No public store listing or iOS release is claimed.

How it works

One strange reading is a clue. Independent agreement forms a pattern.

Read the methodology

Observe

Authorized public sources, Android GNSS diagnostics, and receive-only Sentinel nodes contribute bounded observations.

Normalize

Provider-specific records become one versioned observation model with time, source, evidence class, and attribution.

Correlate

Independent modalities, tight timing, and regional agreement can raise confidence. Correlation is never confirmation.

Score

Confidence, severity, novelty, and impact stay separate. Possible causes and calm factors remain visible beside every number.

Deliver

Watch Zones filter global signals to local relevance without fear-driven frequency or manufactured certainty.

VIRON Labs

Building technology that earns trust under pressure.

VIRON Labs is an independent technology company focused on sensing, situational awareness, and privacy-conscious data systems. VIRON Signal is the public-facing intelligence layer — a global anomaly radar designed to be useful without being sensational.

Signal is part of a broader VIRON technology ecosystem that includes hardware sensor research, RF measurement, and privacy-preserving contribution infrastructure. We build for reliability, not reaction.

Evidence before certainty

Every claim is anchored to its source, evidence class, and confidence. No number appears without an explanation of how it was derived.

Fail closed by design

Provider outages, missing data, and API errors degrade gracefully. A data gap never becomes a false calm or a false alarm.

Privacy as architecture

Contribution payloads exclude exact position, raw telemetry, stable device identity, and session history. Privacy is structural, not a policy statement.

Trust model

No mystery score without visible evidence.

Corrections, stale sources, competing explanations, and dismissed incidents are first-class product states.

01

Provenance

Source, attribution, evidence class, observation time, and freshness travel with every normalized observation.

02

Uncertainty

Confidence and verification are distinct. Unverified community reports remain labeled and private until moderation or independent correlation thresholds are met.

03

Correction

Explained, dismissed, stale, and expired states remain visible instead of being silently erased. Corrections are not hidden.

04

Privacy

GNSS contributions exclude exact location, raw measurements, and stable device identity. Consent is per-session, off by default, and can be revoked at any time mid-session.

What the Scanner application payload contains

Included

  • Broad 4-character geohash (~±20 km)
  • 15-second-bucketed event times
  • Anomaly lifecycle and category
  • Aggregate C/N0 statistics
  • Random session pseudonyms (reset each session)
  • Explicit consent grant time and notice version

Excluded

  • Exact latitude and longitude
  • Prior cell history or route
  • Raw per-satellite measurements
  • Diagnostic JSON export
  • Native GNSS session identifier
  • Stable device, installation, or account identity
  • Device model, OS version, app version
  • IP address, User-Agent, or cookies as payload fields

Experimental features and their limits

FeatureStatusWhat it does not do
Earthquake correlationShadow-onlyDoes not alter Global Status, incident confidence, or any public output
GNSS contributionTransport gatedUpload disabled until secure credentials and privacy controls are operational
Community reportsModeration requiredNever promoted to a public alert without independent correlation or authority confirmation

Questions

Clear limits make a stronger radar.

Does VIRON Signal replace official emergency alerts?

No. Official alerts from recognized authorities remain clearly distinct — labeled as "Official fact" with full source attribution. Follow your local emergency services for urgent instructions. VIRON Signal does not contact emergency services.

Can Scanner Mode confirm jamming or spoofing?

No. An Android phone can surface receiver-level conditions worth reviewing — degraded satellite count, low signal quality, clock anomalies. Confirmation requires independent fixed sensors, technical investigation, and appropriate authorities. One phone never proves interference.

Is any live data available now?

Public event views currently use deterministic demonstration fixtures. Android Scanner can inspect supported receiver measurements locally, but no external event provider is enabled. NOAA and USGS network paths are implemented and disabled; EMSC and GEOFON network polling remains review-gated.

What is the earthquake correlation engine?

An experimental shadow-only feature that compares records across USGS, EMSC, and GEOFON catalogues to group likely matches of the same physical event. Results are for engineering evaluation only — they never alter public incident confidence, Global Status, or any user-visible score.

Do Watch Zones sync between devices?

Not in the current release. Watch Zones are stored locally on your Android device. Cross-device synchronization requires server-side storage not yet in production.

When will iOS be available?

The iOS project exists and the GNSS Scanner stub honestly reports the platform limitation. A production iOS build still requires CocoaPods initialization, signing configuration, and App Store review. No release date or App Store availability is claimed.