What happens to your tour if we stop trading
If Vronos stopped tomorrow, the delivered tours would keep working — every one was handed over as a folder of files the client holds, and nothing inside a delivered tour calls back to us. That is the strong half of the answer, and it is strong because it is a property of the artefact rather than a promise from a supplier. The weak half is that we have no written continuity policy, no escrow arrangement and no named successor, and four of the nine questions below have no published answer. We would rather list them than let the strong half stand in for the whole.
Who you are actually buying from
Vronos is a Person Fizik — a sole proprietorship — registered in Albania under NIPT M02312003R. That is one person, and pretending otherwise on a page about supplier risk would defeat the purpose of writing it. A sole proprietorship cannot be restructured into continuity. It stops when the person stops. Every studio of this size has the same shape, whatever the plural pronoun on their About page implies, and the useful question is therefore not how big the supplier is but what they hand over.
Nine questions, and where we stand on each
| The question | Published? | Where we stand today |
|---|---|---|
| What do I physically hold when the job ends? | Yes | A self-contained folder: panoramas, tiles, any floor plan, icons, logos, fonts, an entry HTML file and the code. Stated on every project page. |
| Does anything switch off if I stop paying you? | Yes | No. There is no subscription, so there is nothing to stop paying. |
| Is what I was given licensed to me for a term? | Yes | No. Nothing is licensed for a period and there is no expiry on it. |
| If you host it, can I take it off your server? | Yes | Yes, at any time and without asking. Hosting with us is a convenience; the files are yours either way. |
| Who am I contracting with, legally? | Yes | Vronos, Person Fizik, NIPT M02312003R, registered in Albania. One person. |
| Is hosting on your subdomain time-limited? | No | We have never set an end date and we have never written down that there is not one. Unanswered. |
| Do I receive the file the tour can be edited from, or only the built output? | No | Not published. It decides whether owning it means you can host it or means you can change it. |
| Do you keep an archive copy, and can I ask for it again in five years? | No | Not published, and no retention period is set. Do not use us as your backup. |
| Is there escrow, or a named successor? | No | There is neither. If it matters to your organisation it belongs in a contract, not on a marketing page. |
Five answered, four not. The five are answerable because they are properties of the thing you receive. The four need a written policy, and there is not one yet.
Why the first five hold without any policy behind them
None of the five answered questions rests on us doing anything in the future. They are all statements about the object. A folder of static files on a host you chose keeps working for the same reason a printed floor plan keeps working: nobody has to maintain the relationship for the thing to continue existing. That is the whole design, and it is why we can answer those five in one line each while a platform cannot answer them at all.
What we would do, what we cannot commit to, and what we will not claim
- Would: if we ever wound down, publish notice and offer every client a fresh copy of their folder while we still had it to give. That is an intention. We are labelling it as one rather than dressing it up as a policy, because a policy has a retention period and an owner and this does not have either yet.
- Cannot yet commit to: how long we retain a copy of a delivered tour, whether hosting on our subdomain has an end date, whether the editable project file forms part of the handover, and any form of escrow. Four questions, no written answers, and no useful purpose served by improvising them here.
- Will not claim: that any of the four is settled. When they are settled they will be written on this page with the date they were settled on, and the change will be visible.
Run these nine at everyone, including us
This table is a better instrument than a reference call, because every question in it has a factual answer and none of them can be answered with an adjective. Send it to whoever you are considering. If a supplier’s answer to question one is a login, the other eight matter much less than you think — everything downstream of “what do I hold” is a variation on the same dependency.
Our own answers above are drawn from what we already publish on services, pricing and every one of the project pages, and the links are there so you can check that this page and those pages say the same thing. There is no external source in this post and no industry figure, because a supplier’s own continuity is not something a third party can vouch for. If you want the practical version of the strong half, what arrives on the last day lists what is in the folder, and owning against renting sets out what self-hosting costs you in return.
Questions people ask
- Should I worry about buying from a one-person studio?
- Worry about the right thing. The genuine risk with a small supplier is availability — not being able to reach us to change something, or to shoot the extension you built last year. The risk it is not is your tour going dark, because your tour does not depend on us being reachable. Judge a small supplier on what they hand over, not on how many faces are on the About page.
- Do you keep a copy of my tour?
- In practice yes, for as long as it is on our subdomain. We have not published a retention period, we do not offer it as a backup service, and you should not treat it as one. Keep your own copy in two places. That advice would be identical whoever built the tour.
- What if I lose my folder?
- Ask us and we will send it again if we still have it. That is what we would do, and it is not a commitment we have written down — which is precisely the gap this post exists to state rather than paper over.
- Does hosting with you create a dependency?
- It creates a convenience. The test for a dependency is whether the tour would still run without us, and it would, because you hold the same files we are serving. If you want to remove the convenience as well, copy the folder to your own host and change where your link points. Nothing has to be requested and nothing has to be unlocked.
- Is there anything inside the tour that contacts Vronos?
- No. The folder is static and self-contained, and nothing in it fetches from us when a visitor opens it. If you buy analytics, that reports to your own Google Analytics property rather than to ours, and you can remove it without touching anything else.
