API and performance questions.

There's no public API yet around the software; definitely something we hope to get during this early access. Regarding performance, I think the best answer here would be to analyze this simple graph. The nodes Instance on Points, Points Scatter and Points Near Meshes are all custom built C++ libraries that match or outmatch Bifrost's equivalents in terms of performance, and the other nodes Selection from Names leverage OpenMaya to give you an interface to the content of your Maya viewport. We have this balance everywhere, including in UE5, where we first use the existing API, then slowly replace anything that we deem necessary to replace. For world building, almost all the nodes we provide are custom built. For modeling, there's a mix of custom + OpenMaya tools. This gives us an edge over Bifrost when it comes to making it actually usable by artists, as we can give them the commands they usually work with as nodes, and since they're already used to them, the learning curve becomes marginal. For instance, we can make a tool that queries the mouse position, and allows you to run some operation that a material picker or an object placer that relies on that data. Such tools are impossible to do with Bifrost, because their focus is clearly not (yet?) on ease of use for artists or smart integration within Maya/Max in a way that you can really leverage the features of those softwares. I like to think of GraphN as a new take on hotkeys or macros (really amazing concept in Modo) more so than a competitor to Houdini or Bifrost, because the userbase of those tools really isn't your average environment, props or character artist, and those are the people we're primarily targeting.