What Server Do You Need for 3D Modelling and Rendering
Count the cores and the memory your scenes need — then measure the actual render speed during the 5-hour test period, before you pay
Match a configuration
A server for 3D and rendering is chosen by three numbers: the core count (CPU render time falls almost linearly — 16 vCPU finish a frame roughly twice as fast as 8), the amount of RAM that holds the geometry and textures of your scene, and the NVMe space for asset libraries and finished frames. A graphics card is mandatory only for GPU engines and an interactive viewport: Blender Cycles, V-Ray and Corona all render on the processor. Below are builds for typical workloads; once you have chosen, order a VPS for rendering.
What such a server costs
Standard, Power and Max — monthly or yearly at a discount. Test period of 5 hours before payment.
Standard 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 |
Standard 3
| 6 vCPU · AMD EPYC |
| 8 GB RAM |
| 80 GB NVMe |
| Unlimited traffic |
| 1× IPv4 · KVM |
| 24/7 support |
A build for a typical workload
Benchmarks for cores and memory, and the plans from our price list that match them.
| Workload | Configuration | Plan | Price, €/mo | |
|---|---|---|---|---|
| Study scenes, simple visualisation | 6 vCPU · 8 GB · 80 GB | Standard 3 | €8.99 | Order now |
| AutoCAD or SketchUp over RDP | 8 vCPU · 8 GB · 100 GB | Standard 4 | €10.99 | Order now |
| CPU archviz render in Blender or Corona | 16 vCPU · 24 GB · 240 GB | Power 3 | €27.99 | Order now |
| Regular rendering of heavy scenes | 24 vCPU · 32 GB · 400 GB | Max 1 | €42.99 | Order now |
| Animation, a separate render farm node | 40 vCPU · 64 GB · 700 GB | Max 3 | €84.99 | Order now |
Benchmarks for CPU rendering; actual render time depends on the scene, the engine and the sampling settings. A build with a graphics card is not part of these plans and is quoted individually. Prices are for monthly billing from our price list — 10 % lower for six months, 18 % lower for a year.
Cores cut render time
CPU rendering scales almost linearly: doubling the vCPU count roughly halves the time to compute a frame.
Memory holds the scene
Geometry and textures load into RAM in full: heavy archviz needs 24–32 GB, while study scenes fit into 8 GB.
A GPU is not always needed
Cycles, V-Ray and Corona render on the processor. A GPU is for the interactive viewport and GPU engines — that build is matched separately.
How to match a server to your scenes
Three steps — from the scene requirements to a measurement on a real render.
Measure the scene
Check how much memory the project takes on your workstation and add headroom for the system and the textures.
Pick the core count for your deadline
Decide how fast a frame or an animation has to be computed: twice the vCPU means roughly half the time.
Benchmark it on your own scene
The VPS is provisioned in test mode for 5 hours: run a reference frame and compare it with your own machine before you pay.
The build is chosen — time to order
Plans and the ordering procedure are on the VPS for 3D rendering page. If you need an interactive viewport or a GPU engine, look at servers with a graphics card: that configuration is assembled for the task.
If you already know the software, start from its own page: Blender, 3ds Max, AutoCAD, Revit or SolidWorks.
Go to the VPS order pageFrequently asked questions
Didn't find your answer?
Write to us via the contact page form.
CPU render time falls almost linearly with core count: 16 vCPU (Power 3, €27.99/mo) compute roughly twice as fast as 8, and the 40 vCPU of Max 3 (€84.99) another 2.5 times faster.
Not for CPU engines: Cycles, V-Ray and Corona render on the processor. A GPU is needed for the interactive viewport and GPU rendering — that build is not part of the plans and is quoted individually.
Use the project size in your workstation's memory as the benchmark: study scenes fit into 8 GB, heavy archviz with 4K textures needs 24–32 GB.
Keeping the texture library and finished frames on the server is convenient: 240 GB NVMe in Power 3, 400 GB in Max 1, 700 GB in Max 3. The disk grows when you move to a higher plan.
3ds Max, AutoCAD and Revit run on Windows only — you connect over RDP. Blender and most render engines also run on Linux, where the overhead is lower.
Yes, several VPS work as separate nodes: a farm manager distributes animation frames between them. The servers can be joined into a private network on request.
You bring your own licences for the 3D software — we provide the server, not the programs. You install everything yourself with root access or over RDP.
On the VPS for 3D rendering page: plans, OS images and checkout. The server is provisioned in test mode for 5 hours — you pay after checking it.