[ LIVE ]  /  Olympus OS · Cognitive Autonomy

Olympus OS

One OS to rule every domain.

Orbital  ·  Air  ·  Sea  ·  Subsea

ABRE Systems builds the operating system that makes autonomous systems survivable, interoperable, and lethal — across the entire defense ecosystem and into commercial markets.

Request Live Demo — Port Tampa Bay →Download Olympus OS Spec Sheet

Orbital

Running Olympus

Air

Running Olympus

Sea

Running Olympus

Subsea

Running Olympus

GALLOWS-01 · HDG 312° · GND 120 KTSREACT · 1.8sTAK · PUBLISHEDCLOUD CALLS · 0

[ 001 ] The Problem

Defense doesn't have a platform problem. It has an integration problem.

Every domain has different hardware, different stacks, different primes. Nothing talks. Nothing scales. Programs die in the Valley of Death.

Different hardware

Per-domain silos

Different stacks

No shared kernel

Different primes

No interoperability

Valley of Death

Programs stall pre-fielding

[ 001b ] The Solution

Olympus is the mission infrastructure layer.

Olympus is not an autonomy package. It's the mission infrastructure layer that sits above any vehicle.

01

One Kernel, Four Domains

The same core OS runs a satellite bus, a UAV, a USV, and a UUV — one kernel, one common operating picture.

02

Hardware Agnostic

We build our own reference platforms to prove it, but Olympus ports to your hardware and your existing fleet.

03

Defense-Native, Commercial-Ready

Built for contested, denied, unjammable ops — which makes commercial applications in offshore, logistics, and space trivially reliable.

[ 001c ] Business Model

We are selling dominance as a software layer.

We are not selling boats. Hardware platforms are Platform Zero — living proof, not the product.

01

Olympus License

Per-vehicle operating system license across every domain we touch.

02

Olympus Fleet

C2, swarming, mission planning, and data — recurring SaaS on top of the kernel.

03

Olympus Integration

We port Olympus onto primes' and partners' existing programs to rescue and accelerate them.

[ 001d ] The Moat

Olympus is the deterrent.

Anyone can build a fast boat, a drone, or a subsea sled. No one else has a single OS that has navigated Orbital, Air, Sea, and Subsea in the real world.

Olympus is the deterrent. Speed is just what it enables.

[ 002 ] Why Olympus OS

Built for the edge of the mission.

01

Performance

Sub-two-second reroute at the edge. No cloud dependency, no round trip, no waiting on bandwidth to make the call.

02

Trust

TAK-native and zero-trust by design. Interoperable with joint force C2, hardened for contested environments.

03

Certification

Architected from day one for airworthiness, seaworthiness, and program-of-record certification pathways.

[ 003 ] Olympus OS

Sense. Think. Act. Share.

01

Sense

→

02

Think(React)

→

03

Act

→

04

Share

One continuous loop. Sensor fusion to decision to actuation to a distributed common operating picture — executed on the platform, in under two seconds.

Olympus OS · Live

Rolling 90-day window

Missions Executed

0

Avg REACT Time

0.0s

Cloud Calls

0/ mission

[ REACT · Alert → Action ]

Elapsed 0.0s · Budget 2.0s

0.0s

Alert

0.4s

Analyze

1.1s

Reroute

1.8s

Publish

AlertSensor cue detected on-platform.

AnalyzeOnboard model classifies + prioritizes.

RerouteNew track computed, control surfaces commanded.

PublishCoT message pushed to TAK network.

[ 004 ] Proving Ground

Port Tampa Bay. Real ships. Real current. Real RF noise.

Port Tampa Bay operational chart

Test Site · Active

27°57′10″ N · 82°26′35″ W

Ops Days / Year

312

Commercial Traffic

37M tons/yr

Largest port complex in Florida — bulk, container, ro-ro, cruise.

Contested RF

24/7

Persistent maritime, port ops, and coastal comms clutter — no synthetic tests.

SOFWERX Adjacency

MacDill

Minutes from USSOCOM and joint experimentation infrastructure.

Only autonomous stack tested daily in America's largest port complex. If it works here, it works in the fight.

