There's a question few clients ask when they commission a virtual tour and that, once answered, usually changes the whole conversation: is the tour mine, or am I paying for it to exist? The distinction isn't semantic. It determines whether the virtual tour is a digital asset of the company — with value on the balance sheet, something that can be transferred, modified and maintained indefinitely — or a rented service that disappears when you stop paying the monthly subscription.
Most of the best-known virtual tour platforms on the market — Matterport, Kuula, Roundme and similar ones — operate under a SaaS model: Software as a Service. The client pays a monthly or annual fee for the platform to host and serve the tour. If payment stops, the tour is no longer available. The client doesn't have the files, doesn't have the code, and has no way to move the tour to another server. What they paid for was access, not ownership.
The SaaS model: what looks cheap can be the most expensive
SaaS virtual tour platforms have a legitimate value proposition: they make publishing a tour easy without technical knowledge, offer a manageable interface, and in some cases include advanced features like Matterport's dollhouse view or the built-in analytics of certain platforms. For a real estate photographer who delivers 30 tours a month to agents who only need the link, the SaaS model makes operational sense.
The problem appears when you calculate total cost over time. A standard Matterport plan for professional use runs between $35 and $65 USD a month for active tours, plus a variable cost per scanned space depending on the plan. For a real estate developer with 5 active properties on tour over 3 years, the subscription cost can easily exceed $2,000 USD — for the right to have the tour exist, not for the tour itself. If the developer decides to switch platforms, they can't take anything with them. The scans stay on Matterport, in proprietary formats with no way to export in a standard format.
is the point at which the accumulated cost of a SaaS virtual tour subscription typically exceeds the production cost of a self-hosted tour of equivalent quality. From the fourth year on, the SaaS client is paying for a tour they've already paid for, and the self-hosted client pays nothing extra.
Comparison based on current Matterport, Kuula and Roundme plans vs. self-hosted 3DVista production, 2024–2025.
The self-hosted model: real ownership of the digital asset
The self-hosted model works like this: the tour is produced with publishing software such as 3DVista Virtual Tour Pro, exported as a package of standard web files — HTML5, JavaScript, panoramic images and related assets — and that package is uploaded to the client's server or to hosting contracted for that purpose. The tour works like any other web page: as long as the hosting is active, the tour is active. There's no intermediary platform that can switch it off.
The client has full access to all the files, can make backups, can move the tour to another server, can modify specific elements with basic knowledge of HTML and JavaScript, can integrate it with any analytics or booking system they use, and can hand it to any other agency for future updates without depending on LUM360 or any other provider to maintain access. The relationship with the production provider ends when the work is delivered; the tour's lifespan depends only on the client.
A self-hosted tour isn't a service. It's a website. And like any website, it belongs to whoever commissioned it, not to whoever built it.
Side-by-side comparison: SaaS vs. self-hosted on the factors that matter
| Factor | Self-Hosted (3DVista) | SaaS (Matterport / Kuula) |
|---|---|---|
| Tour ownership | 100% the client's — files on their server | Hosted on the platform — no export possible |
| 1-year cost | One-time production + hosting (~$150–300 USD/year) | Production + monthly subscription ($420–780 USD/year) |
| 3-year cost | Cumulative hosting (~$450–900 USD total) | Cumulative subscription ($1,260–2,340 USD total) |
| What happens if you stop paying? | Nothing — the tour stays live on the server | The tour is deactivated or degraded depending on the plan |
| Brand customization | Complete — no platform logos | Limited — the platform's logo usually appears |
| GA4/GTM integration | Full — total control of tracking | Limited to the platform's own analytics |
| Hotspots and interactivity | Unlimited — video, audio, links, forms | Matterport features limited by plan; Kuula is basic |
| Portability | Total — can be moved to any server | None — proprietary format, no export |
| VR compatibility | Yes — standard WebVR files | Yes on Matterport — not on most smaller SaaS platforms |
| Vendor dependency | Only on hosting (a replaceable commodity) | High — if the platform shuts down, the tour disappears |
The risk nobody mentions: what happens if the platform shuts down or changes?
The SaaS industry has a history of abrupt plan changes, mergers and shutdowns that directly affect users. Matterport has changed its pricing structures multiple times, eliminating plans that had active users and forcing migrations. Smaller platforms have shut down with little or no notice, leaving clients without access to their tours and with no way to recover the files.
For a boutique hotel that has its tour integrated into its booking engine and its Google Business Profile listing, having the tour stop working overnight — because the platform changed its pricing or simply shut down — is no minor inconvenience. It's an interruption to an active conversion channel, with a replacement cost that includes new production plus the time until the new tour is indexed and working. That risk doesn't show up in the monthly subscription price, but it's real.
Self-hosting eliminates this risk entirely. If LUM360 as a company ceased to exist tomorrow, every tour we've produced would keep running on our clients' servers without any interruption, because the files are there and don't depend on any centralized system that we maintain.
When the SaaS model does make sense
Editorial honesty requires mentioning the cases where the SaaS model has real advantages. The clearest is Matterport for applications where the dollhouse view is essential and there's no equivalent of the same quality in the self-hosted market: architecture, construction, technical inspection and real estate asset management projects where 3D volumetric representation is part of the deliverable.
It also makes sense for real estate photography agencies that produce a high volume of tours with little need for customization: Matterport's integrated workflow, with camera, app and automatic publishing, has an operational efficiency with no equivalent in the self-hosted workflow. For someone who needs to publish 50 tours a month with a 24-hour turnaround, the technical friction of self-hosting may not be justified.
What changes is the conversation with the client. At LUM360 we believe the client should understand from the start what they're buying: whether they're paying for access to a service or building an asset. Both options are legitimate; what isn't acceptable is not knowing which of the two you're choosing.
What the client receives on every self-hosted project
Web files ready for any server
- Technical base
- A complete folder in HTML5, JavaScript and CSS, ready to upload to any compatible server.
- Panoramas
- Equirectangular images at production resolution, with an 8K minimum standard to preserve detail and perceived value.
Editable project and production assets
- Master file
- Editable 3DVista project for future updates, provided the client or their team holds their own license.
- Visual control
- Assets organized so the tour can be maintained, backed up or moved without depending on a closed platform.
Documentation, support and independence
- Documentation
- A server upload guide and a basic reference for updating hotspots or making minor adjustments.
- Support
- 30 days after delivery for adjustments and technical questions related to installing the tour.
- Dependency
- No operational dependency on LUM360: the tour works as a digital asset the client owns outright.
To understand the full infrastructure that makes it possible to host and serve a self-hosted tour — what hosting is, what a domain is, how they relate and what you need for your tour to run on your own server — the next blog article covers exactly that topic: Hosting and domains for virtual tours: the complete guide, no jargon. And if what you need is the comparative financial calculation between continuing to pay for a subscription platform and migrating to the self-hosted model, the Matterport vs. LUM360 5-year analysis runs that number with concrete real estate market scenarios.
Before you hire for a tour, ask whether the tour belongs to you.
At LUM360 we produce virtual tours with complete source code delivery. The tour we produce is yours — not a service we rent you month to month. If you're weighing your options, or you already have a tour on a SaaS platform and want to migrate it, let's talk.
