Pilot test environment

Your starting package. Ready to test.

Twelve pilots connect Star Jumper, ground networks and Galaxity workflows. Begin with a reference configuration, run the analysis agents and explore how the next stage changes the solution.

YOUR TEST ENVIRONMENT

Choose a pilot. Run the starting package.

Reference inputs are provided for every pilot. Change the scale or test condition, then compare the current configuration with growth. No technical file is needed.

Loading pilot controls…

NETWORK IN MOTION

Your network. From orbit to Earth.

Illustrative test environment

Explore satellites, reference ground gateways and the campus service path. The figures below use your selected pilot inputs. Constellation layouts and moving links illustrate the architecture; they do not predict orbital contacts.

Drag to explore the constellation · select a spacecraft or ground endpoint

Visible layers
Connected pilot devices—
Primary utilization—
Window delivery—
Gateway utilization—
Inspect a network role

Earth & constellation

Drag the globe or use arrow keys to change the view. Select a satellite or ground endpoint to inspect its role.

Current configuration

Loading selected pilot preview…

Cyan: satellite and ground architecture. Green in the globe view: reference ground path. Amber: alternate path or capacity review. Red: interrupted campus primary path.

Constellation growth is a view option; orbit bands and motion are illustrative, not to physical scale. Connected-device counts and capacity figures come from the pilot. Cable corridors illustrate transatlantic, transpacific and Asia-Pacific connections, not exact cable routes. This is a local visualization, with no live spacecraft telemetry or device control.

Cinematic scene and spacecraft: original concept artwork. Globe Earth texture: NASA Blue Marble / Earth Observatory.

Link, contact window & recovery assumptions
Gateways, telemetry & operating scale
Evidence, history & security inventory

Sample history is synthetic. A supplied comparison remains unverified until its source and measurement method are reviewed.

Review or change the numerical targets

These reference targets are test assumptions. Client acceptance criteria are agreed during scoping.

The calculations run in your browser. Inputs are not transmitted or saved by this test environment. Keep a report by downloading it.

Built into the starting package

A coordinator, specialist agents and reusable models.

The deterministic analysis agents run the engineering reference models in your browser. The package is ready for test scenarios; trained AI models, live collectors and operational integrations are scoped separately.

Coordination

Pilot coordinator

Star Jumper

Contact-window agent · Mission-delivery agent · Buffer & recovery agent

Ground networks

Path-continuity agent · Gateway agent · Terminal-energy agent

Galaxity

Evidence agent · Track-record agent · Telemetry agent · Crypto-inventory agent

Shared network

Capacity agent · Path-latency agent · Operations agent · Scaling agent

18 reusable engineering reference models

01

Traffic demand

Devices × average traffic per device.

02

Capacity & headroom

Offered load against configured aggregate capacity.

03

Propagation delay

Distance divided by light speed, with fiber propagation factor.

04

Packet serialization

Packet size divided by available link rate.

05

Path latency

Propagation, serialization and supplied processing delay.

06

Contact duty cycle

Usable minutes divided by the modeled window.

07

Window delivery

Effective link capacity over usable contact time.

08

Buffer accumulation

Unserved offered traffic over the modeled window.

09

Backlog drain

Backlog divided by spare service rate during a usable contact.

10

Alternate-path capacity

Primary loss and fallback contribution with capped delivery.

11

Window continuity

Primary time coverage combined with independent fallback availability.

12

Operating energy

Device power × device count × elapsed time.

13

Gateway aggregation

Projected throughput per gateway and gateway headroom.

14

Telemetry pipeline

Device event rate against collection capacity; event volume.

15

Evidence completeness

Available evidence fields against required fields.

16

Track-record comparison

Supplied before/after incident counts and source status.

17

Crypto migration inventory

Known dependencies marked ready against inventoried dependencies.

18

Support coverage

Configured devices per operator against the supplied support limit.

From this test to your environment

Keep the useful model. Add the evidence and integration.

Start with the value chain and a selected flow. Define approved data sources, network boundaries, representative conditions and measurable acceptance. Then connect the scoped collectors, validate the interfaces and expand against the scaling gates.

01

A defined now analysis

Capture the existing service path and the operating evidence that describes it.

02

A focused customer pilot

Replace reference assumptions with approved inputs and measured results for the agreed outcome.

03

An accepted expansion plan

Record delivery, capacity, recovery and operating requirements before adding sites or devices.

Technical foundations: NASA optical communications · NIST post-quantum cryptography.