ARCFORGE // OPERATIONAL AUTONOMY PLATFORM

ROS is DOS.We're building the Windows.

The operational lifecycle and assurance layer for autonomous systems. One workflow to field, supervise, and trust drones, ground robots, and swarms — running today on real ArduPilot hardware, no companion computer required.

Request NDA access See it running

[0] GO AIR · GROUND · SIM · SWARM· 200+ GATES GREEN·SIGNED END-TO-END

ArcForge workspace — one platform across air, ground, simulation, and swarm

ARCFORGE // ONE PLATFORM, EVERY DOMAIN

The shift

ROS won DOS's war. It's stuck in DOS's UX.

ROS2 is the standard robotics runtime. The operator layer above it is still hand-assembled — a different tool for every stage of one mission, all built by engineers for engineers. In the field, the operator who needs the vehicle isn't a ROS developer. ArcForge is the layer that closes that gap.

The platform

The operator layer above robotics middleware.

ArcForge integrates ROS2, PX4, and ArduPilot — it doesn't replace them. Vendor-neutral by design: the same workflow runs across air, ground, simulation, and swarm, on whatever hardware you fly. We own the operator relationship, not the airframe.

ArcForge — operator lifecycle & assurance layer

Discover · Model · Rehearse · Deploy · Operate · Replay · Improve

▲ ONE OPERATOR SURFACE ▲

ROS2 · MAVROS · rosbridge

Robotics middleware — kept, not replaced

PX4 · ArduPilot · Pixhawk · Edge

Flight stack & hardware — integrated, not abstracted

The lifecycle

Seven verbs, one runtime.

Modules run underneath — ArcFlight, ArcGround, ArcSim, ArcSwarm — but the operator works in verbs. Improve feeds Discover; the loop closes.

Discover

Hardware maps itself

Model

Compose & save systems

Rehearse

Sim before the field

Deploy

Signed push to the edge

Operate

Contextual cockpit

Replay

Review what happened

Improve

The loop closes

Proof // running, not promised

Everything here is on real hardware.

A platform that gates commands when a vehicle isn't safe has to hold itself to the same bar. These are live captures, not mockups — and the states are real.

[0] GO · DISCOVER

Hardware maps itself

A real Pixhawk flight controller, auto-detected with provenance. The scan receipt is signed and written to the audit log — discovery you can prove later.

Discover — Pixhawk detected, scan receipt signed to the audit log

[!] NO-GO · FAIL-CLOSED

It refuses when it isn't safe

ArcForge blocks an unsafe configuration and names the blocker, instead of letting the vehicle act. A UI that lies is worse than one that fails.

Fail-closed safety gate — flight blocked with named blockers

[/] REPLAY

A black box reconstructed from telemetry

Recorded flight sessions replay as a synthetic reconstruction with assurance state and energy — zero raw video stored.

Replay — synthetic black box reconstructed from recorded telemetry

[0] GO · MODEL

Compose and save a system

The seven-verb workspace, live over the real system graph. Drones and rovers managed in the same surface.

Model — the seven-verb workspace managing drones and rovers

[/] DEPLOY

Honest readiness, not green-by-default

Deploy reports exactly what's ready and what isn't, and refuses to push until prerequisites pass.

Deploy — honest readiness checklist, refuses until prerequisites pass

[0] GO · SUPERVISE

ArcControl — supervisory command layer

A read-only common picture that proposes, never disposes. Oversight without taking the operator's hands off the controls.

ArcControl — read-only supervisory command layer

[0] GO · SWARM (in simulation)

Mixed-domain coordination, rehearsed in sim

Formation hold across a multi-vehicle wedge in ArcSim. Rehearsal runs in the same runtime as operations, so practice transfers to the field.

ArcSwarm — formation hold across multiple vehicles in simulation

Assurance

Trust from corroboration.

Provenance flows from physical parts to derived capabilities to a verdict on every observation. The operator gets one answer — GO, CAUTION, or NO-GO — and the reason behind it.

[!]

Fail-closed by default

If ArcForge can't confirm a subsystem is healthy, it won't say it is. Readiness refuses to advance under uncertainty — and names the check, threshold, or signal that blocked it.

[#]

Signed end-to-end

Ed25519-signed deploys, verified on the edge — signature plus every file digest. Custody is provable from the part to the capability.

[0]

200+ verification gates, green

Governance is enforced in CI, not just documented. Meta-gates verify the gate set itself; removing one requires a tracked defect ID.

[/]

Built for the field, not the lab

Designed for operators in demanding conditions, where readiness has to be earned each time rather than assumed.

ArcAssist — one reliability verdict: GO, CAUTION, or NO-GO

ARCASSIST // ONE VERDICT, WITH THE REASON

Posture

Defense-native. Dual-use. Export-disciplined.

US-PERSON

Built in the United States

US-person-owned and SDVOSB-eligible, founded by a medically retired U.S. Marine with defense policy and acquisition background.

CONTROLLED

Method held under counsel

Controlled technical data is managed under export counsel and an enforced disclosure registry. Capability is public; method is not.

DUAL-USE

One platform, both markets

The same operator and assurance layer serves defense operators and commercial fleets — air, ground, sim, and swarm from a single license.

Access // two channels

This page is the public half.

What you see here is capability-level and export-safe. Full architecture, additional mission-grade capabilities, and the technical data sheet are disclosed under NDA to vetted U.S.-person parties.

Request NDA access Contact admin@arcforge.tech · Pre-seed open · $1M SAFE