JUPITER / FIELD SYSTEMS Jupiter concept · Metis V03 renders
J JUPITERCOMMS

PORTABLE FIELD INFRASTRUCTURE

Communications,
brought
together.

Maps. Shared files. Sensors. Team services.
A common workspace, close to the people using it.

Explore the platform ↓

An independent project built around local operation.

NEW / Explore the Metis assembly
JUPITER / SYSTEM STUDY 01
JUPITER FIELD PLATFORM
01NETWORK
02COMPUTE
03SERVICES
04STORAGE
LOCAL FIRST⏻
+ Modular concept. Not an as-built drawing.
ONE LOCAL WORKSPACEIDENTITY & ACCESSMAPS & PLANNINGFILES & SERVICES

01 / METIS SENSOR PLATFORM

See the assembly.
Explore every layer.

Meet Metis, the sensor-platform side of Jupiter. Explore the enclosure, camera head and supporting structure through the finished V03 renders.

METIS / DESIGN IN DETAILV03 RENDER COLLECTION

Assembled → exploded → assembled. A ten-second study of the Metis design.

DESIGN VISUALIZATION

TAKE A CLOSER LOOK

The model is yours to explore.

Rotate the assembly, separate the layers and inspect individual components. Open the 3D explorer when you’re ready.

Loads a 26 MB model on request.
The film and stills remain available on any device.

Design preview, not an as-built verification. Selected geometry, finishes and cable paths remain provisional. Exploded spacing illustrates the assembly rather than a verified disassembly sequence.

02 / THE FIELD WORKFLOW

A shared picture.
Where the team works.

Bring local services to the field network. Add remote access when an Internet path is available. Keep the operator experience familiar.

ILLUSTRATIVE WORKFLOW
FIELD CLIENT AFIELD CLIENT BJUPITERJ REMOTE ACCESS CONCEPT ANIMATION · NO RF OR LIVE TELEMETRY
N ↑ LOCAL NETWORK / DIAGRAM NOT TO SCALE

EXPLORE TWO CONDITIONS

Local services.
Remote reach.

The local workspace stays at the centre. An available Internet path extends access to authorized remote users.

  1. 01Connect to the field network
  2. 02Use an enrolled identity
  3. 03Open authorized services
Illustrates the proposed connected architecture.

03 / INSIDE THE PLATFORM

Different functions.
A deliberate system.

Transport, identity, applications and storage have distinct responsibilities. The architecture brings them together without treating network presence as permission.

Conceptual layer model. Engineering geometry and final packaging are separate design work.

01TRANSPORTNetwork paths
02IDENTITYPeople & devices
03APPLICATIONSMaps · files · team services
04STORAGELocal data & recovery

04 / A PROJECT IN DEVELOPMENT

Built in the lab.
Prepared for the field.

Jupiter brings together local infrastructure, mapping, planning and field applications. Development proceeds through measured tests, documented results and recoverable changes.

The local identity pilot is deployed. Device enrollment, extended field acceptance and public video delivery are continuing work. MANET integration awaits hardware testing.

Open the enrolled-user portal ↗

Portal access currently requires Jupiter’s local network or an approved Tailscale connection and an enrolled account. Public operational access is not released. This showcase collects no login credentials.