Building an engine is rarely the shortest route to shipping a product. For Bunzed, however, the engine is not an implementation detail. It is the common layer beneath everything we want to make.
A renderer we can shape
Bungine uses Rust and wgpu to target Vulkan, Metal, and DirectX 12 through one modern graphics API. Owning the layer above that API gives us control over the scene model, resource lifetime, frame scheduling, and development loop.
That control matters when the same renderer needs to serve games, native interfaces, and eventually specialized hardware. A general-purpose engine can support each use case, but it cannot make our particular tradeoffs for us.
The cost is the point
An engine creates work: tooling, documentation, platform support, and countless small systems that mature engines already provide. We are not ignoring that cost. We are choosing it because those systems are where the product becomes distinct.
The goal is not to rebuild every feature. It is to build the smallest coherent foundation that can grow with all three products.