DEPLOYDatabase

Brain

AeroVironment AVACORE

AeroVironment's open autonomy software architecture: a behavior-tree-based, airframe-decoupled stack paired with the Autonomy Retrofit Kit (ARK) edge-compute payload and SPOTR-Edge perception. Designed to be cross-platform; it underpins the Red Dragon one-way-attack UAS and is a named retrofit for the Puma family.

Framework · Maturity: Production · Closed · Powers 2 robots

Machine-readable surfaces

Key facts

Architecture
Behavior-tree-based, airframe-decoupled stack
System structure
Paired with Autonomy Retrofit Kit (ARK) edge-compute payload and SPOTR-Edge perception
Model type
Framework
Maturity stage
Production
Open source
No
Behavior-tree mission execution
AeroVironment's AVACORE datasheet says missions are defined by behavior trees that can be loaded at runtime to support adaptable autonomy (AVACORE datasheet).
Runtime plug-ins
AeroVironment says AVACORE plug-in interfaces can add waypoint planning, target detection, team behaviors, and other algorithms discovered at runtime (AVACORE datasheet).
Unmanned mission framework
AeroVironment describes AVACORE as an open framework with modular interfaces for autopilots, radios, sensors, and new unmanned-system platforms (AVACORE).

Developed by (1)

Powers (2)

Where AeroVironment AVACORE runs

View the global map

Deployments of robots powered by AeroVironment AVACORE, by place and type.

Free to use on your site, with a link back to DEPLOY.

Mentioned on (3)

Registry pages whose text names AeroVironment AVACORE.

Companies (1)

AeroVironment

Robots and products (2)

DriveMod, AeroVironment Puma

Common questions

What is AeroVironment AVACORE?
AeroVironment's open autonomy software architecture: a behavior-tree-based, airframe-decoupled stack paired with the Autonomy Retrofit Kit (ARK) edge-compute payload and SPOTR-Edge perception. Designed to be cross-platform; it underpins the Red Dragon one-way-attack UAS and is a named retrofit for the Puma family.
Which robots run on AeroVironment AVACORE?
2 robot models on the DEPLOY registry run on AeroVironment AVACORE: AeroVironment Puma, AeroVironment P550.
Who developed AeroVironment AVACORE?
AeroVironment AVACORE is credited to AeroVironment on the DEPLOY registry. Each developer attribution is verified via primary sources.
Is AeroVironment AVACORE open source?
No. AeroVironment AVACORE is recorded as proprietary on the DEPLOY registry. Model weights and source are not publicly available.
What type of AI is AeroVironment AVACORE?
AeroVironment AVACORE is a framework on the DEPLOY registry.
What is AeroVironment AVACORE's maturity stage?
AeroVironment AVACORE is at the production stage on the DEPLOY maturity ladder. Production stage means high-volume sustained commercial operations.

Sources (4)

  1. https://www.avinc.com/solution/avacore/
  2. https://investor.avinc.com/news-releases/news-release-details/av-unveils-new-ai-capability-and-autonomy-kit-unmanned-systems
  3. https://www.avinc.com/2025/05/06/av-unleashes-red-dragon-a-new-breed-of-fully-autonomous-capable-gps-denied-one-way-attack-unmanned-aircraft-systems/
  4. https://www.avinc.com/wp-content/uploads/2026/04/2025_AVACORE_Datasheet_250429_v05.pdf
Methodology: Verified · 4 sources (3 primary) · last reviewed 2026-10-09

Verification posture

Verified

High confidence

Review state

Stable

Last reviewed 2026-10-09

Maturity + lifecycle

Maturity stage: production

Sources by quality tier

3
primary-company-ir
Company IR disclosure
1
unclassified
Unclassified source

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for AeroVironment AVACORE.

Canonical ID 4dc07a38-a33e-4ec8-aae0-a17391c4db24