We would all love to see that.
Making that happen is non-trivial. As most of those tools run in the Cloud and require paid services, any such portal would have to use an API, for which there is no industry standard, so each would have to be custom integrated. You would have to sign up for API tokens with the service, add your API key, so that request can be properly accounted for. And that’s just one of the problems to solve.
It’s a fast moving space. If ADSK would integrate with Weavy today, by the time this comes out as a release Weavy is likely old history (already is as it was acquired by Canva). To integrate it the reverse way (Weavy integrating with Flame) is less likely than Resolve or any other more popular tool, and even then this isn’t the most important thing for them.
All AI tools are in a race against time. They don’t have time to worry about our needs. And us keeping up with their pace requires a bit of an agility that release cycles don’t afford.
It does bring me back to the fact, that having some sort of batch node that could execute python code and pass image streams back and forth, would make it a lot easier for the community to build the glue code, which we are capable and willing off.
One possible avenue for that is the existing PyBox node, which warrants further experimentation.
There’s a long thread here that examines some of this.