The technology behind Lotuz 360 tours
This page is for the developer's technical team: what the tour is built with, how it runs, and which files are delivered. We state only technology we actually use.
- krpano platform, installed and run by us
- No overseas platform subscription
- A live tour embedded right in the page, ready to use
Built from a model, shot on site, or a mix of both
A 360 tour has two image sources, and most misunderstandings about cost and time start from mixing the two up.
Built from a 3D model. Each position is rendered from drawings and the model into a spherical image; the building does not need to exist. This is the only option while the project is still on paper, and it allows the time of day, materials and interior options to be chosen. In return, quality depends on the input model and rendering takes more work.
Shot on site. For finished buildings, we shoot with a camera and panoramic head. It is faster and cheaper, and viewers know this is the real condition. Anything not yet built cannot be shot.
Combining both methods in one tour. Common in phased projects: zones already handed over are shot, zones under construction are built from the model, and everything joins into one navigation system. We do both, so there is no need to split the tour in two or hire two suppliers.
Technical Specifications
| Tour-building platform | krpano. We install and run it ourselves on our own infrastructure, with no monthly subscription |
|---|---|
| Image format | Spherical panoramas cut into multiple resolution layers (tiled multires) so only the area being viewed loads |
| Loading | Loads progressively in layers: the tour opens with the overall image, and detail loads as the viewer zooms in. Works on weak connections |
| Viewer platform | WebGL in the browser; no app, extension or plug-in to install |
| Supported devices | Phones, tablets, computers, sales-counter touchscreens and consumer VR headsets |
| Navigation | Hotspots on the floor, a floor-plan minimap, an area list, and auto-rotate when idle |
| Info points | Attach to any position; opens text, images, downloadable documents or external links |
| Day and night mode | Two image sets for the same position; viewers toggle between them right in the tour |
| Deployment | Static files, hosted on our infrastructure or handed over for self-hosting; embed code for the website included |
| Offline version | Installed on a computer or touchscreen at the sales counter |
| Not included in the product | Measuring dimensions and scanning to build dollhouse-style models. We do not offer these two items and make no commitments about them |
Six consequences of this approach
Each technical choice brings a consequence for cost or control.
No monthly subscription fees
Many virtual tour platforms charge monthly per space, and when the fees stop, the tour stops. Our tours are static files with no expiry mechanism.
Tours the developer controls
We deliver all files so the developer can host them. Backing up means copying a folder; to change hosts, copy it over and the tour runs unchanged. No lock-in to a single provider.
Fast to open on weak connections
Images are sliced into layers, so the tour appears almost instantly and detail loads afterwards. Viewers do not wait for one heavy image.
Runs where there is no internet
Connections in sales galleries on construction sites are often unstable. The offline version solves that.
Interface matched to the project's identity
We run the platform ourselves, so the interface, buttons and layout can be adapted to each project's brand identity, without being locked into a template.
No dependence on third-party policies
A foreign platform can change prices, change terms, or stop serving a region. A static-file tour carries no such risk.
Six steps to build a tour
Two review points are marked so the developer knows when to arrange viewers and give feedback.
Finalize the list of stops
On the floor plan, we agree where the tour stops and how viewers move from one to the next. The number of stops affects cost the most, so it is best settled first to avoid extras.
Create spherical images for each point
Finished buildings are photographed on site with a camera and panoramic head; unbuilt ones are rendered from the 3D model. Each zone can use a different method.
Stitching and image correction
Frames are stitched into a seamless spherical image, with light and color balanced between points so transitions feel smooth, then cut into multiple resolution layers.
Build navigation and info points
We place hotspots, the floor plan and the area list, and attach info points that open text, images or documents. If the project has a day/night mode, the two image sets are joined in at this step.
Apply the project's brand identity to the interface
Colors, buttons, logo and layout follow the brand identity. That is why we run the platform ourselves rather than use a prebuilt template.
Handover and website embedding
We deliver all files plus the embed code so the tour runs in the project website. If needed, we also export an offline version for the computer at the counter.
Files in, files out
Developer sends
- Floor plans of each level or the masterplan, so we can settle the stops together
- 3D model and drawings, for the parts not yet built
- Site access schedule, if shooting on site
- Project logo, colors and fonts
- Content for info points: area names, floor areas, attached documents
- Domain or page that will embed the tour, if already available
Lotuz delivers
- The tour runs in the browser and opens on phones and computers
- All tour files for self-hosting, independent of our infrastructure
- Embed code to place the tour on your project website
- Offline version for a computer or touchscreen at the counter, on request
- Original full-resolution spherical images
- Short guide for replacing images and editing info-point content after handover
Three projects, three technical challenges
The four tours below open and can be viewed right away. What is covered here is the part that cannot be seen: the problems that had to be solved for the tour to run like that.

Casa Del Jardin
The tour with the most features: day/night mode, floor plan, info points leading from the exterior into each room. The hardest part is balancing light between the two image sets, so that flipping back and forth causes no color jump and no shift in viewing angle.
- Two image sets for the same position
- Floor plans linking exterior and interior
- It is the tour embedded on this page

Sunneva Island
This is a large-scale island urban area, so the challenge is wayfinding, not a single house: viewers must know where they are within the whole site and where to go next without reading a map. With so many stops, the volume of imagery and keeping lighting consistent across zones are the heaviest part of the work.
- Many stops spread across a large area
- Navigation must explain itself
- Keeping lighting consistent across zones

Paradise Island
A resort in Tanzania, done entirely remotely, with none of our people on site. With the time-zone gap and test builds reviewed over an international connection, the two review points above are what make the project workable.
- Working across borders and time zones
- Approvals done entirely via an online preview build
- A process that also works remotely
Four tours running on this platform
Open the browser's inspection tools on any tour to check against what this page describes.
FAQ
Is embedding the tour in our project website complicated?
Which VR headsets are supported?
Where is the tour hosted, and who holds the files?
After handover, how much can the developer edit themselves?
Can the tour measure room dimensions?
How many scenes does a typical tour have?
Technical discussion before you approve the proposal
Technical teams can contact us directly. The person who answers is the person who builds the tour, with no sales intermediary.
- Technical requirements to cross-check
- Planned hosting infrastructure for the tour
- Presentation device at the point of sale
- Systems to integrate with, if any



