Of course it has some small inconvenients, but not bif deal. for example:

-Just one file, NOT linked files are allowed, wich its very limit for your pipeline workflow, but you can, still make link libraries and then make a final file where you APPEND libs instead of linking. Just a "quick" solution for this inconvenient. but hopes it will be fixed on the future.

-No BAKE functions, I mean nothing that needs to be cached on disk, for example:
-Particle Systems
-Fluid Simulation

-Just Blender internal Render Engine, but plans to add Yafray and maybe Indigo if its very requested.

In the cost theme, Im a litle confused about it, cause with a 3 test i did of course with diferent files and number of frames, it was very CHEAP for example to a file with 640×480 with 1150 frames with no OSA and no RAY activated but with a medium complex scene.

It took 3 minutes on render time, and cost $2.01, WOW, and the final file its 89.3 MB with the 1150 frames in jpg.

This same file on my PC render in a little more 1hour.

I think this its a great service wich comes in handy for a profesional jobs but even artist can benefit with it.

I want to write here my experience here after test the service. I hope it will be improved at least for particles systems render, cause its one of its great features in blender, of course therea are so many more but at least with particles admited could do great FX jobs.

Because I have a project with baked fluid files over 1 GB, and I was wondering how it would handle this, given that it is baked to my local machine.

If it is, I am definitely joining ;)

this is a very good news.
But in this version (beta) when i was maked test with particle systeme, i had a very good render without particle.
Perhaps in the next version.

Good work

Couple of things, though…

An "Exit" or "Logout" button would be nice. After launching the script there's no graceful way to exit, and thus no way to know if you've successfully logged out of the Green Button connection or not.

Also, while trying to exit the script I accidentally hit the "Submit Render" button. The scene I was in had nothing in it, but the job submitted anyway, which wasn't surprising. What *was* surprising was that even though I cancelled the job within about three seconds, I was charged $USD 0.01 of my free $10 trial for my misguided click. Sure, it was only a penny… but it made me think about where I'd be financially if *every* mis-click I've ever made cost that much. :-)

I can't wait to try out the service in earnest once I have a big enough render job.

Thanks for all you've done to bring this to the Blender community!

How is queing and priority handled? Can we specify we want our submission to use x processors or such?

I am thinking for instance if I submit a large Indigo render (in the future…) as a commercial job and want it back say in an hour for a deadline can you achieve that?

The 1c/minute charge rate was in place before we added Blender support, and I haven't come up with a better metric – kind of had my hands full just getting this far, but we're open to ideas on how best to meter CPU activity on a cluster.

We're also interested in supporting the community, so if you have work that will contribute back to the community (e.g. educational content, open projects, or things that really push the envelope of what is possible with Blender), please get in touch and discuss possible discounts or waiving of costs.

We're also looking to run some competitions in the near future – there will even be cool prizes, so watch this space!

Time to add Indigo and/or LuxRender :)