Visual Composer and WPBakery are branches of the same product, and currently both are expected to work with Toolset.
If the branches diverge significantly it could force us to choose in the future, but at the moment they are both compatible.
The free version of VC should work, the premium features do not relate to Toolset integration specifically.
However, I just noticed that we have an issue arising from the Gutenberg integration. If you try to edit a Content Template with VC/WPBakery, the button to choose the page builder is missing, only a button for using Gutenberg is visible.
I'm just checking with my colleagues about what is expected here, and I'll get back to you when I hear from them.
Sorry for the delay getting back to you, we are waiting on a copy of the premium version of VC to test alongside the free version.
We rely on certain "fingerprints" in the VC code to detect it, and it seems that these were changed some time ago, but nobody reported that the integration was broken. It seems like we don't have any active users of VC (though I know we do have users of the WPBakery fork).
When we can confirm that the updated fingerprints we use for the free version work with the premium version we will be able to release a fix.
Just to update you that the developers have concluded that the forks of WPBakery and Visual Composer are sufficiently different that they must be considered separately.
The current position, therefore, is that we support WPBakery but we do not support Visual Composer.
A feature request has been added to add support for Visual Composer, although I cannot give any estimates as to when that might happen.
I also talked to the VC team they said they are working to get compatible with the toolset types.
i am hoping it will work out else my money will be wasted because i have VC now.
