Derek Knox

While it’s flattering that @Unity called out @BeziHQ on its official Unity AI page, I’d like to point out some misinformation in the comparison. “It runs as a plugin alongside the Editor rather than inside it…” This has been an important design decision in how Bezi is architected as a desktop app (not just a plugin). We built our own proprietary indexing system to accurately understand project scenes and codebases, on top of the same functions that Unity itself uses to access project data, so Bezi actually supplies even more relevant context to the AI agent. “It's code-focused and doesn't natively drive the Editor…” Bezi natively drives the Unity Editor through Actions. Anything that Unity AI claims to do inside the Editor can be done by Bezi as well, at higher accuracy. Every Bezi user knows this, and it’s a big reason as to why a lot of game studios try both products and stick with Bezi long-term. Most importantly, the truth of the matter is that one product is truly AI-native from the ground up, and the other added an AI feature to an existing product. One reimagines game development at a higher abstraction level through an increase in creative leverage, and one fills in the gaps to make an existing workflow more efficient. One is pulling the future forward, and one is extending the past. Excited to see how this all plays out over the next few years.