No platform dependency
Your imagery is not held by a vendor who can change terms, raise prices, or remove a listing. The map, the tiles, the viewer and the imagery are all yours, on your servers.
Self-hosted mapping platform
Own Your Map — Not a Subscription to Someone Else's.
Bayon Atlas is the platform behind BayonShield's own 360° tours: camera-card ingest, human-reviewed privacy blurring, automatic virtual walkthroughs, and a self-hosted vector map that never calls a third-party mapping API. Licence the stack and run it on your own hardware.
Why licence it
Built to Be Owned, Not Rented
Most immersive mapping runs on someone else's platform, at someone else's prices, under someone else's terms. Bayon Atlas is the opposite arrangement.
Privacy handled before publication
Faces and plates are obscured before an image can go public — reviewed by a person in both directions, not resolved on complaint after the fact.
No per-view or per-request costs
Nothing meters map loads or panorama views. Page loads never call Google, Mapbox or any external mapping API — no API keys, no per-request billing.
Ordinary cameras, ordinary hardware
Consumer 360° cameras, processed with open-source tooling on standard CPU servers. No GPU, no vendor SDK, no per-seat desktop licence.
Open-source foundations
OpenStreetMap, Protomaps, MapLibre, PostGIS, FFmpeg, ExifTool, libvips, PostgreSQL and Laravel — inspectable, replaceable, and not going away.
Originals never reachable
Raw captures sit outside every web-server location and are served only through an authenticated allow-list. There is no URL that returns an unedited file.
Anonymisation pipeline
Privacy Is the Hard Part. We Built It Properly.
Detectors perform badly on raw equirectangular imagery, where faces near the top and bottom of frame are severely distorted. Bayon Atlas projects each panorama into twenty-four overlapping perspective views — eight headings across three pitch angles at 100° field of view — and runs detection across all of them.
Detect
YOLO-family face and plate models run across the twenty-four views on CPU. Duplicate hits from overlapping views are merged, keeping the widest estimate.
Review
Detection produces an editable list, not a finished result. Draw an ellipse or rectangle over anything missed — a turned head, a document, a screen, a name badge — and dismiss anything wrongly flagged.
Approve & publish
Applying blur produces a candidate. Nothing public changes until it is approved — then every thumbnail, preview, viewer image and share card is rebuilt from the anonymised version.
- Dismissals are permanent — re-running detection matches new hits against previous dismissals by overlap and carries them forward
- Two redaction styles: pixelation plus a Gaussian pass under a feathered mask for faces and plates; flat fill for documents, screens and signage
- Reproducible output — the published image is a deterministic function of the source plus the region list
- Irreversible in the published file — obscured pixels replace the originals rather than layering over them
- Sensitivity cascades: a global default, a per-place override, and a per-run override
- An interlock prevents publishing a scene whose region list changed since blur was last applied
- Audit trail — every suppressed detection records the user, the reason and the region
For the operator
From Camera Card to Published Tour
The whole capture-to-publish workflow, without the camera-to-phone-to-workstation-to-cloud round trip.
Direct camera-card ingest
Insta360 .insp files — raw dual-fisheye frames straight off the card — are stitched to equirectangular on the server with FFmpeg. No phone app, no vendor desktop software, no SDK, no cloud service.
Bulk import, folders become floors
Hundreds of scenes in one ZIP, processed in capture order, hardened against path traversal and zip bombs. A subdirectory is read as a building level, so a multi-storey property needs no manual setup.
Tolerant metadata & GPX
GPS, timestamps, camera make and pose read across EXIF, XMP and Composite tags in every format cameras invent. GPX tracks geotag by timestamp with per-session clock-drift correction and draw route lines on the map.
Automatic walkthrough building
For linear captures — roads, trails, riverside paths — heading is derived from the GPS track and every scene is linked forward and back in one action. Chains break across GPS dropouts and collapse stationary bursts.
Visual arrow aiming
Field GPS is often several metres out, which visibly aims arrows at walls. Click in the panorama where the next scene actually is, then mirror the aim onto its return link in one action.
Places, tags & publishing control
Businesses, properties, hotels, markets and trails each get a page — contact details, hours, amenities, inherited tags, drag-to-reorder scenes, per-scene opening view, and draft / unlisted / public states with soft deletion.
For the visitor
A Public Experience That Owes Nobody Anything
No account, no sign-up, no cookie wall, no app — and no third party learning where your visitors look.
Self-hosted coverage map
OpenStreetMap data served as a single vector-tile archive from your own server, with clustered markers, route lines, and filters by province, place type, tag or capture date.
Walk the space, don't scroll it
Move between connected scenes by clicking arrows laid on the ground ahead of you. Multi-floor buildings offer level-by-level navigation, with a minimap showing your position.
Lands facing the right way
Each scene opens on a framing the operator chose, so visitors land looking at what matters rather than at a wall — with smooth transitions that arrive already oriented.
Permalinks & share cards
Every scene and place has a permanent URL, plus short links on a dedicated domain for messaging and print. Share cards unfurl correctly on social and chat apps, generated from the scene's own imagery.
Mobile without an app
Full-screen viewing, zoom, drag-to-look, keyboard and touch support — in the browser, on any device.
A published removal route
Anyone can see how to request removal of an image — a documented process rather than a support address that may or may not answer.
Stack & operations
What You Actually Run
One installation, one organisation's content, on infrastructure you control.
- Runs on an ordinary Linux server — Debian 13 is the tested and supported platform
- Virtual private server or dedicated hardware; both are fine
- No GPU required — everything runs on ordinary CPU today, and future releases may take advantage of a GPU where one is available
- Installation, configuration and handover are covered as part of the licence
Interested in licensing Bayon Atlas?
Bayon Atlas is licensed for a one-time cost. Tell us about your market, your coverage plans and your hosting, and we will talk through what a licence would look like.