Orbit Fab

Profile boundary

Orbit Fab is a commercial company developing in-space propellant logistics, including the RAFTI cooperative docking and refueling interface, GRIP transfer hardware, mission-planning tools, fuel shuttles, and depot concepts.

Evidence boundary: Official materials support RAFTI specifications, qualification claims, prior demonstrations, contracts, and planned architectures; they do not independently verify routine service availability or GShips compatibility.

Potentially relevant capability areas

• Refueling interface hardware, cooperative docking and fluid transfer, mission planning, depot and shuttle architectures, interface documentation, and planned in-orbit fuel-delivery services.

Task-specific matches

A match is bounded to one declared work program. It does not establish a partnership, availability, endorsement, or an organization-wide rank.

• No task-specific match is recorded.

Potential fit—not a relationship

RAFTI documentation and refueling demonstrations could inform serviceable fluid interfaces, docking, leak control, repeated transfer, logistics architecture, and nonproprietary interface policy for precursor spacecraft. This is not evidence of generation-ship resupply.

Possible bounded engagement, not undertaken: Proposed, not undertaken: review the public interface guide and define a civil compatibility and maintainability study; any hardware purchase, channel relationship, or refueling service inquiry requires procurement, export, safety, and separate authorization.

Fit and engagement risks

• Flight qualification and company-reported milestones do not establish routine end-to-end orbital refueling service.
• Service schedules, price, propellant compatibility, customer interfaces, insurance, and availability remain programme-specific.
• Government and defense customers create dual-use and export-control boundaries.
• A single vendor interface can still create lifecycle and supply dependence despite an open license.

What would change this profile?

Completed repeated in-orbit transfers, independent reliability data, open interoperable implementation evidence, and an authorized technical response would change readiness.