Engine-seconds, cloud credits, top-ups and what each plan includes.
Conversion time is the only metered resource. Everything that happens after a model is converted is unlimited on every plan:
This is deliberate. Metering views would mean the better your product page performs, the more you pay — which is a strange thing to charge for.
Conversion is measured in engine-seconds: the time a conversion engine actually spends on your file. It is the unit we are billed in, so it is the unit you are billed in — nothing is rounded up into a proprietary “credit” that hides the real cost.
The underlying rate, so you can check the arithmetic:
| 1 cloud credit | £3.00 |
|---|---|
| 1 cloud credit buys | 12 minutes of engine time |
| Therefore | £0.25 per engine-minute |
Your plan includes an allowance of engine time, shown as minutes in the header so you can see it without doing sums.
Allowances do not roll over. Each billing period starts fresh, and time you did not use is not carried forward. If your usage is lumpy — a big catalogue import one month and nothing the next — a top-up in the busy month usually works out better than a larger plan all year.
VUE checks your remaining allowance before starting a conversion, so running out means the upload is refused rather than a job dying halfway with your time spent. The message tells you how much the conversion needs and how much you have.
| Limit | What it means |
|---|---|
| Conversion time | Engine time per billing period. The one that is actually metered. |
| Models | How many models can exist in the organisation at once. |
| Types per model | The biggest family you can convert in one go. Checked before conversion starts, and the message names the real number. |
These are switched on or off per plan:
| Feature | What it gates |
|---|---|
| Augmented reality | The view in your space button on embeds. |
| FBX and OBJ import | Uploading mesh formats as well as Revit families. |
| Configurator | Defining and curating your own option controls. Derived controls from a Revit family work regardless. |
| Material library | The shared library, Revit library import, and procedural finishes. |
| API access | API keys and the Revit add-in. |
| Branding level | The most branding the plan allows — see branding. |
The current price list is on the pricing section of the home page, which is generated from the same plan definitions the app enforces — so it cannot drift from what you actually get.
The header shows minutes used against minutes available, and warns as you approach the limit. Settings breaks it down by model, so a month that ran hot is traceable to the conversion that did it — usually one large catalogue family.
If the numbers do not look right, raise a ticket. We can see the per-job engine time and will explain or correct it.