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.
Realview is our own 360° platform — the capture rig, the authoring suite, the hosting and CDN, and the viewer your guests actually touch. Underneath it runs Meridian Engine, the rendering engine we built to get a space sharp on screen before anyone decides to leave.
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.
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.
A state-of-the-art authoring tool we developed: retouching, color, alignment, hotspot authoring, video and color grading, floor plan assembly, everything that ends up in the viewer.
Versioned publishing, in-viewer client review threads, and built-in analytics. When a change is made, the new version goes live in a few minutes.
What your guests actually touch, running on Realview — including true display HDR on compatible screens. No watermark, no third-party template, no vendor badge in the corner.
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 lets us built features your business needs, quickly.
Your logo, your type, your colors, your domain. Nothing in the frame advertises a software vendor, including us.
Drop in a full tour or a single locked scene. It will feel like a part of your identity, won't break your layout or argue with your CMS.
Hotspots, floor plans, and authored paths point people at the suite, the view, the ballroom — whatever closes the booking.
Tours can be even support offline playback, so a pitch at a venue or on a trade-show floor never depends on the network.
Every publish is versioned. Changes ship fast, and a bad one can be rolled back without taking the live tour down.
No per-seat licences, no feature paywalls, no waiting on 4th-party vendor roadmap for the thing you need next quarter.

Meridian Rendering Engine is the part of Realview that turns a 360° space into pixels in a browser. It handles the entire file-to-frame lifecycle — what gets requested, in what order, at what quality, and when it is allowed to touch the GPU.
A good rendering engine is the entire difference between a tour that feels instant and one that makes a guest wait on a loading spinner. And ours is the best.
Most tour software uses “HDR” to describe capture: bracket, merge, then flatten everything back into SDR. Meridian keeps going. On a compatible HDR display, sunlight, windows, reflections, and practical lights can rise beyond "paper white" with genuine display headroom.
It builds that result from the same authoring pipeline as SDR, so cleanup, sharpness, loading, video hotspots and behavior remains reliable. No second viewer, no fragile HDR tile tree and no performance or loading hit.
Meridian's adaptive scheduling is ahead of the curve. It measures screen area, projects every tile into your viewport and reveals sharp detail in the field of view where it actually matters.
Meridian tracks the camera's velocity and makes intelligent decisions about where you are heading. Detail you're looking for is already on the GPU when you arrive, so a fast pan stays sharp and detail appears instantly.
A phone on hotel Wi-Fi and an M-series desktop are not the same machine, so they do not get the same treatment. Meridian profiles the hardware on arrival and picks its memory, bandwidth, and decode budgets to match.
A still panorama does not saturate the hardware. The frame loop shuts itself off when nothing is moving and picks up on input. Texture uploads are metered against the frame budget so loading never costs you a frame drop.
lower time to usable detail
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.
We tested Meridian against industry-leading panorama viewer using the same byte-for-byte identical set of tiles. 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 simply 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
Built with purpose.
The people who wrote the renderer are the people shooting your property. “Can it do this?” is merely a question of time.
Tell us about the property — we’ll come back within 24 hours with an approach, a timeline, and a price.