Capture01
The rig
Our own camera rigs and a shooting standard every operator follows — so a property with forty rooms reads as one tour, not forty different ones.
Aldea Labs / RealviewPlatform / 01
Built in-houseWe don’t licence
We don’t licence
tour software.
We built it.
Realview is our own 360° platform — the capture rig, the macOS editor, the hosting, and the viewer your guests actually touch. Underneath it runs Meridian, the rendering engine we built to get a space sharp on screen before anyone decides to leave.
Capture / Studio / Cloud / Viewer
Live sceneRendering / Meridian
Rock Bar / Oblu Sangeli, MaldivesDrag to look
The system / end to endPipeline / 02
Four links, all oursFrom the camera to the
From the camera to the
pixel on screen.
Most tour providers own one link in the chain and stitch the rest together from other people’s software. We own all four — which is why a fix here takes an afternoon instead of a week-long support ticket.
Studio02
The editor
An authoring tool we developed: retouching, colour, alignment, hotspot authoring, and the tile export that feeds the viewer.
Cloud03
The publisher
Versioned publishing, client review threads, and analytics. A space changes - the new version is live the same day.
Viewer04
The experience
What your guests actually touch, running on Realview. No watermark, no third-party template, no vendor badge in the corner.
What you get / brand-ownedDelivery / 03
The client sideBuilt around your brand,
Built around your brand,
not around our licensing.
These are the things clients ask for once a tour is live — a rebrand, one scene locked for a campaign, an offline copy for a trade show. Owning the whole stack means the answer is a date, not a feature request.
Identity01
Ours, but yours
Your logo, your type, your colours, your domain. Nothing in the frame advertises a software vendor, including us.
Integration02
Embeds that behave
Drop in a full tour or a single locked scene. It will not hijack scroll, break your layout, or argue with your CMS.
Narrative03
Guided, not aimless
Hotspots, floor plans, and authored paths point people at the suite, the view, the ballroom — whatever closes the booking.
Resilience04
Works on venue Wi-Fi
Tours can be pinned for offline playback, so a pitch on hotel internet or a trade-show floor never depends on the network.
Release05
Publish without fear
Every publish is versioned. Changes ship fast, and a bad one can be rolled back without taking the live tour down.
Ownership06
You keep the keys
No per-seat licences, no feature paywalls, no waiting on someone else's roadmap for the thing you need next quarter.
Rendering engine / in-houseMeridian / 04
The engine that makes
the magic happen.
Meridian is the part of Realview that turns a 360° space into pixels in a browser. It owns the whole path from file to frame — what gets requested, in what order, at what quality, and when it is allowed to touch the graphics card.
That sounds like plumbing. It is the entire difference between a tour that feels instant and one that makes a guest wait on a loading spinner.
Readiness01
It loads what you are looking at
Most viewers count tiles. Meridian measures screen area — it projects every tile into your viewport and only reveals sharp detail once the pixels you can genuinely see are covered. Blocking requests go to the middle of the frame, never to a sliver at the edge.
Prediction02
It knows where you will look next
Meridian tracks the camera's velocity and projects it forward about a tenth of a second, then ranks every tile by how close it sits to where you are heading. Detail is already on the GPU when you arrive, so a fast pan stays sharp instead of catching up after you stop.
Profiling03
It sizes itself to the device
A phone on hotel Wi-Fi and an M-series desktop are not the same machine, so they do not get the same settings. Meridian profiles the hardware on arrival and picks its memory, bandwidth, and decode budgets to match.
Restraint04
It stops when you stop
A still panorama does no work at all. The frame loop shuts itself off when nothing is moving and restarts on the next input, and texture uploads are metered against the frame budget so loading never costs you a dropped frame.
Controlled runtime study / 28.07.26Evidence / 05
Cold start / controlled 4G58.9%
lower time to usable detail
Meridian2.598 s
Incumbent6.326 s
Median time to stable, meaningful panorama detail. Both runtimes were served byte-for-byte identical imagery from one origin, on one machine, alternating which went first.
55.7%Faster room to roomMoving between scenes once a tour is already open, on the same connection.
66.1%Less data pulledPanorama bytes fetched before the view is worth looking at.
90Paired runs, zero excludedThirty alternating pairs across each of three protocols. Every run counted.
Testing
caveats
caveats
On a fast desktop connection the gap narrows to about 20%. Once a tour is fully loaded, both engines saturate 120hz refresh rate — Meridian’s advantage is in getting there, not just drawing at 120fps. The full method, the confidence intervals, and the limits of what the test proves are available on request.
30 alternating pairs per protocol / zero excluded / 1440 × 900 DPR 1 / shared 213,985,421-byte panorama tree
Realview / Aldea LabsImage / motion / space
Built, not licensed.
The people who wrote the renderer are the people shooting your property. “Can it do this?” is a scheduling question here, not a licensing one.
Back to Tools & TechWant to see it on
Want to see it on
your own space?
Tell us about the property — we’ll come back within 24 hours with an approach, a timeline, and a price.