CRESTMOOR STS

Sovereign Tactical Solutions | Rochester, New York

One mission layer for every carrier

Crestmoor STS builds Sentry, an edge architecture that lets mixed vehicles, sensors and unmanned systems work as one network, and an arbitration layer that keeps a person in command of consequential decisions.

The Sentry stack

  • NodeEdge compute and sensor I/O
  • OSPerception, mapping and mission services
  • MeshShared state, node loss and resync
  • LinkOpen adapters to vehicles, radios and operators
Wheeled and tracked robotic hosts beside a relay, supervised by an operator.
Concept visualization: planned mixed-host demonstrator with a relay node.

Sentry

An architecture first, a vehicle second.

Platform independent

Mission logic, data structures and operator workflow move between carriers. Platform differences stay in an adapter layer.

Local first

Each node senses, estimates state and maps at the edge. Weak links reduce coordination without stopping basic operation.

Team of machines

One operator supervises a mixed group through a single view instead of steering each machine by hand.

Built on open interfaces

Documented adapters let radios, sensors, positioning sources and compute modules be swapped without redesigning the system.

Block diagram: Node (edge compute and sensor I/O) feeds OS (perception, mapping, mission services) and Mesh (shared state, node loss and resync). OS and Mesh connect to Link (adapters to hosts, radios and operators), which connects to Host A and Host B (compatible vehicles) and an operator under human supervision.
  1. Node. Edge compute and sensor I/O.
  2. OS. Perception, mapping and mission services.
  3. Mesh. Shared state, node loss and resync.
  4. Link. Adapters to hosts, radios and operators.
  5. Connected to. Host A and Host B (compatible vehicles) and an operator providing human supervision.
  6. Note. Lines represent illustrative interfaces; local processing remains at each node.
Conceptual Sentry architecture overview; interfaces are illustrative.
Concept edge-compute enclosure beside wheeled and tracked robotic carriers.
Concept visualization: common edge-compute integration across different hosts.

Arbitration

Threshold Arbitration Framework.

Flow diagram: a proposed action from the autonomy stack goes to arbitration review, which checks rules, conditions, risk and uncertainty. Three outcomes follow: proceed within authorized scope, pause when conditions require a hold, or human review, where an explicit decision is required.
  1. Proposed action. From the autonomy stack.
  2. Arbitration review. Rules, conditions, risk and uncertainty.
  3. Outcome 1: Proceed. Within authorized scope.
  4. Outcome 2: Pause. Conditions require a hold.
  5. Outcome 3: Human review. An explicit decision is required.
  6. Consequential decisions remain under human authority. Illustrative flow only.
Illustrative arbitration outcomes; internal thresholds are not shown.

Uses

Non-weaponized mission packages.

Reconnaissance

Persistent local sensing, route scouting and distributed observation.

Force protection

Perimeter patrol, remote sensor nodes and alerting around fixed or mobile sites.

Robotic carrier transporting secured equipment cases under human supervision.
Concept visualization: equipment movement in a controlled setting.

Logistics support

Unmanned movement of equipment and supplies in controlled settings.

Tracked inspection rover near industrial piping with an engineer supervising.
Concept visualization: supervised infrastructure inspection.

Inspection and response

Infrastructure inspection, site assessment and disaster response with mixed robotic teams.

Status

Where each piece stands today.

ItemState
Sentry architecture and test planDefined
Integrated prototypeNot yet built; none is claimed
First demonstratorPlanned: two dissimilar hosts and a relay node, built from commercial parts
Arbitration doctrineWritten; field validation not claimed
Open-architecture standardsDesign direction only; no conformance claimed

Partners

Who we are looking for.

Two engineers examining a sensor assembly and a technical sketch.
Concept visualization: collaborative sensor-integration work.

Leadership

The people behind the work.

Portrait of Eugene Thomas

Eugene Thomas

Founder and Chair

Eugene founded Crestmoor in 2025 and leads the company's technical direction and strategy. A U.S. Navy veteran who served as a Hospital Corpsman on operational deployments, he later worked as a Security Protective Officer with the Central Intelligence Agency.

He brings a decade of hands-on experience in electrical systems, industrial mechanics and maintenance, HVAC and refrigeration, and carpentry, with coursework in computer systems technology. That background shapes his approach to electromechanical integration, fault diagnosis, serviceability and the physical demands of robotic hardware.

Portrait of John Love

John Love

Technology Innovator

John is an independent technology innovator and hands-on mechanical professional with a lifelong interest in robotics, automation and emerging technology. He develops original robotics and mechanical-systems concepts and organizes them into product plans for discussion with technical, manufacturing and business partners.

His practical background includes manufacturing, generator systems, plumbing, mechanical troubleshooting, quality control and team supervision.

Contact

For partnerships, pilots and technical collaboration, write to Eugene Thomas, founder.

ejt@crestmoorsts.com

Crestmoor STS is a division of Crestmoor Defense LLC. crestmoordefense.com