Autonomous defence · End to end

We buildautonomousdefencesystems.

Things that should be autonomous. Built end to end, in-house.

See the catalog
OL·0001  Jetray — interceptor
Scroll ↓

The catalog · Built under one roof

01The catalog · Built under one roof
OL · 0001Counter-UAS

Jetray

A high-speed interceptor for counter-UAS work — autonomous detection, tracking, and pursuit in a two-kilogram airframe.

  • Top speed200–250 km/h
  • Range6 km · 3 km AGL
  • Airframe2 kg · 500 g payload
Jetray — interceptor, halftone plate
OL·0001
OL · 0002Robotics

Cylo

Force-sensing, compliant actuators for humanoid and quadruped joints. Built in-house because robots that share space with people need joints that can feel, not just move.

  • StatusRev C · integration
  • Peak torque180 N·m
  • Control loop1.2 kHz
Cylo — Robotics, halftone plate
OL·0002
OL · 0003AI swarming GCS

Cortex

The AI swarming ground station. One operator tasks the fleet in plain language — a deterministic guardian vetoes anything unsafe, and missions keep flying when the link drops.

  • StatusIn development
  • StacksArduPilot · PX4 · MAVLink 1/2
  • SafetyDeterministic veto
  • Link lossMission continues
OL·0003

How we work · Small team, narrow scope

02How we work · Small team, narrow scope
§1

One building.

Mechanical, electrical, firmware, and software under the same roof. Fewer hand-offs, shorter feedback loops.

§2

Real artifacts first.

We build things that fly, turn, and run. Papers, decks, and demos come after — if at all.

§3

Right tool, right layer.

Edge autonomy when the link drops. Hardware we build end to end. The right layer for the mission, not the demo.

§4

Small team, narrow scope.

We pick a short list of problems and go deep. Everything else we say no to.

Questions

03Questions

Autonomous defence systems, end to end — the airframes, the actuators, and the autonomy that flies them. Jetray, Cylo, and Cortex are the current catalog.

One building in Bangalore, India. Mechanical, electrical, firmware, and software under the same roof.

Email akash@otonomy.ai — requests go straight to the engineers.

Yes — mechanical, firmware, and ML. Same address.