I have to say, though - I really couldn't see myself using a closed-source framework for any web application, especially one which is quite new. The potential for running into bugs which it's impossible for me to fix is too great, and I can't afford the time and tension involved in waiting for a vendor to offer an update.
As the founder (and at present, sole developer) of a small ISV, it can be difficult balancing requests from customers, the vision of the company, and maintaining existing code alone. This problem would be far more pronounced for someone attempting to build out, maintain, and develop a community around an entire framework. Aside from perhaps Werkzeug (especially when it was first released), I can't think of a web framework that would have been able to thrive without either a growing community of developers and maintainers contributing, or heavy corporate sponsorship.
I know I'm just some guy on the web tapping out a comment, but I think you'd save quite a bit of sanity and find much better adoption by opening up the source, encouraging others to contribute, and empowering more developers to build applications rather than finding themselves frustrated by a bug in a closed framework which they cannot fix. If revenue is a concern for you, perhaps it's worth considering that things tend to work out well for those who succeed in defining new ways of building and deploying web applications (cf. 37Signals, the Django team, JRuby's core team, etc). You might be surprised.
Thanks for sharing the screencasts - good luck!
Scott