SpaceNoneSuchThe platform layer

Comms orbiter · SaaS · research

More than a launch. A node in orbit.

Training, tourism and education are the front door. Behind it, the same launch and the same routing turn SpaceNoneSuch into something bigger: a communications orbiter, a delay-tolerant software platform built on BuzzMe's vault-routing, and a research node for how we might one day talk across space, or across caves on another world. The architecture is already here.

One-to-many broadcast, live

One message, every endpoint

SpaceNoneSuch orbiterbroadcast hub · vault
Satellitesat-to-satellite
Aircraftsat-to-air
Ship at seasat-to-sea
Ground stationsat-to-land

Broadcast

4 of 4 links

Status

Fanning out

Bundles delivered

0

Mode

Nominal

The orbiter does not forward to a single next hop. It broadcasts the same vaulted bundle one-to-many to every endpoint in view at once: sat-to-satellite, sat-to-air, sat-to-sea and sat-to-land. Force an outageand the link that drops simply holds its copy in the vault until the window returns, while the other branches still deliver. NASA's high-rate delay-tolerant networking (HDTN) is built for exactly this kind of one-to-many store-and-forward.

How high sets how wide

Reach is set by altitude.

A comms orbiter only reaches what sits over its horizon, so its footprint grows with altitude. Drag from low orbit up to geostationary and watch the coverage cap widen, while the round-trip delay stretches and every pass lasts longer. The trade is always reach against delay.

LEOMEOGEO

Altitude

610 km

Regime

LEO

Footprint

4.4% of Earth

Round trip

4 ms

In view

13 min/pass

Schematic, not to scale: geostationary orbit sits far higher than drawn. Figures are geometric, taken at the horizon looking straight down, so usable coverage is a little smaller once you require a workable elevation angle. One orbiter is only a slice at any instant, which is exactly why global service takes a constellation.

Why a constellation, live

One sees a third. Three see the world.

A single orbiter only reaches what sits over its horizon, about a third of the planet from geostationary orbit. Space three of them 120 degrees apart and their footprints tile the whole equatorial belt. Let them cross-link and a bundle can hop orbiter to orbiter to the far side of the Earth, with no single point of failure.

Orbiters

1

Instant reach

~1/3 of the globe

Blind spots

Most of the planet

Resilience

Single point of failure

Schematic, not to scale. Real geostationary orbit sits far higher than shown, and continuous global service still needs the constellation plus store-and-forward to bridge the gaps between passes. The classic result holds: three satellites 120 degrees apart cover the world, poles aside.

Extending the reach

A GEO hub, a swarm of CubeSats.

A single geostationary orbiter is the always-on backbone, but it sits over the equator, so the poles and the deep shadows fall outside its view. Low-flying CubeSats reach into exactly those gaps and feed their traffic back up to the hub over optical cross-links. A proven pattern, not a concept.

GEO hubCubeSat

Proven in orbit

  • NASA TDRS — geostationary relays that carry traffic for spacecraft, including the ISS, that cannot see a ground station directly.
  • ESA EDRS — a GEO node collecting from low-orbit satellites over optical cross-links and handing the data down: the same hub-and-extender shape.

The honest caveats

  • The cross-link up to GEO is the hard part: a CubeSat has tiny power and a small aperture across a 36,000 km haul, so optical links and precise pointing do the heavy lifting.
  • A CubeSat is only overhead for minutes, so coverage is intermittent. Store-and-forward carries the bundle until the next pass.
  • It broadens where you reach, not how fast. Adding relays fills gaps; nothing beats the speed of light.

Why SpaceNoneSuch and BuzzMe are hard to split

Inseparable by design

Store-and-forward is not exotic. It is exactly how BuzzMe already moves messages across a network whose shape keeps changing, using its own vault-routing. Point that same idea at space and the pieces line up: a message waits in the vault until the next contact window, then hops onward. That shared backbone is why the two are hard to pull apart, and it is drawn tighter on purpose.

BUZZME

One ring over everything

The halo that crowns the emblem is the origin cue: BuzzMe is the ring, SpaceNoneSuch sits inside it. One mark, one account, one network.

  • Every registrant signs in through BuzzMe. No BuzzMe account, no launch seat, no training, no platform access.
  • Every message, email and call runs on BuzzMe and its vault-routing. There is no side channel.
  • The orbiter flies purpose-built payloads that only speak the BuzzMe protocol, so the ground segment and the space segment are the same network.

Three roles, one orbiter

What the platform can be

Role one

A communications orbiter

