I am Early Ehlinger, President of ResPower, Inc. I am considering adding Indigo rendering to our commercial render farm (see link in my signature), and would like some feedback from anybody that has a moment to reply.
We provide two billing models : metered rendering and unlimited rendering. Under metered, we keep track of the render time and charge accordingly. Under unlimited, you pay a flat fee and can submit as many frames as you like during the life of your subscription. However, frames have a completion timeout to prevent abuse and allow us to load balance between multiple customers. The timeout depends upon the subscription level. For Blender, it ranges from 15 minutes to 2 hours. For all other render engines, it is set at 2 hours.
With respect to Indigo, here are my concerns/questions:
1) It looks like the default for Indigo renders is to continue indefinitely. This obviously doesn't fit in with our existing model very well. Would having the render halt when the samples per pixel reaches some (user-defined) threshold or when a certain amount of time has elapsed be acceptable? These are the -haltspp and -halt command line options.
2) You have more experience than I do with Indigo [ obviously

3) Our farm is heterogeneous in nature, as we have been "growing" it organically for almost 8 years. Obviously this could lead to noise flickering from frame to frame if an older node renders some frames. To make sure that all frames reach the predetermined SPP level, I'm trying to figure out if using the -r igi_path option will be viable. Does anybody here have experience with that option, as far as how well it works, stability issues and the like?
4) I'm considering pricing this so that it fits in with our existing Blender pricing, which starts at $20 for 15 minutes/frame, unlimited frames, for 30 days. Does this pricing sound reasonable?