New Renderfarm: BlenderRenders.com

Aaron writes:

We’ve tested our service up through 400 rendering cores, and we have the option to expand, though initially this has not presented a problem.

Our model is fairly simple in that we allow our nodes to see your entire upload directory, so assuming you have the appropriate file structure along with relative linking in place, you should be in good shape. However there are two things that do stand out. Fluids are tricky in that they require a directory structure to be more fixed, and python scripting using the -P flag from the command line is currently not an option.

We do have an initial 50 minute per frame rule on our renders which can be waived with an email request to us. Primarily the limit is in place because our current policy is to charge for resources used, and we dont want to put our customers in a position where, for instance, someone forgot to uncheck motion blur, and then a simple 100 frame job eats up their entire budget.

Our billing model utilizes Amazon payments which also helps protect our customers by ensuring two things: 1. Customers define a maximum authorization dollar amount that cannot be exceeded. In order to render more than the current authorization balance, a customer needs to re-authorize a new amount. This ensures that they never exceed their budget, even when they need to go to bed while renders continue overnight! and 2. Amazon has all the payment info and BlenderRenders never stores credit card, or even address information. That protects our clients’ privacy.

If you register with the system, you can see our FAQ, which should also help clarify how some of this works. Registering doesn’t require any billing info.

Aaron has offered to help us write a review by setting up a free test account. If there’s anyone up for the job (which means you need a serious scene to render and you’ll need to write a proper report about the service), please get in touch with me.

Advertisement