The author mentioned Unity in the README, but every other game engine I know requires NativeAOT support. I hope it doesn't run into the limitations of NativeAOT otherwise it's just Unity-only.
I have teams with 1-2 permanent members and 8 more that may or may not want to check like... maybe once a week at most. Seat limits really mess with the "compliance officer needs to do something every once in a while but do we really need to pay for a separate seat?" issue with per-seat pricing.
A heavy user and a one-time-monthly user are different costs to the product but charge me the same. ;_;
The fees are higher everywhere. Their pitch is "our fees are higher, but we have higher-end customers who spend more", which roughly tracks with reality. But a hot dog stand isn't gonna have whales but an upper-end store might, so it's not surprising to see less support it.
Which do you prefer most in an application: What the app currently does (or will do in three months)? What the future app might look like in five years? And/or: how it will get there?