No. SquidNet 2.x licenses will no longer be valid with the new 3.x release. If you upgrade your version to 3.x, you’ll be provided with a new LOCAL RENDER FARM license.
SquidNet’s licensing models are as follows:
Reseller agreements can be arranged. Please send us an email for additional information.
Yes. A 20% license discount is provided for educational institutions.
The cloud interface provides the following types of reports:
You may have an unlimited number of studio accounts and users with the cloud interface. Each studio account provides an interface for admins to create an unlimited number of render accounts.
SquidNet uses render credits to determine the amount of rendering resources used by a specific job. Render credit consumption is base on the the PPI (Processor Performance Index) of the rendering node. Higher performing render nodes consume render credits at a higher rate than lower performing render nodes. However, in the end, the overall cost of rendering each frame is the same.
Job profiles are created from application templates and contain the rendering instructions and parameters for a render job. Both the local and cloud interfaces allow job profiles to be created, edited, submitted and saved. Each profile can be re-opened, edited and resubmitted to the render farm.
Technical support is provided by email, phone, Skype and remote desktop connections (AnyDesk, RDP, Teamviewer, etc…).
Free online training is provided upon license purchase. Typical training sessions are as follows:
For feature requests and recommendations, please send us an email.
SquidNet supports the following rendering applications:
Render farms require centralized storage of render content. Farm render nodes access (render) the project content stored on the storage device. Upon render completion, the images are typically written to the same storage device.
Any network accessible storage (NAS) device will suffice. However, use of Windows (non-server) mapped drives are not recommended because Microsoft limits the number of concurrent network connections.
SquidNet runs as a background service (daemon on Linux and Mac OS). This service runs at all times and is persistent between host restarts. The main SquidNet GUI connects to the service via direct inter-process communications (IPC – TCP/IP). Service prerequisites are as follows: