Platform · Argus

Argus

Mission replay & after-action analysis.

Reconstruct real-world operations from telemetry and event logs — ground patrols, drone missions, maritime interdictions, strike sorties, logistics convoys. Argus parses CSV or JSON mission data, replays it on a map with a scrubbing timeline, and lets operators step through every event, annotate findings, and export an after-action package.

Overview

What Argus Does

replay

Argus is a mission-replay environment built for after-action analysis of real-world operations. Operators upload a mission log — CSV or JSON, with timestamps, coordinates, event types, and arbitrary metadata — and Argus parses it into a normalized timeline. The result is a control-room console where the full mission can be replayed at variable speed, paused at any moment, and inspected event by event.

Where after-action review traditionally lives in spreadsheets, screenshots, and disjointed log files, Argus consolidates everything into one synchronized view: a dark-mode map with an animated trail, a timeline scrubber with per-event ticks, an event feed grouped by type and severity, and a detail rail with annotation. Operators can jump to the next or previous event with a keystroke, scrub to any moment in the operation, and attach time-anchored notes that persist with the mission record.

Argus is built for organizations whose operations leave a structured trace — UAS sorties, security patrols, logistics routes, maritime interdictions — where understanding what happened, when, and in what order is the difference between a clean debrief and an unanswered question.

Modules

Core Modules

upload_file

Mission Ingest

CSV or JSON parser with forgiving field aliasing. Accepts timestamp, lat/lon, type, and arbitrary metadata. Unknown columns fold into metadata so nothing is lost. Anomaly detection flags telemetry gaps and impossible jumps at parse time.

CSV / JSON Anomaly Flags
map

Map Replay

Dark-mode tactical map with full path drawn dim, an animated trail-so-far that flows forward as time advances, a pulsing live position marker, directional chevrons indicating heading, and clickable colour-coded event markers tied to the timeline.

Animated Trail Heading Chevrons
timeline

Timeline Scrubber

Play, pause, scrub at 1× / 2× / 5× / 10× / 25× speed. Per-event ticks coloured by type, hover preview with summary, click to jump. Annotation pins surface above the rail. Keyboard transport keeps hands off the mouse during a debrief.

Variable Speed Keyboard Transport
list_alt

Event Feed

Chronological list of every discrete event, colour-coded by type and severity, with the active event tracked as the timeline advances. Per-event icons distinguish system checks, commands, sensor contacts, weather alerts, weapons release, and routine telemetry milestones.

Severity Colour Auto-scroll
search

Event Inspection

Detail rail showing event type, exact timestamp, coordinates, full metadata table, anomaly badges, and the relative offset to the previous event. Operators can step previous/next through the discrete event sequence with a single keystroke.

Metadata Table Relative Offsets
edit_note

Annotations & Export

Time-anchored notes attach to any event and persist with the mission record. The full mission — events, telemetry, anomalies, annotations — exports as a single re-uploadable JSON file, suitable for archival or handoff to the after-action package.

Time-anchored Notes JSON Export
Architecture

Technical Specifications

developer_board
Frontend

Next.js (App Router) with Tailwind. Single-page replay shell composed of four panels — map, timeline, event feed, detail rail — sharing one authoritative time cursor driven by requestAnimationFrame. Map renders Leaflet with dark CARTO tiles.

Backend

Next.js API routes on a Node runtime. PrismaORM over MySQL. Mission ingest accepts files up to 25 MB / 250,000 events per mission — comfortably enough for ~70 hours of 1 Hz telemetry per replay.

Database

MySQL via Prisma. Tables: User, Mission, Event, Annotation. Mission ownership scoping is enforced at every read; no cross-tenant leakage paths.

Authentication

NextAuth credentials provider with JWT-only cookie sessions. bcrypt-hashed passwords. Session token cookie marked HttpOnly, SameSite=Lax, and Secure in production.

Parser

Forgiving CSV (PapaParse) and JSON parsers with field aliasing — time/datetime for timestamp, latitude/y for lat, event_type/kind for type, etc. Anomaly pass marks gaps >30s and jumps >1 km/sec.

Export

Full mission round-trip JSON export including events, anomalies, and annotations. Output re-uploadable through the same ingest pipeline — mission archives travel as a single file.

Security

Security & Compliance

shield
cloud_off

Data Sovereignty

Mission data is held in the customer’s own database. No third-party telemetry, analytics, or cloud-routed payloads. Self-host beside Atlas or run as a SaaS instance.

manage_accounts

Session Security

NextAuth credentials with bcrypt-hashed passwords. JWT-only cookie sessions, HttpOnly + SameSite=Lax + Secure in production. Sessions expire on the configured window.

history

Audit Logging

Every annotation captures author and timestamp. Mission-level audit trail of who imported, opened, exported, or deleted a mission record.

lock

Mission Isolation

Mission ownership is enforced at every read. A user only sees missions they uploaded; cross-user access is impossible without an explicit role grant.

Get Started

Replay your missions in Argus

Argus is available as a hosted SaaS instance and as a self-host package. Bring an existing CSV/JSON mission log to evaluate the replay quality against your operations data, or request a guided demonstration with a sample drone or maritime mission.