Unlimited Computational Resources
TechNest, p.zza Vermicelli
87036 - Rende (CS)
The current supported Blender version is 2.80. Version 2.79b is still supported, while we will soon release the version for 2.83. Generally all future Blender LTS versions will be supported. In addition we can provide support for some minor release.
Yes, you cannot use Python scripts for security problems and you cannot use post processing mechanisms on the rendered frame like "compositing". These filters must be applied after the Coremuniti rendering phase. In addition, the maximum weight limit for each project is 500 Mb. You can find the complete list of restrictions at this link.
The ownership of the rendered file as well as the ownership of the file containing the scene
to render are ALWAYS of the user who sends the project over the network as specified in the
Terms and Conditions.
However, both the scenes and the results of the rendering, in the Testnet network,
are sent in the clear.
Coremuniti is not responsible for any leaking of the scenes or render results due to improper
use of the system.
It is understood that the leaking or hacking of other users' scenes or even the modification of the core software for viewing the scenes of others remains an offense punishable by law. Furthermore, it is the responsibility of the user who creates a new project to NOT send copyrighted material or that cannot be freely rendered on such a platform. For more information you can contact firstname.lastname@example.org
In order to send a Blender project to the Coremuniti network it is necessary to insert all the project files (such as textures or external blender files) in a single large .blend file. You can find a guide to preparing the Blender file at this link.
The scenes sent in the Coremuniti TESTNET network, even if it is sent in clear,
are not directly visible to other users of the network.
Viewing the scenes requires a system hack that is expressly prohibited
in the Terms and Conditions .
Using scenes from other users is an abuse and is punishable by law.
Furthermore, the the scenes assignment to the executing users is tracked. Coremuniti is in no case responsible for abuses perpetrated on the network.
Of course, you can try to render the .blend file with the version closest to the one used.
However, we recommend:
(1) First open the file with the version supported by Coremuniti to evaluate the results of the rendering.
(2) Save the file with the version supported by Coremuniti to avoid problems in starting up the project.
Coremuniti Device Identifier or CDI is a unique identifier for a single device. For each device, a new CDI must be generated. Multiple devices with the same CDI will be banned from the system. A guide to using CDI is available at this link .
Of course, it is possible to run Coremuniti Server from the command line using the package
To run this application you must have installed a Java Runtime Edition version 8 or later (version 11 is recommended).
At this link a guide to the application.
Running Coremuniti Server is already secure in itself. The executables that are sent over the network
(like the different versions of Blender) are carefully evaluated by the Coremuniti team and are
In addition, all precautions are taken to prevent malicious code from being executed on the PCs of users who perform the work of others.
However, you can increase security by using virtualization. A virtualization system such as Virtualbox can be used with a linux distribution (e.g. Ubuntu). The Coremuniti Server application can then be installed on this system.
This solution allows CPU sharing with similar performances with respect to the execution without virtualization, while currently it does not allow GPU sharing.
We will release soon an operating system image ready to use for execute on virtual machines or public cloud.