[ 005 ] Reference Platforms

REFERENCE PLATFORMS

One OS across four domains. Hardware is Platform Zero — living proof, not the product.

  • OLYMPUS AZRAEL

    Orbital Reference Platform

    Orbital Reference Platform. Proves Olympus OS on-orbit: autonomous tasking, edge processing, and downlink into the same TAK picture the ground fights from.

  • OLYMPUS GALLOWS

    Air Reference Platform

    Air Reference Platform. Long-loiter VTOL that demonstrates the Olympus REACT loop in contested airspace — runway-independent, EW-resilient, TAK-native.

  • OLYMPUS SIREN

    Sea (Surface) Reference Platform

    Sea (Surface) Reference Platform. Long-dwell USV that runs Olympus in a working commercial port — dense RF, real traffic, real current.

  • OLYMPUS ABADDON

    Subsea Reference Platform

    Subsea Reference Platform. Deep UUV that proves Olympus in the hardest comms environment on earth — no GPS, no surface link, full autonomy.

[ 006 ] TAK-Native

Shows up on the tablet the operator already carries.

ATAK tablet showing a live GALLOWS-01 track and REACT reroute alert

Zero integration. Zero new UI.

Every Olympus event publishes as native CoT into the operator's existing ATAK / WinTAK / iTAK common operating picture. Tracks, alerts, and reroutes appear where the team already looks — no separate console, no cloud round-trip.

  • ///Native Cursor-on-Target (CoT) publisher
  • ///Federated to team, unit, and joint TAK servers
  • ///Coordinates and callsigns redacted in this view

[ 007 ] Mission Profiles

One OS. Four domains. Same loop.

Every profile below runs the same Olympus kernel. The vehicle changes. The domain changes. The operating system does not — and that is the product.

01

Orbital

Space-Based Cross-Domain Cueing

LEO · Denied theater, no forward ISR

A contested littoral goes dark to airborne ISR. Olympus OS runs on the Azrael bus, processing imagery on-orbit instead of downlinking raw pixels. It classifies a vessel of interest, publishes CoT straight into the joint picture, and cues the air and surface nodes below — no ground station in the loop.

Runs on

OLYMPUS AZRAEL

Outcome

On-orbit detect to operator CoT: under 2s. No cloud, no ground relay.

02

Air

Forward Base Perimeter

Austere operating location · No runway

An isolated support node has no airfield and no persistent ISR. Gallows launches from a two-person footprint and Olympus flies the mission: autonomous perimeter orbit, movement detection outside the wire, then reroute, loiter, and geolocate under active EW. The same REACT loop that runs in orbit runs here.

Runs on

OLYMPUS GALLOWS

Outcome

Runway-independent orbit. 5-minute cold start to on-station.

03

Sea

Port and Harbor Defense

Port Tampa Bay · Restricted channel

A small craft deviates from the commercial lane during a high-security transit. Olympus fuses radar and AIS on Siren and classifies the track as anomalous in under a second, then cross-cues Gallows for visual confirmation and pushes the alert to the watch commander's ATAK tablet. One OS arbitrates both platforms.

Runs on

OLYMPUS SIREN

Outcome

Alert-to-action: 1.6s. Operator verified, no manned launch.

04

Subsea

Seabed Infrastructure Watch

Coastal channel · No GPS, no surface link

A port authority needs continuous seabed monitoring without diver exposure. Abaddon runs a terrain-relative survey with no GPS and no link home — Olympus navigates, classifies seabed change, and holds the mission autonomously, then offloads through Siren on surfacing into the same C2 picture.

Runs on

OLYMPUS ABADDON

Outcome

24-hour autonomous coverage. Zero dive-team sorties.

/// Olympus OS is the constant. The platforms are Platform Zero — proof, not product.

[ 008 ] Integrations

Plugs into the stack you already run.

C2

TAK / ATAK

Native Cursor-on-Target publisher. Tracks, alerts, and reroutes appear directly in the operator's existing ATAK, WinTAK, or iTAK picture — no separate console, no retraining.

  • CoT ingest / publish
  • Team & joint server federation
  • No cloud round-trip