SpaceNoneSuch does not only send people up, it keeps a node up there: an orbiter that stores and forwards traffic across broken, high-latency links. And it does not forward to one place, it broadcasts one-to-many, sat-to-satellite, sat-to-air, sat-to-sea and sat-to-land in a single pass.

Proven today

  • Delay/disruption-tolerant networking, including NASA's high-rate HDTN implementation of the Bundle Protocol, is operational on real spacecraft.
  • Optical inter-satellite links and relay satellites fly today, route around the horizon, and fan one signal out to many receivers.

Still a proposal

  • An independent SpaceNoneSuch orbiter, launched from the harbour, is the ambitious part.
  • Cave-to-cave relays on another world are a long-horizon goal, not a product.

Role two

A software platform (SaaS)

BuzzMe already routes messages over changing topology with its own vault-routing. Offer that as a service for delay-tolerant traffic: store-and-forward messaging, relay capacity, and vaulted delivery that survives an outage.

Proven today

  • BuzzMe already handles topology and vault-routing for its own network.
  • Selling routed, stored, guaranteed-eventual delivery is a normal business model.

Still a proposal

  • Extending BuzzMe routing to real space links needs spectrum, licensing and hard engineering.
  • Billing and quality-of-service for delay-tolerant traffic is new ground.

Role three

A research platform

A place to test the hard parts in the open: optical relay through reflectors, RF fallback when dust or atmosphere blocks the beam, and comms for people living inside a planet rather than on it.

Proven today

  • Hosted payloads and comms testbeds are a standard way to fly experiments.
  • Optical-comms and DTN experiments already run on orbit.

Still a proposal

  • A dedicated SpaceNoneSuch research orbiter is a build, not a given.
  • Laser-plus-reflector relay and habitat comms trials are early-stage research.

The no-budget orbiter

A layered stack that wins in software

No budget for lasers, gimbals or a fleet, so the orbiter leans entirely on what is already free and proven (NASA's open HDTN and Contact Graph Routing) and puts every scarce dollar of ambition into software. Each layer below names the grand idea, then the real, grounded technology it maps to, and whether it is proven, buildable now, or still simulated.

The thesis

You cannot out-build SpaceX or Amazon in the physical realm, so do not try.

Inherit the spacecraft-grade transport that already exists and is free, and compete where a lean operator can actually win: in software, on the routing, on the waveform. Uncle Sam's HDTN and CGR, driving any surface (even a printed one), is the edge.

Contact Graph Routing, live

Illustrative schedule

Held, then forwarded on the next pass

The stack above names CGR. Here it is working. The routing engine knows when each link will next open, so it parks a bundle at the current node and forwards it the instant the next contact window arrives. Nothing is streamed in real time, and nothing is lost while a link is dark.

Cave relay
Orbiter
Deep-space relay
Earth
0m6m12m18m24m

Cave relay Orbiter

Orbiter Deep-space relay

Deep-space relay Earth

Clock

T+00:00

Bundle at

Cave relay

Status

Held — awaiting the Orbiter window

Delivery

T+10:00

Illustrative schedule: real contact windows come from orbital mechanics and a ground-station plan, not these numbers. The behaviour is the point. Miss the first pass and CGR simply re-books the bundle onto the next window, so delivery slips later instead of failing.

The long-horizon thesis

Live inside a planet, not on it

If the surface of Mars is deadly in seconds, the answer may not be a dome on top of it. Go under. Start in a dugout, adapt inside a lava tube, and live within the planet rather than on it. Roads, a walk, a visit to a neighbour, all of it turns inward. The needs shrink to three: light, food, and a way to find and talk to the caves around you.

Light and food are somebody else's hard problem. The third one, finding and talking to your neighbours with no line of sight to Earth, is exactly what a store-and-forward relay network is for. That is the piece SpaceNoneSuch and BuzzMe can actually start on now.

Lava tubes as radiation-shielded habitats are a serious, current planetary-science idea. Crash-landing into and living inside another world is not, yet. This is the direction, not a timeline.

Laser, mirrors, and one honest correction

Reflectors bend a beam, they don't punch through weather

Mirrors will not push a laser through a dust storm. Scattering is the problem, and a mirror does not un-scatter light. What reflectors do well is bend a beam around a corner in vacuum, where nothing is in the way. So the honest design is optical relays in clear space, an RF fallback for when dust or atmosphere blocks the beam, and store-and-forward underneath it all, so a lost window only delays a message, never loses it.

This is a concept in active development, a presentational brief rather than an operating service. The orbiter, the SaaS and the research platform described here depend on real spectrum, licensing, partners, capital and engineering. Nothing on this page is a live product or a booking.