VPS for Lumion — from €5.49/mo

Visualise architecture in the cloud — a Lumion server on NVMe with RAM headroom, a 5-hour test period, so you risk nothing

Deploy a server for Lumion
A virtual server for Lumion

The main thing first: Lumion renders with the graphics card, so it does not run on a regular VPS without a GPU — for the rendering itself we build a separate configuration with a graphics card. Base plans from €5.49/mo take care of the rest: storing asset libraries and scenes on NVMe, preparing geometry, shared team access to projects over RDP and backups. You deploy the OS yourself and install your own Lumion licence; server access is full, with administrator rights. A 5-hour test period is available — verify your workflow before paying.

Plans

VPS for Lumion

The plans in this block — Standard 1 (4 vCPU, 4 GB) and Standard 2 (4 vCPU, 6 GB) — suit storing libraries and preparing geometry. Rendering in Lumion itself requires a graphics card — the GPU configuration is sized separately. A 5-hour test period before payment.

Compare all plans
5.49 mo

Standard 1

4 vCPU · AMD EPYC
4 GB RAM
50 GB NVMe
Unlimited traffic
IPv4 · KVM
24/7 support
6.99 mo

Standard 2

4 vCPU · AMD EPYC
6 GB RAM
60 GB NVMe
Unlimited traffic
IPv4 · KVM
24/7 support
1

Your own Lumion environment

Deploy the OS you need and install your own Lumion licence with asset libraries — the server is entirely yours.

2

Rendering — on a GPU configuration

Computing scenes and clips requires a graphics card: for that we size a separate GPU server, while the base plan remains the project store.

3

Scenes on NVMe

Fast drives and RAM headroom keep large scenes, textures and assets close at hand, speeding up work and rendering.

How to run Lumion on a VPS

1

Choose a plan and an image

Pick a plan — Standard 1 (4 vCPU, 4 GB) or Standard 2 (4 vCPU, 6 GB) — and select the OS image for installing Lumion and remote access.

2

Install the OS yourself

Through the panel you deploy the chosen OS on the KVM server yourself — the configuration stays fully under your control.

3

Install Lumion

Connect over remote access or the KVM console, install your own Lumion licence and upload the scenes.

A server for visualisation work

A server for visualisation work

We will suggest which plan fits your scene complexity and clip length: the RAM, vCPU count and NVMe space for assets. Lumion leans on graphics — the GPU configuration we size separately.

We will help set up remote access and a secure connection. Configurations with a graphics card are described on the GPU servers page; an overview of visualisation workloads — the 3D rendering VPS.

Help me size it

Frequently asked questions

Didn't find your answer?
Write to us via the contact page.

Yes. We provide a server with root access, and the Lumion licence you install is your own — the server is fully under your control.

Lumion is demanding on graphics. The base plans focus on vCPU, RAM and NVMe, and a configuration with a GPU we size separately.

Yes: libraries and scenes sit in a shared folder on the server, and members connect over RDP under their own accounts. Project versions stop drifting apart across personal computers.

Yes. The rendering runs on the server, and you connect from a laptop or a tablet from anywhere.

Lumion is built around a graphics card, so a regular configuration without a GPU will not do. We assemble a GPU server for the task — describe your projects and the render resolution you need.

Prepare geometry, store model and texture libraries, and keep shared access to projects. The rendering itself moves to a configuration with a graphics card.

Lumion libraries and scenes take hundreds of gigabytes: start from 400 GB NVMe (Max 1, €42.99/mo) and plan headroom for growth.

Connect through the KVM console: it works independently of the system and network state. From there you can repair the configuration or reinstall Windows from scratch.