the license for the generated code is not too bad… but a bit vague… (it was updated recently)
so basically, currently, worst case is having to ‘register’ your use… but no fees for VERSION 1.X
its that last bit… if it was a bigger project, you might get stuck on version 1.x, as they might introduce fees for 2.x!
in fairness though, I think C74 are, as this times, just keep options open.
and Im not sure the type of commercial projects thats use RNBO, will really need to upgrade RNBO at a later date… but yeah, you’d have to go in with your eyes open.
(but hey… I doubt few pro developers are considering RNBO for any serious projects)
as for JUCE… yeah, theres very little UI possibilities in RNBO, for any target …
but frankly, thats ok, imho… once you go beyond some pretty basic UIs , your going to want the abilities to write full custom UI, and doing this with C++/Juce is a pretty reasonable route.
and yes, everything can be compiled locally - thats a non-issue.
so yeah, beyond prototyping, things get a little more complicated, but the basic approach is still good.
anyway, Ive been having fun with RNBO, diving a bit deeper…
there are a few limitations currently, Id really like some more meta data available in the generated code, this is proving a bit limited at the moment.
I can get around this by parsing some of the json thats generated alongside the C++ code, but thats a bit of a faff…
running on a rPI w/ PiSound is a nice experience…
Ive got a few PiSounds knocking around, so Im going to code a few instruments for those 
also been looking at the Rnbo Runner which is quite interesting…
(this is whats being used to implement the rPI ‘implementation’)
Ive got some other ideas for other platforms to use RNBO… though, I’ll probably dig into those only once Ive got a better feeling of how useful I find RNBO.
the SSP RNBO template is working nicely so far, but I need to figure out how to provide a build environment to end-users that won’t require dev experience… theres a few possibilities here.
including potentially just building the on the SSP itself.
(I use a cross compile environment, which Ive documented, but I fear its just going to be too intimidating)