Step 04 · Deploy Anywhere | NovaVR
N0va {{ brand }}VR ← Back to process
04 Step 04 · Delivery

Deploy anywhere — headset, desktop, or browser tab.

One build, packaged for however your team will actually use it — a trade-show headset, a sales laptop, or a link a client opens on their phone. No separate rebuild per platform.

VR headset

Quest, Pico or PC VR — for trade-show booths, showrooms and hands-on training floors.

Desktop & tablet

Mouse/touch-driven version of the same build, for sales laptops and kiosk screens.

Browser link

Send a client a URL — no app install, runs on whatever device they open it on.

What you get on launch day
✓
Packaged builds for every target platform

Headset app, desktop executable, and a hosted browser link — all from the same source build.

✓
A short run-of-show

One page covering setup, controls and troubleshooting — so your team can run it on the show floor without us in the room.

✓
A support window

Fixes and small tweaks covered for a defined period after delivery — new machines or features are scoped separately.

What deployment actually means

One build, four places it runs

A headset for full 1:1 scale at a show, a laptop for a sales call, a touchscreen on your stand, and a tablet handed across a desk. The same project serves all four; level-of-detail versions handle the difference in what each can render.

No installation for your customer

Browser builds open from a link with nothing to download. This matters more than it sounds: an app your customer has to install is an app most of them will not install, and a demo that needs IT approval is a demo that happens next quarter.

Hosted by you or by us

We can host it, or hand you the files to put on your own infrastructure. Manufacturers with their own IT policy usually prefer the second, and everything is delivered so that is possible.

Yours at handover

The optimised models and the built experience are delivered to you with no ongoing licence and no dependency on us. You can extend it, hand it to a dealer network, or take it to a different studio in three years.

Common questions

Does our customer need to install anything?

No. Browser builds open from a link. A headset build is installed once on your own devices, but nothing is required of the customer.

Can we host it ourselves?

Yes. Everything is delivered as files you can put on your own infrastructure, which is what most manufacturers with an IT policy prefer.

What hardware do we need for a trade fair?

A standalone headset such as a Quest 3 and a large touchscreen covers most stands. Neither needs a host computer, and both travel in a case rather than on a lorry.

Do we own it afterwards?

Yes, with no ongoing licence. The models and the built experience are yours, and you are not dependent on us to keep using them.

What if we want changes in two years?

Come back to us, or take the files to anyone else. The delivery is deliberately not a lock-in — the assets are in standard formats.

Adding machines later?

The pipeline stays open — send us the next machine and it goes straight back to step 01, joining the same deployed build rather than starting a new project from scratch.

Start your spec → Back to process overview →