Boston Global / Opportunity for Rhea Space Activity
Rhea Space Activity × ReOrbit · Proposal for discussion

Make AutoNav part of the sovereign satellite stack.

A potential technology partnership that takes RSA’s navigation capability into ReOrbit programmes—and creates a path from paid engineering to licensing and ongoing support.

Explore the opportunity ↓
Prepared for Rhea Space Activity5 November 2026
Proposed AutoNav integration pathwayRSA AutoNav connects through a paid qualification study to ReOrbit spacecraft, supporting sovereign customer missions. Compatibility and customer awards remain to be established.AutoNavPROPOSED HOSTED CAPABILITYReOrbit spacecraft programmesQUALIFY → INTEGRATE → LICENSE → SUPPORT
Conceptual partnership architecture. No integration or commercial agreement is assumed.
01 / THESIS

A route to recurring revenue from a capability RSA already develops.

The proposition is to qualify AutoNav for a specific ReOrbit spacecraft, then build a repeatable commercial offer around that integration.

The opportunity for RSA

Become an embedded navigation technology partner.

Earn funded engineering and qualification revenue first. Where the capability meets the mission need, progress to a platform licence or per-equipped-spacecraft fee, with separately priced maintenance and mission support.

Potential reach extends across selected GEO and LEO customer programmes, subject to platform fit, procurement and export permissions.

The value to ReOrbit

Add a dissimilar navigation capability to its sovereign offering.

Explore an optical alternative or backup to GNSS-dependent navigation, supporting customers that value resilience, autonomy and control of critical infrastructure.

The commercial test is whether that additional capability meets an actual mission requirement at an acceptable integration and lifecycle cost.

RSA’s entry point is a funded technology work package. The business can be pursued without RSA owning or financing the satellite network.
02 / FIT

Navigation IP meets a software-defined spacecraft platform.

RSA’s AutoNav focus and ReOrbit’s platform approach create a credible reason for a direct engineering conversation.

Rhea Space Activity

AutoNav + integration expertise

Optical navigation software, state estimation, mission adaptation and qualification. JAM-related optics or computing may be relevant if the host requires additional hardware.

ReOrbit

Spacecraft + customer mission

Flight software, cameras, onboard processing and the spacecraft interfaces needed to host and validate a third-party navigation application.

RSA’s funding and VANGUARD announcements support the AutoNav-led thesis. ReOrbit publicly describes software-defined satellites and regional 5G NTN connectivity. These disclosures establish strategic alignment, not compatibility or a design win. Source notes.

Start with one host configuration and one navigation requirement. Establish the camera, compute, accuracy, timing and reference-data requirements before promising a software-only solution.
03 / APPLICATIONS

Two practical ways to develop the relationship.

A
Lead with the spacecraft

AutoNav on a selected ReOrbit mission

Qualify an optical navigation application for a funded host mission. Demonstrate a useful alternative or backup navigation function, with measured resource use and agreed acceptance criteria. Use the outcome to define a repeatable integration package and licence structure.

Commercial route: paid feasibility → funded qualification → production licence or hardware package → ongoing support.

B
Develop a customer mission

Navigate without GPS. Communicate beyond terrestrial coverage.

Investigate a joint offer for maritime, aerial or ground platforms: RSA provides navigation resilience; a suitable ReOrbit service provides connectivity for command, coordination and reporting. Start with a named customer use case and validate the navigation and communications performance separately.

Commercial route: customer discovery → joint demonstration → defined product and service workshare.

These paths are complementary. A communications network does not itself validate RSA navigation, and satellite connectivity is not automatically immune to disruption. Space-domain awareness, RPO and QLOAK can remain later, separately funded options when a customer mission supports them.

04 / ECONOMICS

Build a supplier business with several ways to earn.

The immediate commercial objective is a paid engineering engagement with a credible route to follow-on revenue.

