What you receive, and where you keep it

What arrives at the end of a job is a folder. Inside it are the panoramas in optimised web format, the tiles the viewer loads as you look around, one entry HTML file, the JavaScript and styles that run the tour, and your own material — logos, fonts, icons, any floor plans it uses. You put that folder on a static web host and the tour is live. There is no account to keep, no licence key, nothing that expires, and nothing inside it that phones home to a service which could withdraw a file and break it.
What is actually in the folder
- The panoramas
- Every 360° photograph, in optimised web format and cut into the tiles the viewer pulls in as you turn your head. These are the tour. Everything else in the folder exists to show them.
- One entry file
- A single HTML page. That is what your web host serves and what a link points at. Open it and the tour starts.
- The code
- The JavaScript and styles that run the thing: the navigation arrows, the information popups, the menu, and the floor-plan position tracking if your tour has one.
- Your own material
- Logos, fonts, icons, any floor plans the tour uses, and the photographs and text that open inside the popups. It travels with the tour rather than being loaded from somewhere else.
- What is deliberately not in it
- No login. No seat. No licence key. No call out to a service that could stop answering. That is the whole reason we build them this way.
Where you can keep it
- On your own domain. Most clients put it on a subdomain of the site they already have.
- In a folder on the hosting you already pay for. It needs a static web host and nothing else — no PHP, no database, no build step, nothing to install on the server.
- On our subdomain. That is €5 per GB of storage a month, and the files are still yours either way.
- In your own archive, next to your other originals, whether or not it is published anywhere. A tour you have taken offline is still a tour you hold.
One honest limit on that list: a build that runs with no web server at all — a reception screen, a trade-stand laptop, a kiosk — is a separate build and we quote it separately, because the target hardware changes what the build has to be. It is on the pricing page under the things we quote rather than list. What you are handed as standard is a folder for a web host.
Why this is not the same as free hosting
This is not hypothetical in this category, and it has a date on it rather than a warning attached to it. What happens when a platform is sold sets out the case with its sources, and self-hosted, white-labelled, hosted-for-you untangles the three different things that get called the same word.
Three questions to ask before you sign anything
- Which files do I receive? Not “do I own it” — that gets a yes from everybody. Ask what lands on your machine, and whether it opens without their software running.
- What happens to the tour if I stop paying you? With a folder the answer is nothing. With an account the answer is worth hearing in full.
- What does a change cost later? New rooms, new popup text, a re-shoot after a refurbishment. Ours is priced from the same rate card, and the positions that have not changed are not re-charged.
That third one is where the honest caveat sits. The folder you hold runs anywhere, and it keeps running with nobody’s permission. Changing what is inside it — adding rooms, rewriting popups, re-shooting a room that has been refurbished — is work, and it is priced like work. Owning the files means you are never locked in. It does not mean edits are free, and any supplier who implies otherwise is selling you the wrong sentence.
Questions people ask
- Do I have to host it myself?
- No. If you would rather not run anything, we host it on our subdomain for €5 per GB of storage a month. The point is that you are handed the files as well, so hosting with us is a convenience you chose rather than a condition of the tour continuing to work.
- What happens if I stop working with Vronos?
- Nothing happens to the tour. You are holding the folder, it runs on any static web host, and there is no account, key or subscription of ours in the middle of it. Move it to your own server or to another agency whenever you like — no permission required and nothing to unlock.
- Does it need PHP, a database or anything installed on the server?
- No. It is static files: panoramas, an entry HTML page, JavaScript and styles, plus your own logos, fonts and any plans. Any host that can serve a folder of files can serve it. That is also why it is straightforward for your own web agency to take over.
- Can my web agency embed it in our website?
- Yes. It is a folder on a host with an entry page, so it can sit on a subdomain, in a subfolder of the main site, or inside a page on your site. Nothing about that arrangement depends on us being involved afterwards.