Cyango

A property photographer scans an apartment. The client likes the result, then asks for a guided tour, floor plans, a contact form, and a version that works on a tablet offline. The next enquiry comes from a museum. It wants visitors to explore a fragile object, hear the curator explain its history on site with augmented reality, and continue the experience at home.

A tourism operator needs to show several locations, booking links, multiple languages and embed it quickly on their website. A retailer wants a showroom with product hotspots and a path into checkout. A heritage team wants a scanned chapel paired with archival photos and audio guides. An events agency needs a password-protected preview for a client, then a public launch embed two weeks later.

What do these all have in common?

None of them are buying a file or a vibe coded supersplat wrapper. They are buying an outcome. Preferably one that can scale their business. A ready to use virtual tour experience so they don't worry. That's why they are paying YOU.

From Creation to Distribution

Cyango covers most of that loop in one platform. Upload raw scans or source video and xr/converter generates the Gaussian Splat. xr/studio is where you add UI, media, interactions, and everything else the project needs. Publish once for web, mobile, AR, and VR, or push the same experience to digital signage and managed device fleets. When checkout is part of the brief, our own payments gateway is built in, with no Stripe or third-party payment stack required.

Drag splats, whether generated in xr/converter or imported from an external pipeline, into multi-scene Stories. Add buttons, popups, timeline animations, scene transitions, quizzes, 360° media, video, audio, and multilingual content from a visual editor. Preview in the browser before publish. For teams using AI-assisted workflows, compatible agents connect through MCP and work inside the editor rather than regenerating the whole project on every revision request.

Create: wrap captures in experiences that clients actually buy

A splat viewer answers one question well: "Can I look at this capture from different angles?"

That is enough for internal review, portfolio sharing, or a quick wow moment in a meeting. It is not enough for serious sales.

The splat is one scene among several. The required experience mixes captured reality with conventional media, UI, and business logic. The same project must publish to web, mobile, AR, and offline tablets without maintaining separate builds for each channel.

Walk through a few sectors and the requirements stack up quickly:

Property. Import the splat. Set an opening camera animation so the first view matches the listing photography. Add hotspots on kitchen, bathroom, and storage. Drop in a floor-plan image or video scene. Place a contact form and agency branding on the closing scene.

Museum. Place the object splat in a scene with controlled viewpoints so visitors cannot accidentally clip through fragile geometry. Attach curator narration to specific camera positions. Enable AR on supported phones so the object can be placed on a plinth or table in the gallery. Add a second scene with archival photos and provenance text.

Tourism. Build one Story with a scene per location. Switch languages inside the same project instead of cloning three separate builds. Add booking buttons that link out to the operator's reservation system. Track which scenes visitors reach so marketing can see whether the coastal stop outperforms the vineyard stop.

Training. Open with a splatted facility overview so workers orient in the real environment. Branch into procedure scenes with video, diagrams, and quiz checkpoints. Update content when safety rules change without rebuilding a custom app.

Retail and campaigns. Route from a splatted display wall into product detail popups, a configurable 3D model, or an XR Store. Password-protect unreleased work for client review, then flip to public on launch day. Clone the template for regional variants without rebuilding from scratch.

Workspaces support role-based permissions and shared asset libraries. Stories can be cloned and adapted. Non-developers and clients can edit the project next month without much effort.

None of this is exotic engineering on its own. Together it is the kind of work that used to mean a game-engine project, a native app, or a patchwork of embeds held together by a developer on retainer.

Behind that publish button sits an infrastructure

Building the experience is half the job. The other half is getting it onto the devices your clients and their audiences already use, and keeping it running there without you maintaining separate builds for every channel.

When you publish from xr/studio, Cyango processes every asset in the Story through a cloud pipeline: splats are optimized for web delivery, video and audio are converted for streaming, 3D models are compressed with multiple quality levels, and everything is pushed to a global CDN. xr/player runs the same published Story in the browser on desktop, phone, AR, and WebXR headsets from one link. The runtime adapts what it loads to the device and connection, so a phone on mobile data and a desktop on fiber both get a workable experience without you shipping two versions.

Distribution options sit on the same publish. Host on Cyango with password protection, preview links, and analytics. Export a self-contained package when IT wants to run it on their own infrastructure. Install as a PWA on tablets and kiosks so the full experience caches locally after one online load. Then extends the same publish to digital signage and managed device fleets when the deployment leaves the browser.

The radiance field ecosystem solved capture. The commercial value now lives in what happens after: processed assets, reliable delivery, and one publish path to web, mobile AR, VR, offline install, and fleet rollout. 

That is a creation-to-distribution problem, not a viewer problem.

References

• Cyango: https://www.cyango.com