// MISSION_MANIFEST REV 2026.05/loc: [REDACTED]

Gentle
Weapons

AI infrastructure for contested environments.

Built for defense. Built for the edge. Built to run when the network doesn't, the power flickers, and the enemy is inside the wire.

> Three systems. One stack. Deployed on robotics, UAS, ground vehicles, and forward compute.
> Designed for disconnected, degraded, intermittent, and limited operations.
> In pilots with major players in defense autonomy. [ CONTACT FOR BRIEFING ]
Request_Brief
// NVIDIA JETSON ORIN///DDIL_READY///ITAR_AWARE_SUPPLY_CHAIN///SBOM / FIPS 140-3 TRACK///CMMC L2 ROADMAP///OTA_SIGNED_UPDATES///EDGE_FIRST_MESH///ROBOTICS / UAS / GCV///// NVIDIA JETSON ORIN///DDIL_READY///ITAR_AWARE_SUPPLY_CHAIN///SBOM / FIPS 140-3 TRACK///CMMC L2 ROADMAP///OTA_SIGNED_UPDATES///EDGE_FIRST_MESH///ROBOTICS / UAS / GCV///
// OPERATING_DOCTRINE

The battlefield doesn't care
about your cloud region.

§ 02 / 06
PROBLEM_01— OBSERVED
Autonomy ships stalled at the edge.

Model weights are easy. The platform underneath is where programs die. Kernel drift, CUDA breakage, unsigned updates, no rollback.

PROBLEM_02— OBSERVED
The network is the enemy.

EW, jamming, tethered ops, LEO gaps. Cloud-trained autonomy has no path home. Your mesh needs to form itself and heal itself securely without a horizon link.

PROBLEM_03— OBSERVED
Deployments are hand-soldered.

Shipping AI to 200 robots is not a "kubectl apply". It is firmware, weights, sensors, calibration, radios, OTA, and a rollback plan that works when the operator is wearing gloves.

// SYSTEMS_MANIFEST

Three systems. One stack.

A hardened base, a private network, and a deployment system. Engineered to interlock. Ship any one. Ship all three. Every layer is built from the ground up for a contested edge.

§ 03 / 06
#01PLATFORM · LINUXREADINESS: TRL-4
// PRODUCT_ID: gwos

GWOS

A Linux distribution purpose-built to run NVIDIA Jetson in production.

GWOS takes the Jetson family from developer kit drift to fielded, attestable compute. Immutable rootfs, A/B updates, signed OTA, kernel-locked CUDA, purpose-built for reliability. The things you'd expect from a production OS, but tuned for autonomy payloads in a sealed enclosure three klicks from home.

> CAPABILITY_SET
  • [ OK ]Immutable, attested rootfs · A/B partitions · atomic rollback
  • [ OK ]Pinned CUDA / TensorRT / cuDNN stack · kernel lock-step
  • [ OK ]Signed OTA with delta updates over low-bandwidth links
  • [ OK ]TPM-backed boot, secure-element device identity, SBOM per image
  • [ OK ]FIPS 140-3 cryptographic track, CMMC L2 alignment roadmap
Request_AccessAVAILABILITY: LIMITED_PILOT
gwos.sh● LIVE
    ┌──────────────────────────────────┐
    │  JETSON ORIN / NX / NANO         │
    │  ┌────────────┐  ┌────────────┐  │
    │  │ GWOS KERNEL│  │ CUDA 12.x  │  │
    │  └────┬───────┘  └─────┬──────┘  │
    │       │  signed OTA    │         │
    │  ┌────▼────────────────▼──────┐  │
    │  │  IMMUTABLE ROOTFS · A/B    │  │
    │  └────────────┬───────────────┘  │
    │    attested boot · SBOM  · TPM   │
    └──────────────┬───────────────────┘
                   │
          [ FIELDED_DEVICES: ███ ]
$ gwos image build --target orin-nx --profile autonomy
$ → sbom.cdx.json written · 1,482 components
$ → signature: 0x7a3f..e901 · verified
$ gwos ota push --wave 1 --canary 3 --rollback auto
$ [ DEPLOYED: 3/3 · HEALTHY ]
#02NETWORK · EDGE_MESHREADINESS: TRL-4
// PRODUCT_ID: poolnet

Poolnet

An edge-first private mesh. Self-forming, encrypted, egress-optional.

Poolnet is what your autonomy fleet talks over when the LTE is jammed, the satcom is politely degraded, and the TAK server is three valleys away. A WireGuard-grade overlay that discovers peers, heals partitions, and lets you reach any node — from an operator laptop, a co-deployed drone, or a rack at home — without trusting the middle.

> CAPABILITY_SET
  • [ OK ]Self-forming mesh · peers discover and route without config
  • [ OK ]End-to-end encrypted links · per-node keypairs · short-lived certs
  • [ OK ]Partition-tolerant · continues operating without backhaul
  • [ OK ]Policy-driven egress · tether to cloud only when authorized
  • [ OK ]Radio-agnostic: LTE, Wi-Fi, mesh radios, satcom, direct-RF
  • [ OK ]Operator-in-the-loop ACLs · audit trail · time-boxed access