Revenue streamWhat RSA suppliesWhat makes it investable
Engineering & qualificationFeasibility, interfaces, mission adaptation, testing and acceptance evidence.A funded statement of work, milestones and controlled scope.
IP licensingA platform licence, per-equipped-spacecraft fee or defined field-of-use licence.Clear rights, deployment reporting, appropriate minimums and protected background IP.
Hardware where requiredQualified optics, computing or integrated navigation modules selected by the study.Funded orders, viable unit margins and bounded warranty obligations.
Ongoing supportSoftware maintenance, upgrades, mission support and agreed reference-data services.Priced service levels, renewals and controlled long-term obligations.
Licence opportunity = funded spacecraft × attach rate × licence fee.
Fleet size is not an order. Price engineering, hardware and support separately where appropriate, and avoid counting bundled revenue twice.

No revenue forecast or product price is assumed. Actual value depends on mission selection, performance, customer funding, negotiated rights and contribution margins.

05 / FIRST STEP

Propose a paid AutoNav feasibility study.

A suggested six-to-eight-week work programme, following NDA, permitted information exchange and a funded scope. Duration and fees should be agreed with the engineering teams.

01 · DEFINE

Select the mission and success criteria.

Confirm the host spacecraft, existing navigation approach and operational need. Agree target accuracy, integrity, update rate, outage performance and the customer value of a backup capability.

02 · TEST

Validate the integration assumptions.

Assess optics, image access, processing and flight-software interfaces. Use representative imagery and hardware-in-the-loop testing where feasible. Quantify power, memory, compute and timing needs.

03 · DECIDE

Produce a costed qualification plan.

Deliver a compatibility assessment, performance evidence, remaining gaps, export pathway and commercial structure. Decide whether to fund qualification or stop with a bounded cost.

The output is a decision-ready integration package: requirements, test results, resource budget, risk register, qualification roadmap, responsibilities and a proposed engineering/licensing/support model.

Suggested allocation: RSA leads the navigation implementation and performance assessment; ReOrbit supplies host specifications, representative interfaces and mission requirements. Funding responsibility and all deliverables remain to be agreed.

06 / CONDITIONS

Resolve the few issues that determine whether the opportunity is real.

Mission performance

Prove the camera and processing configuration, observability, navigation accuracy and integrity. Measure incremental resources; existing hardware and near-zero power use are not assumptions.

Timing and reference data

Define initial time, clock holdover and catalogue/ephemeris requirements. Assess UDL dependencies and any viable sovereign alternative. Validate NTN synchronisation requirements separately.

IP and export permissions

Confirm the rights to license the implementation and improvements. RSA Australia may be a suitable contracting entity, but does not remove ITAR/EAR obligations or automatically authorise Finnish access and onward sales.

A funded commercial route

Identify the budget holder, customer requirement and procurement path. Protect background IP, bound delivery/support obligations and avoid broad exclusivity or a requirement to fund constellation capex.

The Australian constellation proposal is one potential route to future demand. It is not a prerequisite for this technology partnership: a funded GEO mission, another sovereign LEO programme or a hosted demonstration may offer a more immediate entry point.

07 / DISCUSSION

Agree the study.
Prove the fit.
Build the commercial relationship.

The proposed next conversation is between RSA and ReOrbit’s technical and commercial leads, with one objective: determine whether there is a funded host mission worth qualifying.

From RSA

Nominate a technical and commercial owner. Set out the relevant software baseline, interface needs, qualification evidence and licensing boundaries.

From ReOrbit

Identify a candidate mission, navigation requirement, host configuration, engineering sponsor and budget owner.

Joint decision

Agree an NDA, export-cleared information exchange and paid statement of work with measurable deliverables and a clear proceed/stop gate.

The opportunity is to position RSA as a navigation technology partner in sovereign satellite programmes—with an initial paid study and a path to repeatable licensing and support.

Proposal for discussion. No partnership, engineering compatibility, customer award or funding commitment is represented as agreed.

1 / 8