SYNTHMIND

Pterops OSFrom mission intent to recorded outcomes.

The execution foundation for human-supervised aircraft missions: verify signed requests, supervise operations and preserve the mission record.

Discuss Pterops OS
Pterops OSHuman-supervised execution

  1. Verify authority

    Check signed requests against approved permissions and operating constraints.

  2. Supervise execution

    Connect accepted operations to the autopilot and monitor their progress.

  3. Review outcomes

    Preserve command activity and telemetry for a traceable mission record.

Approved intent Supervised operations Recorded outcomes

Product overview

Pterops OS,
at a glance.

Updated

Purpose
Verify mission requests, supervise bounded execution and record outcomes alongside an aircraft’s autopilot.
Who it is for
Aircraft operators, integrators and engineering teams assessing human-supervised mission execution with their own fleets.
Workflow
Check signed requests and approved authority, translate accepted operations for the autopilot, monitor execution and retain journals for review.
Evaluation
Discuss your requirements and an evaluation approach with Synthmind.

Your aircraft.
Your operating environment.

Pterops is being developed around documented interfaces and modular components, enabling assessed integrations with customer aircraft, payloads and operational systems.

Start with the fleet you have

Your aircraft, payloads, communications and ground systems shape the integration. We start with your mission requirements and agree the interfaces, constraints and acceptance process.

Discuss integration with your fleet

Clear responsibilities

Pterops OS handles mission-request verification, supervised execution and recorded outcomes. Your autopilot retains stabilisation, state estimation and low-level flight control.

Technical architectureComponents, interfaces and licensing
Pterops architecture: a test signing harness connects to Node and a simulated ArduCopter. Dotted connections from Control and Fleet through Authority are planned. Core supplies shared contracts and libraries.
Architecture overview · solid: exercised in simulation · dotted: planned

Pterops OS spans onboard software and ground services. Node is intended for a Linux companion computer.

Agent & admission
Checks signed requests, permissions, freshness and replay protection.
Gateway
Connects to the autopilot, translates accepted operations and journals command activity.
Monitor & navigation integrity
Assesses operating limits and navigation reports, and requests recovery when appropriate.
Supervisor
Manages process health and health-token signalling. Deployment integration and application isolation remain unfinished.

Shared foundations

Pterops Core supplies shared message definitions and signing/verification libraries. It is a code foundation, not a central server through which commands pass.

Ground services

Authority is the planned backend for preparing, signing and dispatching approved requests. Control provides the operator interface. Fleet supplies readiness records and does not command aircraft.

Open architecture & licensing

Open architecture does not mean universal aircraft compatibility or an entirely open-source platform. The licensing plan includes Apache-2.0 contracts, SDK bindings and simulator tooling; Node, Authority, Control and product applications are proprietary. Public source releases and technical documentation are not yet available. Contractual source access for audit is a separate arrangement.

Integration & availability

Current stage: Pterops OS is development software, demonstrated with a single ArduCopter in software-in-the-loop simulation. Physical-flight validation and production integration with Pterops Control and Fleet remain pending.

Read the technical evidence

Discuss integration
with your fleet.

Start an integration enquiry