Mysterio.tech · Intelligent Entertainment Robotics

Move spatial media where the show needs it.

Human swarm controller behind four production monitors directing a larger group of eight-leg SpiderBot Mark 2 units whose ProjectionPods converge on the central concert stage
ILLUSTRATIVE CONCEPTHUMAN CONTROLLED
CONTROLLED ZONESNOT A DEPLOYED SYSTEM
V1 DESIGN TARGETProjection: rig + perchVisionPod flight: controlled zone only
SpiderSwarm platformSpiderBot productProjectionPod + VisionPod payloads

Mysterio is developing SpiderSwarm, a proposed control platform for modular SpiderBot units with swappable ProjectionPod and VisionPod payloads across stages and venues, all managed as one operator-controlled system.

See the modular system ↘Try the control concept →

ILLUSTRATIVE CONCEPT Renderings and software simulation only. V1 functions, performance, and operating approvals remain to be built and validated.

01 / More than Meets the Eye

Swarm Controlled Experience Design

The credible first product is a modular spatial-media system: professional projection where power, cooling, structure, and serviceability are available; lightweight vision and calibration where mobility creates real value.

Fixed infrastructureCreative coverage is constrained by the original rig and venue geometry.

Bespoke resetsEach venue creates another placement, alignment, and commissioning problem.

Split controlMobility, media, calibration, telemetry, and safety are managed in separate layers.

Product architecture

One platform. One base. Swappable payloads.

PLATFORMSOFTWARE PROTOTYPE

SpiderSwarm

Operator software for mapping, grouping, cueing, health, and safety-state orchestration.

PRODUCTDESIGN TARGET

SpiderBot

A proposed modular robotic unit with a common payload interface and rig / perch / controlled-flight modes.

PAYLOAD / PDESIGN TARGET

ProjectionPod

A proposed professional projection payload for tethered rigged and perched use.

PAYLOAD / VDESIGN TARGET

VisionPod

A proposed lightweight camera, depth-sensing, and calibration payload for mobile capture and controlled flight.

SpiderBot Mark 2 eight-leg carrier beside distinct ProjectionPod Mark 2 and VisionPod Mark 2 modules and the shared PodDock interfaceCONCEPT RENDER · COMMON INTERFACE PROPOSED

02 / Modular hardware

Swap the payload.
Keep the node.

The proposed PodDock Mark 2 uses keyed guides, kinematic alignment, preload and independent secondary retention so a trained technician can assign the right payload to the right operating envelope.

P / PROPOSED

ProjectionPod

Professional projector, gimbal, cooling, and calibration camera. Design target: tethered AC/data operation on rated rigs and perches.

V / PROPOSED

VisionPod

Lightweight video, depth, and tracking sensors. Design target: capture and calibration from ground, perch, rig, or controlled flight zones.

03 / Proposed Field Service

On Show Day: Scan Venue and Deploy Swarm

VisionPod captures venue geometry and approved operating zones. The operator then assigns payloads and roles, deploys each SpiderBot to a rated position, and completes calibration and health checks before the show.

  1. Scan venueCapture surfaces, obstacles, reference points, and controlled operating zones.
  2. Configure swarmAssign ProjectionPod and VisionPod payloads to approved positions and roles.
  3. Deploy + verifyConfirm placement, lock, identity, calibration, health, and permitted mode.
Four-panel Mark 2 service sequence showing a secured eight-leg SpiderBot, guarded PodDock release, keyed VisionPod seating, and verified retention
ILLUSTRATIVE CONCEPT Proposed module preparation within show-day deployment · interface unbuilt

04 / SpiderSwarm control

You Command
the Swarm.

Select a SpiderBot, an operating group, or the entire fleet. This working software interaction demonstrates scope selection, command-state changes, operator authority, and a simulated E-stop—without claiming a hardware connection.

SOFTWARE EVIDENCEInteractive prototype · no hardware connected

SPIDERSWARM CONTROL / SOFTWARE PROTOTYPEOPERATOR AUTHORITY · ONLINE

