armory3d/armory

3D Engine with Blender Integration

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 12 minutes ago
Added to GitGenius on September 20th, 2026
Created on October 29th, 2015
Open Issues & Pull Requests: 399 (+0)
GitHub issues: Enabled
Number of forks: 353
Total Stargazers: 3,339 (+1)
Total Subscribers: 147 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 15.9 days
Mean response time: 208.4 days
90th percentile: 853.6 days
Tracked items: 49

Most active contributors

Sign in to see contributor activity.

How this project is maintained

87% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "bug" is answered fastest, typically in about 8 days, while "feature request" waits about 2 months. Three people close 67% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 46
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 886 days
Stale 30+ days: 45
Stale 90+ days: 6

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 1

Top labels

  • bug (34)
  • feature request (23)
  • good first issue (1)
  • logic nodes (1)

Most active issues this week

Detailed Description

Armory is a 3D game engine with deep Blender integration that compiles projects to multiple platforms while maintaining a minimal footprint.

The engine addresses the need for a game development pipeline that keeps artists and developers working within a single tool. Rather than exporting assets between separate applications, Armory functions as a Blender add-on, allowing creators to build, script, and deploy games directly from Blender. The renderer supports both deferred and forward rendering paths and is fully scriptable, giving developers control over the visual pipeline. Projects compile to multiple target platforms from a unified codebase.

Armory suits developers and small teams who want to minimize their toolchain and keep production within Blender's familiar environment. It is particularly valuable for projects where portability across platforms matters and where keeping executable size small is a constraint. The engine's focus on performance and minimal footprint makes it suitable for deployment on resource-limited targets. Teams already invested in Blender workflows will find the integrated approach eliminates friction in the asset pipeline.

The project maintains active development with regular releases and an established community forum for support. Documentation is available through a wiki and release notes are published consistently. The codebase shows ongoing refinement across its core systems, with contributions addressing both engine capabilities and the Blender integration layer.