3D Rendering Server Rental — from €5.49/mo
Order a render node and compute scenes in the background — a 5-hour test period before payment, so you risk nothing
Order a render node
A 3D rendering server starts at €5.49/mo, and for production work most people pick plans with 16–40 vCPU. When ordering you choose a Linux or Windows image, install the system yourself through the panel and the KVM console, and deploy Blender, 3ds Max or any other package with your own licence. The computation runs on the server around the clock while your workstation stays free. The server is issued in a 5-hour test mode — render a control frame before you pay. Not sure how many cores you need? See the breakdown of which server 3D and rendering work requires.
Plans
VPS for rendering
For single scenes and learning, Standard 1 (4 vCPU · 4 GB, €5.49/mo) is enough; for production and render nodes people take the higher plans with 16–40 vCPU. Pay monthly, per half-year (−10%) or per year (−18%), with a 5-hour test period before payment.
Compare all plansStandard 1
| 4 vCPU · AMD EPYC |
| 4 GB RAM |
| 50 GB NVMe |
| Unlimited traffic |
| 1× IPv4 · KVM |
| 24/7 support |
Standard 2
| 4 vCPU · AMD EPYC |
| 6 GB RAM |
| 60 GB NVMe |
| Unlimited traffic |
| 1× IPv4 · KVM |
| 24/7 support |
What the plan includes
Dedicated vCPU on AMD EPYC, RAM, an NVMe drive, unmetered traffic, one IPv4 address, a KVM console and 24/7 support.
Rendering runs around the clock
The server never switches off: launch long computations overnight while your own computer stays free for work.
Your software and licences
Install Blender, add-ons and any render engine with your own licence — root access and your choice of OS make it possible.
How to order and start rendering
Three steps — from placing the order to the first frame.
Place the order
Pick a plan with the core count you need, choose the billing period and an OS image — Linux or Windows to suit your package.
Install the OS yourself
Through the panel and the KVM console you deploy the system yourself and get hardware-level access to the server.
Install the package and upload the scene
Over SSH or RDP, install Blender or another render engine, upload the scene and textures, and start the computation.
Not sure how many cores to take
The rule of thumb is simple: twice as many vCPU means roughly half the time per frame. A table of configurations for study scenes, archviz and animation is on the page about which server 3D and rendering work requires.
Need it even faster — connect several VPS as farm nodes and split the frames between them. For GPU engines and an interactive viewport, see servers with a graphics card: the configuration is built to the task.
How to size the configurationFrequently asked questions
Didn't find your answer?
Write to us via the contact page.
Choose a plan, set the billing period and OS image, and register — the server is created automatically. Payment is made after the test, not before the order.
5 hours. That is enough to install the OS, set up Blender, upload a scene and render a control frame on the production configuration.
vCPU on AMD EPYC, RAM, an NVMe drive, unmetered traffic, one IPv4 address, a KVM console and 24/7 support. Exact amounts are in the plan table above.
You do: pick the image when ordering, deploy the system through the panel and the KVM console, then install Blender and add-ons over SSH or RDP with your own licence.
Over SSH, SFTP or RDP — the same as on a regular machine. Finished frames are convenient to download the same way or serve straight from the server.
Yes, the plan moves up to a higher one with a short restart: more vCPU, RAM and disk are added. No need to reinstall the package or re-upload scenes.
You do, in the control panel in a couple of clicks — automatic copies are not part of the plan. Keep project sources on your own storage as well.
It depends on the scene and the deadline: reference points for cores, memory and disk are collected on the page about which server 3D and rendering work requires.