WORKING INTERACTION · NO HARDWARE CONNECTED

SELECTED

SPIDERBOT 02

1 / 08 NODES

HUMANOPERATOR
02ProjectionPod · PERCH
WORKING EVIDENCE Scope selection + UI stateILLUSTRATIVE Commands + emergency stopNOT CONNECTED Hardware + live telemetry
EVENT LOGREADY — awaiting operator command

05 / Proposed show workflow

FUTURE STATE

Move. Lock.
Map. Play.

Mobility changes placement, not authority. Playback begins only after the unit is stationary, retained, mapped, and approved by the show operator.

  1. Move

    During load-in, place each unit at its approved service, rig, or perch position. Projection stays dark while the unit moves.

  2. Lock

    Confirm rated structure, tether or retention, payload mount, power/data, and the permitted operating mode.

  3. Map

    From a stationary state, load venue geometry and calibrate pose, surfaces, brightness, color, and overlap.

  4. Play

    Run approved media cues while the identified operator retains safe hold, blackout, and emergency-stop authority.

06 / Deployment matrix

The payload defines
the permitted mode.

V1 keeps professional projection on rated rig and perch positions. Controlled flight is a VisionPod research mode inside defined no-audience zones.

Mark 2 comparison of a body-tethered ProjectionPod SpiderBot on an overhead rig, a secured perch unit, and a VisionPod-only unit inside an empty controlled flight zone
ILLUSTRATIVE CONCEPT V1 prioritizes rated rig and perch placement; controlled flight remains VisionPod-only proposed R&D.

Swipe horizontally to compare operating modes

Operating envelope
RigV1 priority
PerchV1 priority
Controlled flightResearch path
Primary payload
ProjectionPod / VisionPod
ProjectionPod / VisionPod
VisionPod only
Power + data
Tethered
Tethered or bounded local
Onboard, lightweight target
Positioning
Rated overhead point
Rated scenic / venue structure
Defined no-audience zone
Readiness claim
DESIGN TARGET
DESIGN TARGET
PROPOSED R&D

07 / Safety plane

Mobility only matters if control is bounded.

PROPOSED Architecture requires validation and independent safety review.

AUTH

Human authority

Hold, blackout, land / park, and emergency stop remain available to an identified operator.

ZONE

Hard boundaries

Rated placement, physical tethering where applicable, and software-defined zones constrain permitted motion.

MODE

Payload interlock

The proposed module identity prevents a payload from being assigned to an unapproved operating mode.

FAULT

Fail-safe state

Loss of link, pose confidence, power margin, or thermal headroom triggers a predefined safe response.

08 / 90-day feasibility sprint

Earn the seed round with evidence.

The sprint turns the concept into measured answers on photometrics, thermal load, synchronization, fault response, and operator workflow. Each phase ends in a documented go / no-go gate.

FUTURE STATE 90-day timing is a proposed planning target.

Planned engineering bench with an eight-leg SpiderBot Mark 2 secured to a test fixture, ProjectionPod Mark 2 aimed at a calibration wall, instrumentation, and a separate VisionPod
FUTURE STATE · PLANNED TEST Instrument plan only · no physical test represented
  1. DAYS 0–30Phase One

    Bench proof

    Measure payload mass, thermal load, acoustics, photometrics, power, and the tool-less interface.

    GO / NO-GO GATE
  2. DAYS 31–60Phase Two

    Two-node proof

    Demonstrate repeatable placement, optical calibration, synchronized media, health telemetry, and safe hold.

    GO / NO-GO GATE
  3. DAYS 61–90Phase Three

    Controlled venue proof

    Run a non-public mock show with a production partner, documented operating procedures, and stop drills.

    GO / NO-GO GATE

Controlled proof partner

Host Mysterio’s first SpiderSwarm feasibility sprint.

We’re looking for one production partner, one controlled venue, and the engineering collaborators needed to turn design targets into measured evidence.

Discuss the engineering sprint ↗Request the investor brief →