Request_AccessAVAILABILITY: LIMITED_PILOT
poolnet.sh● LIVE
      NODE_01 ─── NODE_02 ─── NODE_03
         \         │           /
          \        │          /
           \       │         /
            NODE_04 ─── NODE_05
                   │
          NODE_06 ─┴─ NODE_07
    ::::::::::::::::::::::::::::::::::
      link: p2p, encrypted, mesh
      egress: optional · tethered OK
      discovery: self-forming
$ poolnet up --identity node_04.key
$ → peers discovered: 6 · routes converged in 240ms
$ poolnet route --to fleet/uas-17 --via mesh
$ → link: p2p · enc: x25519+chacha20 · rtt: 38ms
$ [ BACKHAUL: OFFLINE · MESH: HEALTHY ]
#03DEPLOYMENT · CONTROL_PLANEREADINESS: TRL-4
// PRODUCT_ID: poolboy

Poolboy

A deployment system for next-gen AI workloads on autonomous platforms.

Poolboy is the control plane for shipping models and binaries to robots, UAS, and ground vehicles already in the field. Canary to a single host, widen to a wave, confirm per-node signatures, and roll back when regressions happen. Works over poolnet. Lands on GWOS. Treats every rollout like the live operation it is.

> CAPABILITY_SET
  • [ OK ]Fleet-scale rollouts · canary / wave / region targeting
  • [ OK ]Cryptographically signed, per-node acknowledged deploys
  • [ OK ]Atomic rollback to last-known-good on telemetry breach
  • [ OK ]Bandwidth-aware · resumable · works over intermittent links
  • [ OK ]Declarative autonomy manifests · weights, configs, sensors
  • [ OK ]Human-authorized go/no-go gates · two-operator control
Request_AccessAVAILABILITY: LIMITED_PILOT
poolboy.sh● LIVE
  [PAYLOAD] weights.safetensors   128MB
     │
     ▼  manifest_signed
  [POOLBOY] ──▶ POOLNET ──▶ N x GWOS
     │
     ├─ rollout: canary → wave → fleet
     ├─ rollback: last_known_good
     └─ ack: cryptographic · per-node

    TARGET_FLEET: ROBOTS / UAS / GCV
$ poolboy rollout submit ./autonomy_v2.manifest
$ → target: UAS_FLEET_NORTH · 142 nodes
$ poolboy gate approve --operator op_07
$ → wave 1: 3/3 · wave 2: 18/18 · wave 3: 121/121
$ [ ROLLOUT: COMPLETE · ROLLBACK: ARMED ]
// INTEGRATED_STACK
GWOS under foot. Poolnet between nodes. Poolboy on the rollout.
Request_Full_Spec
// DEPLOYMENT_VIEW

How it fields.

§ 04 / 06
schematic_v12 · integrated_stackscale: 1 : [REDACTED]
§ 1
ORIGIN
Operator · Program Office
  • Authoring
  • Two-operator gates
  • Policy authoring
§ 2
DISTRIBUTION
Poolboy + Poolnet
  • Signed rollouts
  • Encrypted overlay
  • Bandwidth-aware
§ 3
EDGE
GWOS on Jetson
  • Attested boot
  • Atomic rollback
  • Autonomy payload
CLASSIFICATION
UNCLASSIFIED // CUI AWARE
ENVIRONMENT
DDIL · JAMMED · AUTONOMOUS
OPERATOR LOAD
CLI + SIGNED MANIFESTS
FAILURE MODE
LKG ROLLBACK · NO-BRICK
// POSTURE

For the side
that calls it defense.

Gentle Weapons is an American company building the infrastructure layer for next-generation defense autonomy. Our customers are defense autonomy companies delivering capabilities to warfighters who have to make the software work in unpredictable environments.

We build one stack, for one mission: getting autonomous systems to survive and succeed in the places that matter.

DEFENSE_FIRSTUS_OWNEDITAR_AWARESECURE_SUPPLY_CHAIN
OPERATING_PROFILE
_X
HQ
[REDACTED] · UNITED STATES
FOUNDED
2026
HEADCOUNT
███ · GROWING
BACKING
STRATEGIC · PROGRAM-LED
PARTNERS
NVIDIA · DIU
ACTIVE PROGRAMS
AUTONOMY · ISR · GCV · C2
CMMC
L2 ROADMAP
> FIELD_USE_LOG
2026.03 · poolboy fleet rollout · OK
2026.02 · gwos image signed for [REDACTED] · OK
2026.01 · poolnet partition test · 6 nodes · OK
2025.12 · integrated stack live-fire exercise · OK
// OPEN_CHANNEL

REQUEST A BRIEFING WITH THE FOUNDER.

Defense autonomy startups, primes, and integrators: send a short note. We reply to qualified inquiries within 24 hours with a scheduling link to meet with the founding team.

§ 06 / 06
gw_brief.sh
_X
Transmitenc: aes-256 · xmit: outbound
> DIRECT_CHANNELS
press:    BY INTRODUCTION
> JOIN_US
We're hiring mission-driven production engineers, kernel / firmware specialists, and network software engineers. If you've shipped Linux at scale or operated systems in the outside world, we want to talk.
> NOTICE

This page is a public overview. Technical specifications, deployment references, and performance data are shared under NDA with qualified program parties.