TECHNICAL PLATFORM

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
4 tours
Running live, opens on a phone
VND 0
Monthly subscription fee for a delivered tour
10 people
A direct team: the person who answers is the person who builds
10+ years
Visualization and architectural presentation
01

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.

02

A live tour embedded right here

This is the Casa Del Jardin tour, not a screen-recorded video. Drag to look around, click a point on the floor to move to another room, and flip the day/night mode to compare against the specification table below.

The tour is a static file hosted on our infrastructure, so it can be embedded. Project websites embed it exactly this way, with a few lines of code and nothing extra to install.

Open the tour in a new window →

03

Technical Specifications

Tour-building platformkrpano. We install and run it ourselves on our own infrastructure, with no monthly subscription
Image formatSpherical panoramas cut into multiple resolution layers (tiled multires) so only the area being viewed loads
LoadingLoads progressively in layers: the tour opens with the overall image, and detail loads as the viewer zooms in. Works on weak connections
Viewer platformWebGL in the browser; no app, extension or plug-in to install
Supported devicesPhones, tablets, computers, sales-counter touchscreens and consumer VR headsets
NavigationHotspots on the floor, a floor-plan minimap, an area list, and auto-rotate when idle
Info pointsAttach to any position; opens text, images, downloadable documents or external links
Day and night modeTwo image sets for the same position; viewers toggle between them right in the tour
DeploymentStatic files, hosted on our infrastructure or handed over for self-hosting; embed code for the website included
Offline versionInstalled on a computer or touchscreen at the sales counter
Not included in the productMeasuring dimensions and scanning to build dollhouse-style models. We do not offer these two items and make no commitments about them
04

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.

05

Six steps to build a tour

Two review points are marked so the developer knows when to arrange viewers and give feedback.

1

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.

2

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.

3

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.

4

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.

Review point 1: view the test build and give feedback
5

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.

Review 2: lock the interface before release
6

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.

06

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
07

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

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

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

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
09

FAQ

Is embedding the tour in our project website complicated?
No. We send an embed snippet, and the website administrator pastes it in the right place, like the Casa tour in the middle of this page.
Which VR headsets are supported?
Common headsets that take a phone work fine, because the tour runs in the phone's browser. We do not build a separate app for dedicated headsets and make no commitment about this type.
Where is the tour hosted, and who holds the files?
By default it is hosted on our infrastructure for immediate use. All files can be handed over, and many developers choose to self-host; copy it anywhere and the tour runs unchanged.
After handover, how much can the developer edit themselves?
The developer can swap the image of a stop and edit text in an info point, with a short guide supplied. Adding stops or changing the navigation system needs us, because more spherical images must be shot or rendered.
Can the tour measure room dimensions?
No. Measuring dimensions and building dollhouse models fall under dedicated scanning equipment and are not part of our products. If exact figures are needed, rely on the drawing set.
How many scenes does a typical tour have?
There is no standard figure; the list of stops decides. A sales gallery usually has few stops; an urban area can have many times more, so the first step is to settle this list on the floor plan.
10

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.

Include this information for the fastest reply:
  • Technical requirements to cross-check
  • Planned hosting infrastructure for the tour
  • Presentation device at the point of sale
  • Systems to integrate with, if any
Lotuz Architectural Design Consultancy Co., Ltd. · 268 30/4 Street, Hoa Cuong Nam, Hai Chau, Da Nang