Bevy
Bevy is “a refreshingly simple data-driven game engine built in Rust” — “Free and Open Source Forever” (MIT/Apache-2.0, community-supported, “no license fees, no sales cuts”). It extends this spoke beyond the standalone engines on two of its open-question axes: a Rust/ECS architecture and a code-first model adjacent to the framework-based engines (flame-engine). Source: bevy.org.
Defining architecture — ECS
Bevy ECS (Entity Component System): “Components are Rust structs, Systems are Rust functions,” “Massively Parallel and Cache-Friendly.” A data-oriented design distinct from the object/scene-tree model of godot-engine or unity-engine. Does both 2D and 3D via a modular, backend-agnostic Render Graph.
Positioning
Code-first and community-driven — closer to a framework you program against (like flame-engine/Phaser) than an editor-centric standalone engine, while still doing 3D. Bets hard on iteration speed: “With Bevy you can expect 0.8-3.0 seconds with the ‘fast compiles’ configuration” against 30+ seconds for other Rust engines, plus hot reloading — the same leanness/iteration axis the unity-vs-godot-comparison surfaced, here via Rust. The Rust counterpart to Godot’s open-source-with-low-overhead positioning.
Re-verified 2026-08-12 against the live front page. The compile-time claim stands and the licence is now stated as “100% free. Forever and always. Open Source under the permissive MIT or Apache 2.0 licenses.” Two changes worth recording. The front page no longer says anything about an editor, so this page’s earlier “editor still in progress” parenthetical had no live source behind it and has been dropped rather than updated — whether the Bevy Editor shipped is now an open question here, and answering it needs the release notes, not the landing page. And the feature list has grown into engine territory: skeletal animation with blend shapes, a flexbox UI framework, scene save/load with hot reloading, audio, and cross-platform targets down to iOS/Android and the web. On the library-versus-engine split this spoke drew for the browser stack (pixijs → babylonjs → playcanvas), Bevy’s own claims now sit at the engine end.
Related
godot-engine · flame-engine · o3de · unity-engine · unity-vs-godot-comparison