Autonomy

ROS

Onboard autonomy and sensor nodes run on a hardened ROS backbone, enabling rapid payload integration, simulation-to-reality behaviors, and third-party algorithm hosting.

  • ROS 2 nodes
  • Gazebo / SIL pipeline
  • Modular payload drivers

Flight Control

MAVLink

Standard MAVLink interface to flight controllers, payloads, and ground stations. Fly-by-autonomy with human-on-the-loop oversight and full telemetry backhaul.

  • Autopilot command & control
  • Telemetry & health streaming
  • Mission waypoint upload

Beyond LOS

SATCOM

Iridium, LTE-M, and tactical SATCOM failover keep Olympus assets reachable when line-of-sight RF is blocked or the fight moves past the horizon.

  • Iridium SBD / RUDICS
  • LTE-M failover
  • Tactical SATCOM ready

[ 009 ] Security & Compliance

Trusted by design.

01

Zero Trust

Olympus OS assumes no trust by default. Every asset, operator, and message is authenticated and authorized continuously, not once at the perimeter. Least-privilege access keeps the command picture limited to the people who need it.

  • Authenticated assets & operators
  • Continuous authorization
  • Least-privilege C2 access

02

Data Handling

Mission data is processed at the edge on the platform. No cloud dependency means no required data egress, no external aggregation, and sovereign control over sensitive information. Transit and rest protections are built into the architecture.

  • Edge-first processing
  • No required cloud egress
  • Encrypted transit & rest

03

Framework Alignment

The platform is built from day one to support NIST 800-171 and CMMC 2.0 certification pathways. Controls, audit logs, and supply-chain traceability are designed into the stack so program-of-record accreditation is a continuous outcome, not a late fix.

  • NIST 800-171 aligned
  • CMMC 2.0 pathway ready
  • Audit-ready control baseline

[ 010 ] Team

Operators. Engineers. Builders.

Brandon Harris

Co-Founder · Chief Executive Officer

Former Army Special Operations Senior Enlisted Leader and AFSPECWAR Mission Commander. Leads strategic vision, commercial scale, and Port Tampa Bay operations.

DUTIES

  • Strategic vision
  • Commercial scale
  • Port Tampa Bay operations

Gard Laeskogen

Chief Operating Officer

Commands HIL, Vulcan Forge integration, and the systems that bridge design to production. Former Norwegian SOF FSK Paratrooper. NTNU / Berkeley Cybernetics.

DUTIES

  • HIL command
  • Vulcan Forge integration
  • Design-to-production bridge

Connor Hogan

Chief Technology Officer

Owns absolute sovereignty in embedded C++ tracking and quantization. Ex-NASA, USAF DARPA, and ARES live airport programs.

DUTIES

  • Embedded C++ tracking
  • Quantization
  • ARES live airport

Admiral Lex Walker, USN (Ret.)

Co-Founder · President & Chief Strategy Officer

Retired U.S. Navy Admiral shaping ABRE's operational strategy, joint-force alignment, and long-horizon program direction.

DUTIES

  • Operational strategy
  • Joint-force alignment
  • Long-horizon program direction

Karin Layton

Co-Founder · Chief Quality Officer

Owns quality, safety, and certification — building the systems that carry ABRE platforms to program of record.

DUTIES

  • Quality
  • Safety
  • Certification

[ 011 ] Our Footprint

Built where the mission is.

ABRE Systems operates at the intersection of autonomy, defense, and commerce. Two nodes: engineering and proving ground in Tampa, defense programs and federal liaison in Arlington.

[ 012 ] Get in the loop

Two ways to move forward.

[ 01 ] Operational

Request Live Demo — Port Tampa Bay →

See Olympus OS run on real water, real RF, real traffic. Half-day on-site with the engineering team.

[ 02 ] Technical

Download Olympus OS Spec Sheet →

Architecture, interfaces, and performance envelope for integrators and program offices.

Headquarters

ABRE Systems Inc.
Port Tampa Bay
Tampa, Florida

contact@abresystems.com

Protected against automated submissions. No cloud dependencies required.