Space
Rendezvous Robotics
Rendezvous Robotics is developing modular spacecraft intended to assemble and reconfigure autonomously in orbit. [1] company claim
Your heat score
Your personal rating, from 0 to 100.
Set your score
Saved only in this browser. Your rating is an opinion, separate from the evidence.
Inputs, production and buyer
Schematic of dependencies through tile integration and mission delivery.
Reading direction. No quantity or physical timing is implied.
Select a participant or connection. Its explanation stays alongside.
Ready to explore.
Electronics, sensors and tile interfaces.
analysis
No named component suppliers.
Rendezvous, current spacecraft tile architecture
Publication date not recorded; Accessed 2026-11-01
Open original sourceComponents and payload
analysis
Electronics, sensors and tile interfaces. [17]
No named component suppliers.
Rendezvous, current spacecraft tile architecture
Publication date not recorded; Accessed 2026-11-01
Open original sourceIntegrate and qualify spacecraft tiles.
analysis
Capacity and qualification results unknown.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceTile production
analysis
Integrate and qualify spacecraft tiles. [1]
Capacity and qualification results unknown.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceOffer modular mission capability.
analysis
Sales terms unknown.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceRendezvous offer
analysis
Offer modular mission capability. [1]
Sales terms unknown.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceDeliver tiles to the mission orbit.
analysis
Rideshare reservation claimed; provider unnamed.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceLaunch service
analysis
Deliver tiles to the mission orbit. [1]
Rideshare reservation claimed; provider unnamed.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceUses assembled capability.
analysis
Illustrative end buyer/user category.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceMission operator
analysis
Uses assembled capability. [1]
Illustrative end buyer/user category.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceTile design requires integrated functional parts.
analysis
No procurement contract implied.
Unnamed component suppliers could provide electronics, sensors and interfaces for tile production.
A complete tile needs these functions to work together.
Production would integrate and test the parts; no supplier contracts are established.
Rendezvous, current spacecraft tile architecture
Publication date not recorded; Accessed 2026-11-01
Open original sourceParts dependency
analysis
Components and payload → Tile production
Tile design requires integrated functional parts. [17]
- What happens
- Unnamed component suppliers could provide electronics, sensors and interfaces for tile production.
- Why it matters
- A complete tile needs these functions to work together.
- What follows
- Production would integrate and test the parts; no supplier contracts are established.
No procurement contract implied.
Rendezvous, current spacecraft tile architecture
Publication date not recorded; Accessed 2026-11-01
Open original sourceQualification is needed before mission acceptance.
analysis
Logical dependency, not completed qualification.
Production would provide integrated hardware for the Rendezvous offer.
Mission customers need qualified hardware with an agreed specification.
The offer could proceed to mission integration; qualification completion is not established.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceQualified hardware
analysis
Tile production → Rendezvous offer
Qualification is needed before mission acceptance. [1]
- What happens
- Production would provide integrated hardware for the Rendezvous offer.
- Why it matters
- Mission customers need qualified hardware with an agreed specification.
- What follows
- The offer could proceed to mission integration; qualification completion is not established.
Logical dependency, not completed qualification.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceTiles require a deployment arrangement.
analysis
Exact interface and contract unknown.
The tile provider would arrange integration with a launch service.
Tiles need a deployment arrangement before orbital assembly is possible.
The launch provider would deliver the payload under a separate agreed mission plan.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceLaunch integration
analysis
Rendezvous offer → Launch service
Tiles require a deployment arrangement. [1]
- What happens
- The tile provider would arrange integration with a launch service.
- Why it matters
- Tiles need a deployment arrangement before orbital assembly is possible.
- What follows
- The launch provider would deliver the payload under a separate agreed mission plan.
Exact interface and contract unknown.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceLaunch enables the proposed assembly mission.
analysis
No successful external mission yet established.
A launch service would place the tiles into the intended mission environment.
Orbital delivery is a prerequisite for the proposed external assembly.
The mission team would attempt assembly and operations; success is not established.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceOrbital delivery
analysis
Launch service → Mission operator
Launch enables the proposed assembly mission. [1]
- What happens
- A launch service would place the tiles into the intended mission environment.
- Why it matters
- Orbital delivery is a prerequisite for the proposed external assembly.
- What follows
- The mission team would attempt assembly and operations; success is not established.
No successful external mission yet established.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceBuyer could purchase hardware or integrated capability.
analysis
Revenue model and payer unconfirmed.
A prospective operator could pay Rendezvous for hardware or integrated capability.
A commercial mission needs a payer and an agreed delivery boundary.
Contract scope and payment terms would define the revenue; neither is established here.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourcePotential payment
analysis
Mission operator → Rendezvous offer
Buyer could purchase hardware or integrated capability. [1]
- What happens
- A prospective operator could pay Rendezvous for hardware or integrated capability.
- Why it matters
- A commercial mission needs a payer and an agreed delivery boundary.
- What follows
- Contract scope and payment terms would define the revenue; neither is established here.
Revenue model and payer unconfirmed.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceComplete participants, relationships and sources
Components and payload
analysis
Electronics, sensors and tile interfaces. [17]
No named component suppliers.
Rendezvous, current spacecraft tile architecture
Publication date not recorded; Accessed 2026-11-01
Open original sourceTile production
analysis
Integrate and qualify spacecraft tiles. [1]
Capacity and qualification results unknown.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceRendezvous offer
analysis
Offer modular mission capability. [1]
Sales terms unknown.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceLaunch service
analysis
Deliver tiles to the mission orbit. [1]
Rideshare reservation claimed; provider unnamed.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceMission operator
analysis
Uses assembled capability. [1]
Illustrative end buyer/user category.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceParts dependency
analysis
Components and payload → Tile production
Tile design requires integrated functional parts. [17]
- What happens
- Unnamed component suppliers could provide electronics, sensors and interfaces for tile production.
- Why it matters
- A complete tile needs these functions to work together.
- What follows
- Production would integrate and test the parts; no supplier contracts are established.
No procurement contract implied.
Rendezvous, current spacecraft tile architecture
Publication date not recorded; Accessed 2026-11-01
Open original sourceQualified hardware
analysis
Tile production → Rendezvous offer
Qualification is needed before mission acceptance. [1]
- What happens
- Production would provide integrated hardware for the Rendezvous offer.
- Why it matters
- Mission customers need qualified hardware with an agreed specification.
- What follows
- The offer could proceed to mission integration; qualification completion is not established.
Logical dependency, not completed qualification.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceLaunch integration
analysis
Rendezvous offer → Launch service
Tiles require a deployment arrangement. [1]
- What happens
- The tile provider would arrange integration with a launch service.
- Why it matters
- Tiles need a deployment arrangement before orbital assembly is possible.
- What follows
- The launch provider would deliver the payload under a separate agreed mission plan.
Exact interface and contract unknown.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceOrbital delivery
analysis
Launch service → Mission operator
Launch enables the proposed assembly mission. [1]
- What happens
- A launch service would place the tiles into the intended mission environment.
- Why it matters
- Orbital delivery is a prerequisite for the proposed external assembly.
- What follows
- The mission team would attempt assembly and operations; success is not established.
No successful external mission yet established.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourcePotential payment
analysis
Mission operator → Rendezvous offer
Buyer could purchase hardware or integrated capability. [1]
- What happens
- A prospective operator could pay Rendezvous for hardware or integrated capability.
- Why it matters
- A commercial mission needs a payer and an agreed delivery boundary.
- What follows
- Contract scope and payment terms would define the revenue; neither is established here.
Revenue model and payer unconfirmed.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceScope. Supplier identities, production subcontractors and final buyers are unverified. Arrows express material, service or payment dependencies, not existing invoices.
Proposed system
A spacecraft built from working tiles
Each proposed tile combines control, sensing and joining hardware so a spacecraft can be assembled and changed after launch.
Use Enlarge drawing for detail. The tour caption explains the selected elements.
Step 1 of 4: 1. Understand one tile. Static diagram.
1. Understand one tile
A processor uses edge sensing to support electromagnetic control. The tile also carries a latch and electrical/data connections; payload details remain ambiguous.
Full step and context
A processor uses edge sensing to support electromagnetic control. The tile also carries a latch and electrical/data connections; payload details remain ambiguous.
Reduced motion is on. Use Previous and Next to explore the steps.
Guided reading, not physical motion.
Explore the diagram
Hover or focus an element to preview its evidence. Click or tap to pin it. Select another element or clear the selection to continue.
Choose an element to inspect its evidence.
A spacecraft built from working tiles
Title identifies the current proposed product.
company claim. The company proposes spacecraft tiles with local processing, edge sensing, electromagnetic motion control, mechanical latching and power/data links.
Drawing. company claim.
Source location. Every Tile Is A Spacecraft [17]
Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
Schematic positions; no scale
Hexagonal body represents a spacecraft tile; geometry is schematic.
company claim. The company proposes spacecraft tiles with local processing, edge sensing, electromagnetic motion control, mechanical latching and power/data links.
Drawing. company claim.
Source location. Every Tile Is A Spacecraft, annotated tile render [17]
Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
Processor
Processor symbol represents local control, not its physical location or chip specification.
company claim. The company proposes spacecraft tiles with local processing, edge sensing, electromagnetic motion control, mechanical latching and power/data links.
Drawing. company claim.
Source location. Tile Processor accordion [17]
Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
Edge sensors
Edge sensor symbol and leader identify position sensing; count is illustrative.
company claim. The company proposes spacecraft tiles with local processing, edge sensing, electromagnetic motion control, mechanical latching and power/data links.
Drawing. company claim.
Source location. Sensor Suite accordion [17]
Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
Electromagnets
Edge blocks and opposing arrows denote controlled attraction/repulsion; no field strength or trajectory.
company claim. The company proposes spacecraft tiles with local processing, edge sensing, electromagnetic motion control, mechanical latching and power/data links.
Drawing. company claim.
Source location. Electromagnetic Actuators accordion [17]
Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
Mechanical latch
Hook symbol denotes a mechanical connection, distinct from magnetic actuation.
company claim. The company proposes spacecraft tiles with local processing, edge sensing, electromagnetic motion control, mechanical latching and power/data links.
Drawing. company claim.
Source location. Mechanical Latch accordion [17]
Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
Payload
Central zone denotes the labelled payload region, not a specified interface.
analysis. The site labels a payload region, but its Payload text describes the power/data mesh and the separate interconnect panel is empty. Detailed interfaces remain unverified.
Drawing. analysis.
Source location. Payload and Power & Data Interconnects accordions [17]
Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
Power + data
Parallel contact symbols denote electrical/data connection; topology and pin count are illustrative.
analysis. The site labels a payload region, but its Payload text describes the power/data mesh and the separate interconnect panel is empty. Detailed interfaces remain unverified.
Drawing. analysis.
Source location. Power & Data Interconnects label; mesh wording under Payload [17]
Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
1 STACK FOR LAUNCH
Repeated flat tile silhouettes represent compact stacking; no launch compatibility or capacity guarantee.
company claim. The stated workflow is stacked launch, orbital assembly, expansion and reconfiguration.
Drawing. company claim.
Source location. How It Works, Launch [17]
Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
2 ALIGN AND LATCH
Neighbouring tile silhouettes, approach arrows and a joint represent controlled assembly.
company claim. The stated workflow is stacked launch, orbital assembly, expansion and reconfiguration.
Drawing. company claim.
Source location. How It Works, Assemble [17]
Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
3 ADD TILES
Dashed additional tile denotes proposed growth, not an observed flight event.
company claim. The stated workflow is stacked launch, orbital assembly, expansion and reconfiguration.
Drawing. company claim.
Source location. How It Works, Scale [17]
Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
4 RECONFIGURE
Two arrangements denote intended reconfiguration; no time or guaranteed manoeuvre path.
company claim. The stated workflow is stacked launch, orbital assembly, expansion and reconfiguration.
Drawing. company claim.
Source location. How It Works, Adapt [17]
Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
Proposed functions, not an operational spacecraft.
Footer separates current proposal from historical research and gives the stated mission boundary.
analysis. The seven-tile external demonstration is planned no earlier than April 2028. The 2019 TESSERAE paper describes a different research predecessor.
Drawing. analysis.
Source location. Seed announcement, new-generation mission paragraph; IEEE paper pages 1-3 [1]
Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
Step timings allow time to read. They do not represent physical speed or duration.
1. Understand one tile
A processor uses edge sensing to support electromagnetic control. The tile also carries a latch and electrical/data connections; payload details remain ambiguous.
2. Launch compactly
The proposed tiles stack for launch. Actual launcher and deployment interfaces require mission qualification.
3. Approach and join
The company describes electromagnetic control for tile motion and a separate mechanical latch for the joined structure.
4. Expand or rearrange
Additional tiles or a changed arrangement could alter capability. These are planned functions, not flight results.
One schematic hexagonal spacecraft tile has a processor, edge sensors, electromagnetic actuators, a mechanical latch, a central payload region and power/data contacts. Below it, stacked tiles lead to a joined structure; added or rearranged tiles represent intended changes after launch. Arrows show functions and logical order, not a simulated physical trajectory. The site has an unresolved payload/interconnect text mismatch. The earlier TESSERAE research is separate from the current free-flying spacecraft proposal.
Limitations.
- Current company proposal accessed 1 November 2026, not a flight-proven blueprint. No dimensions, forces, speed, throughput, payload specification or reliability claim. Internal component locations and counts are illustrative. Videos were inaccessible; static company renders and accordion views were inspected. The seven-tile external mission is planned no earlier than April 2028. Historical TESSERAE testing does not validate this full architecture.
Evidence
- company claim. The company proposes spacecraft tiles with local processing, edge sensing, electromagnetic motion control, mechanical latching and power/data links. [17]
- company claim. The stated workflow is stacked launch, orbital assembly, expansion and reconfiguration. [17]
- analysis. The site labels a payload region, but its Payload text describes the power/data mesh and the separate interconnect panel is empty. Detailed interfaces remain unverified. [17]
- analysis. The seven-tile external demonstration is planned no earlier than April 2028. The 2019 TESSERAE paper describes a different research predecessor. [1] [8]
Diagram elements
- product-heading: company claim. Title identifies the current proposed product. Every Tile Is A Spacecraft [17] Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
- tile-outline: company claim. Hexagonal body represents a spacecraft tile; geometry is schematic. Every Tile Is A Spacecraft, annotated tile render [17] Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
- processor: company claim. Processor symbol represents local control, not its physical location or chip specification. Tile Processor accordion [17] Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
- sensors: company claim. Edge sensor symbol and leader identify position sensing; count is illustrative. Sensor Suite accordion [17] Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
- actuators: company claim. Edge blocks and opposing arrows denote controlled attraction/repulsion; no field strength or trajectory. Electromagnetic Actuators accordion [17] Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
- latch: company claim. Hook symbol denotes a mechanical connection, distinct from magnetic actuation. Mechanical Latch accordion [17] Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
- payload: analysis. Central zone denotes the labelled payload region, not a specified interface. Payload and Power & Data Interconnects accordions [17] Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
- interconnects: analysis. Parallel contact symbols denote electrical/data connection; topology and pin count are illustrative. Power & Data Interconnects label; mesh wording under Payload [17] Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
- launch-stack: company claim. Repeated flat tile silhouettes represent compact stacking; no launch compatibility or capacity guarantee. How It Works, Launch [17] Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
- assemble: company claim. Neighbouring tile silhouettes, approach arrows and a joint represent controlled assembly. How It Works, Assemble [17] Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
- scale: company claim. Dashed additional tile denotes proposed growth, not an observed flight event. How It Works, Scale [17] Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
- adapt: company claim. Two arrangements denote intended reconfiguration; no time or guaranteed manoeuvre path. How It Works, Adapt [17] Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
- product-boundary: analysis. Footer separates current proposal from historical research and gives the stated mission boundary. Seed announcement, new-generation mission paragraph; IEEE paper pages 1-3 [1] Limitation. Original explanatory drawing. Component placements, symbol counts and relative sizes are not engineering specifications; no demonstrated flight performance.
Interactive 3D explainer
How spacecraft tiles could assemble
Inspect the company-render exterior, then follow the proposed sensing, motion, joining and connection roles in separate functional views.
Controls
Jump to a step
Hover the model or choose a part
No part selected
Rendezvous Robotics
Inspect the company-render exterior, then follow the proposed sensing, motion, joining and connection roles in separate functional views.
The exterior follows a company concept render. Internal designs, forces, trajectories and successful orbital assembly are not established here.
Source for this explanation ↗The static explanation below is available without 3D or JavaScript.
Evidence boundary. The exterior follows a company concept render. Internal designs, forces, trajectories and successful orbital assembly are not established here.
Static explanation and all component roles
- Tile exterior: a stationary explanatory view, not measured motion.
- Launch packing: a stationary explanatory view, not measured motion.
- Sensing and control: a stationary explanatory view, not measured motion.
- Edge alignment: a stationary explanatory view, not measured motion.
- Joined pair: a stationary explanatory view, not measured motion.
- Mission concept: a stationary explanatory view, not measured motion.
- Tile body
- The shallow hexagonal body has a bevelled rim, dark edge apertures and a thirteen-cell face motif in the company render.
Purpose. Flat tiles can be packed separately from the shape of a proposed orbital structure.
Normalised exterior proportions, not dimensional CAD. The aperture and face-pattern functions are not identified.company claim | inspected 2026-11-01 | Source 1 | Source 2 | Source 3
- Edge sensors
- A symbolic position cue links two edge regions. The company assigns neighbouring-tile position knowledge to edge sensors.
Purpose. A controller needs information about its neighbour before guiding an approach.
The sensor type, precise location, range and accuracy are undisclosed. The marker is a functional role.company claim | inspected 2026-11-01 | Source 1
- Tile processor
- The separate control marker receives a position cue and sends a command. It represents the stated embedded CPU function.
Purpose. Useful assembly control connects sensing to the next action.
This labelled block is not a processor package, circuit board or verified control algorithm.company claim | inspected 2026-11-01 | Source 1
- Electromagnetic actuation
- Two exterior tiles move towards aligned edges. The company assigns attraction, repulsion and motion control to electromagnetic actuators.
Purpose. The edges need alignment before the structure can be joined.
Schematic approach only. No coil design, force, flight trajectory, speed or tolerance is simulated. - Mechanical joining
- A boundary marker changes from open to joined after the edges align. It identifies the mechanical latch function.
Purpose. Holding a structure together is distinct from positioning its parts.
The seam is a functional indicator, not a disclosed latch shape, strength or locking sequence.company claim | inspected 2026-11-01 | Source 1
- Power and data links
- A solid power path and a dashed data path cross the joined boundary. These are proposed electrical and information connections.
Purpose. A useful spacecraft assembly needs shared connections as well as structural contact.
The company places mesh wording under Payload and leaves the interconnect description empty. Pinout, protocol and capacity remain unspecified.company claim | inspected 2026-11-01 | Source 1
- Mission role
- An illustrative array shows why tiles would be joined: to support a chosen spacecraft mission rather than remain separate panels.
Purpose. Assembly is a means of providing useful spacecraft functions.
The face motif is not labelled as solar cells or processors. Array count and mission performance are illustrative.company claim | inspected 2026-11-01 | Source 1 | Source 2 | Source 3
company claim; analysis geometry · Rendezvous Robotics source. Source inspection dates are listed for each component. Publication date is recorded in the dossier source list where established. Every shape is an explanatory simplification; the scene does not establish engineering performance.
Capital, customers and market direction
Money and market
Evidence checked to . Company finances and wider-market indicators are kept separate.
First priced round
USD 20mThe company announced a seed round for spacecraft development, flight demonstrations and hiring. [F1]
Earlier SAFEs may convert or overlap. The round is not current cash, valuation or a funded mission budget.
company claimCapital milestone
2028 flightThe planned free-space demonstration is scheduled no earlier than April 2028. [F1]
Schedule and success remain uncertain; development, launch, operations and contingency need separate budgets.
company claimAdjacent market signal
USD 542.1mRedwire reported Q2 2026 backlog, alongside USD 117.1m revenue and 27.8% gross margin. [F2]
Diversified space and defence results, including acquired operations. Not a modular-assembly market estimate.
verifiedCash and runway
Not disclosedNot established. Current cash, committed facilities, monthly cash burn and a funded milestone plan have not been obtained.
A financing announcement is not the cash balance. No runway estimate is shown.
analysisWhat the market signal means
Demand for infrastructure is not yet tile revenue
Adjacent space suppliers have revenue and contracted work. Rendezvous must turn a technical capability into a priced, accepted mission service or product with a clear buyer, delivery boundary and liability allocation. [F1] [F2]
A market narrative or collaboration announcement cannot substitute for contracted revenue.
analysisQuestions that change the financial case
- What is the cash budget and contingency through the orbital demonstration and customer acceptance?
- Who pays for launch, insurance, integration, mission operations and replacement?
- What customer commitment survives a delay or a demonstration that meets only part of its objectives?
Financial overview sources and dates
- F1 Rendezvous priced seed and flight programme
Published 2026-10-28 · Accessed 2026-11-01
- F2 Redwire Q2 2026 results
Published 2026-08-05 · Accessed 2026-11-01
The development
On 28 October 2026, Rendezvous Robotics announced a $20 million seed financing. [1] verified
Claims and evidence
Rendezvous Robotics is developing modular spacecraft intended to assemble and reconfigure autonomously in orbit. [1]
company claimOn 28 October 2026, Rendezvous Robotics announced a $20 million seed financing. [1]
verifiedThe April 2026 Form D identifies Rendezvous Robotics, Inc. as a Delaware corporation formed in 2024, with its principal business in Golden, Colorado. [5] [6]
verifiedThe company describes itself as privately held. Aurelia describes its spinouts as independent, for-profit entities; the cap table and control rights remain unverified. [12] [11]
company claimThe company plans a seven-tile free-space assembly and reconfiguration mission, with a rideshare reservation no earlier than April 2028. [1]
company claimThe December 2025 roadmap targeted an external mission in late 2026. The later 2028 plan needs scope reconciliation before treating the difference as a precise delay to the same mission. [2] [1]
analysisThe primary 2019 IEEE paper describes magnetic tiles with sensing and corrective separation, combining preliminary prototype work with proposed mission architecture. [8]
verifiedThe 2022 MIT interview reports small-tile tests inside the ISS, including cabin aisleway trials. Astronauts helped assemble the dome made from the small test tiles; this was not a self-built operating satellite. [7]
company claimThe Starcloud collaboration was announced in October 2025 as an MoU to explore integration and commercial models, not a disclosed purchase order. [13]
company claimThe April 2026 Form D reports $5,197,500 sold in a SAFE offering. Its relationship to the later priced round is unresolved; the amounts must not be added as cash available. [5]
verifiedToyota's account specifies 36 tiles for the final ISS test, while the company and trade accounts specify 32. This conflict is separate from the seven-tile external mission. [10] [2] [4]
analysisThe opened patent reproduction identifies MIT as assignee of US12617553B2. Rendezvous's licence scope and exclusivity are not established by that record. [14]
verifiedThe current company design combines a tile processor, edge sensors, electromagnetic motion control, mechanical latching and power/data interconnections. These are proposed product functions, not a completed external flight demonstration. [17]
company claim
Assessment
| Topic | Reading and evidence |
|---|---|
| Product and mechanism | The proposed spacecraft tiles launch stacked, use edge sensing and an onboard processor to support electromagnetic assembly, latch mechanically, then connect power and data. The current site labels a payload region but misplaces the mesh description under Payload, leaving interface details ambiguous. The 2019 research system is a predecessor, not this product specification. [17] [1] [8] analysis |
| Customers and buying process | Commercial and government communications and sensing are stated target markets. Named budget owners, funded requirements and procurement criteria remain unknown. [4] analysis |
| Commercial proof | Starcloud is a concrete collaboration lead at MoU stage. Paid orders, customer acceptance and repeat purchases are not established. [13] analysis |
| Pricing or economics | Not established. System prices, integration costs, launch mass, insurance and lifetime-cost comparisons are needed to test economic benefit. unknown |
| Competitors and substitutes | NASA's deployed roll-out array illustrates an operating alternative for power structures. Conventional integration and robotic assembly remain competing approaches; no matched comparison proves Rendezvous cheaper or more reliable. [15] [16] analysis |
| Distribution | The stated architecture relies on partners for payloads and other spacecraft elements. Prime-contractor agreements, integration responsibilities and a repeatable sales route remain unknown. [4] [13] analysis |
| Intellectual property or defensibility | A relevant patent is identifiable, with MIT listed as assignee. Current rights, the licence chain, field of use, royalties and exclusivity require documents and official-register checks. [14] analysis |
| Manufacturing or operational scaling | The company describes in-house core assembly hardware and partner-supplied components. Production yield, test throughput, supplier qualification and repeatability across units are unresolved. [4] analysis |
| Regulation | Not established. Mission-specific approvals, spectrum arrangements, launch integration and debris/disposal documentation were not retrieved. unknown |
| Capital needs | The seed is intended to fund development and demonstrations. Cash received, burn, launch costs, contingency and SAFE conversion terms remain unknown; the funding records do not establish runway. [1] [5] analysis |
| Key risks | Small-tile cabin tests do not establish safe external deployment, durable interfaces or mission reliability. The external schedule and ISS tile-count discrepancies require reconciliation. [7] [2] [1] [10] analysis |
| Next falsifiable milestone | Seek independently witnessed, repeated joining, power/data operation, separation and rejoining of representative tiles under agreed mission conditions, with failures recorded and a credible external flight plan. [8] [4] analysis |
| Team | The filing identifies officers and directors; the paper establishes the research lineage. Integrated flight-system responsibilities, staffing and delivery evidence need separate assessment. [5] [8] analysis |
| Business model | A model based on spacecraft hardware and integration is plausible. The split between hardware, services and licensing, and the allocation of mission liability, are not established. [4] [13] analysis |
Opinion
The useful investment question is whether small assembly experiments can become a reliable spacecraft and a funded customer mission. Financing and the changed public timetable make execution worth examining; they do not prove performance.
Limits. Reconcile mission scope before calling the schedule change a precise delay. Reverse the positive execution reading if representative repeated tests fail the agreed mission envelope, or capital and launch commitments cannot support a credible plan. Private control, paid demand and integrated reliability remain incompletely established.
opinionCommercial picture · 2026-11-01
Competition, costs and demand
Product and commercial evidence as of 1 November 2026. Claims remain bounded by the cited sources.
Commercial route
Schematic of a proposed route from platform development to mission purchase.
Reading direction. No quantity or physical timing is implied.
Select a participant or connection. Its explanation stays alongside.
Ready to explore.
Develops modular spacecraft.
company claim
Development stage.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceRendezvous Robotics
company claim
Develops modular spacecraft. [1]
Development stage.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceNamed exploration partner.
company claim
No order disclosed.
Rendezvous and Starcloud MoU
Published 2025-10-30; Accessed 2026-11-01
Open original sourceStarcloud
company claim
Named exploration partner. [13]
No order disclosed.
Rendezvous and Starcloud MoU
Published 2025-10-30; Accessed 2026-11-01
Open original sourceCombines platform and mission requirements.
analysis
Illustrative role, not a confirmed contractor.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceMission integrator
analysis
Combines platform and mission requirements. [1]
Illustrative role, not a confirmed contractor.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceFunds a desired orbital capability.
analysis
No confirmed payer.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceMission buyer
analysis
Funds a desired orbital capability. [1]
No confirmed payer.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceExplore power and thermal integration.
company claim
MoU, not delivery.
Rendezvous and Starcloud explore power and thermal integration.
The partners need to assess whether modular infrastructure fits a potential orbital computing system.
Any delivery would require a separately agreed and funded mission.
Rendezvous and Starcloud MoU
Published 2025-10-30; Accessed 2026-11-01
Open original sourceIntegration study
company claim
Rendezvous Robotics → Starcloud
Explore power and thermal integration. [13]
- What happens
- Rendezvous and Starcloud explore power and thermal integration.
- Why it matters
- The partners need to assess whether modular infrastructure fits a potential orbital computing system.
- What follows
- Any delivery would require a separately agreed and funded mission.
MoU, not delivery.
Rendezvous and Starcloud MoU
Published 2025-10-30; Accessed 2026-11-01
Open original sourcePossible platform supply to a mission.
analysis
Illustrative commercial structure.
Rendezvous could supply tile hardware and engineering to a mission integrator.
The proposed platform must fit a mission before it can become a delivered capability.
The integrator would combine it with other mission requirements.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceHardware and engineering
analysis
Rendezvous Robotics → Mission integrator
Possible platform supply to a mission. [1]
- What happens
- Rendezvous could supply tile hardware and engineering to a mission integrator.
- Why it matters
- The proposed platform must fit a mission before it can become a delivered capability.
- What follows
- The integrator would combine it with other mission requirements.
Illustrative commercial structure.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceMission procurement would fund accepted capability.
analysis
No contract amount or payment routing established.
A prospective buyer could specify requirements and fund an integration contract.
A project needs an agreed acceptance boundary and payer.
The integrator would deliver against negotiated requirements; payment timing is unknown.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceRequirements and payment
analysis
Mission buyer → Mission integrator
Mission procurement would fund accepted capability. [1]
- What happens
- A prospective buyer could specify requirements and fund an integration contract.
- Why it matters
- A project needs an agreed acceptance boundary and payer.
- What follows
- The integrator would deliver against negotiated requirements; payment timing is unknown.
No contract amount or payment routing established.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceDelivered system would serve the mission buyer.
analysis
Target outcome, not operating service.
An integrator could deliver accepted mission capability to a buyer.
The buyer needs a working mission outcome, not only component development.
Operational use would follow acceptance; no such delivered service is established here.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceMission capability
analysis
Mission integrator → Mission buyer
Delivered system would serve the mission buyer. [1]
- What happens
- An integrator could deliver accepted mission capability to a buyer.
- Why it matters
- The buyer needs a working mission outcome, not only component development.
- What follows
- Operational use would follow acceptance; no such delivered service is established here.
Target outcome, not operating service.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceComplete participants, relationships and sources
Rendezvous Robotics
company claim
Develops modular spacecraft. [1]
Development stage.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceStarcloud
company claim
Named exploration partner. [13]
No order disclosed.
Rendezvous and Starcloud MoU
Published 2025-10-30; Accessed 2026-11-01
Open original sourceMission integrator
analysis
Combines platform and mission requirements. [1]
Illustrative role, not a confirmed contractor.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceMission buyer
analysis
Funds a desired orbital capability. [1]
No confirmed payer.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceIntegration study
company claim
Rendezvous Robotics → Starcloud
Explore power and thermal integration. [13]
- What happens
- Rendezvous and Starcloud explore power and thermal integration.
- Why it matters
- The partners need to assess whether modular infrastructure fits a potential orbital computing system.
- What follows
- Any delivery would require a separately agreed and funded mission.
MoU, not delivery.
Rendezvous and Starcloud MoU
Published 2025-10-30; Accessed 2026-11-01
Open original sourceHardware and engineering
analysis
Rendezvous Robotics → Mission integrator
Possible platform supply to a mission. [1]
- What happens
- Rendezvous could supply tile hardware and engineering to a mission integrator.
- Why it matters
- The proposed platform must fit a mission before it can become a delivered capability.
- What follows
- The integrator would combine it with other mission requirements.
Illustrative commercial structure.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceRequirements and payment
analysis
Mission buyer → Mission integrator
Mission procurement would fund accepted capability. [1]
- What happens
- A prospective buyer could specify requirements and fund an integration contract.
- Why it matters
- A project needs an agreed acceptance boundary and payer.
- What follows
- The integrator would deliver against negotiated requirements; payment timing is unknown.
No contract amount or payment routing established.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceMission capability
analysis
Mission integrator → Mission buyer
Delivered system would serve the mission buyer. [1]
- What happens
- An integrator could deliver accepted mission capability to a buyer.
- Why it matters
- The buyer needs a working mission outcome, not only component development.
- What follows
- Operational use would follow acceptance; no such delivered service is established here.
Target outcome, not operating service.
Rendezvous, seed round and mission roadmap
Published 2026-10-28; Accessed 2026-11-01
Open original sourceScope. Only the Starcloud exploration relationship is directly announced. Other roles describe a possible commercial route, not verified trading relationships.
Competition and substitutes
Evidence and limitations for competition and substitutes.
| Topic | Evidence and scope |
|---|---|
| Redwire ROSA | Redwire offers deployable solar arrays; NASA reports ROSA operation on the ISS. Roll-out deployment is a concrete alternative for power structures. [18] [19] analysis A deployed array is not a reconfigurable multi-purpose tiled spacecraft. |
| MDA SKYMAKER | MDA markets robotics for satellite servicing and in-space assembly. A robotic manipulator is an alternative assembly approach. [23] analysis No matched mission cost or performance comparison with Rendezvous. |
| Conventional spacecraft | A mission can retain ground integration and launch-compatible dimensions rather than require in-orbit tile assembly. [1] analysis Analytical baseline; mission capability may differ. |
| Historical funded substitute | NASA awarded Maxar USD 142 million for the SPIDER assembly/manufacturing demonstration in 2020. NASA discontinued its OSAM-1 host project in 2024. [24] [25] verified Historical contract funding, not competitor equity, current sales or a successful flight. |
| Related research: TESSERAE | NASA lists Aurelia Institute's TESSERAE as a self-assembling tile prototype in development, with a 2022 ISS test. It is related research, not evidence of a commercially equivalent Rendezvous product. [27] analysis SMA47, printed p256. The entry still describes a planned January 2026 demonstration; later completion must be checked in original mission records. |
Funding
Evidence and limitations for funding.
| Topic | Evidence and scope |
|---|---|
| Priced seed | The October 2026 announcement reports USD 20 million led by MaC Venture Capital and Toyota Ventures. [1] company claim Company announcement; cash receipt, valuation and burn undisclosed. |
| Earlier SAFE | The April 2026 Form D reports USD 5,197,500 sold in the offering. [5] verified Not current cash. SAFE conversion or overlap with the later round remains unresolved. |
| Capital needs | Not established. A costed mission plan, cash receipts, debt, grants, contingency and working capital are required; no runway is calculated. Not established Further primary evidence required. |
Costs and economics
Evidence and limitations for costs and economics.
| Topic | Evidence and scope |
|---|---|
| Launch-service benchmark | Spaceflight publishes USD 895,000 for a 50 kg payload to low Earth orbit. [26] verified Undated provider tariff observed on 1 November 2026, nominal USD, not a current binding quotation. Scope is one rideshare payload; orbit details, integration, tax and insurance inclusions require confirmation. Rendezvous tile mass and launch terms are unknown. |
| Customer CAPEX boundary | The SPIDER award concerns a robotic arm, antenna assembly and beam manufacture demonstration. Its USD 142 million is a programme-specific development contract. [24] verified Historical US nominal 2020 award, not a per-tile price, operating cost or transferable Rendezvous budget. |
| Company CAPEX and OPEX | Not established. Factory equipment, tile materials, test cost, yield, labour, operations, insurance and replacement costs were not established. Not established Further primary evidence required. |
| Unit economics | Not established. No demonstrated price per delivered capability, recurring revenue, production rate or like-for-like lifecycle-cost comparison was retrieved. Not established Further primary evidence required. |
Supply and delivery chain
Evidence and limitations for supply and delivery chain.
| Topic | Evidence and scope |
|---|---|
| Functional inputs | The current tile design identifies a processor, edge sensors, electromagnetic actuation, mechanical latching and power/data connections. [17] company claim Named vendors, radiation grades and manufacturing partners are unknown. |
| Production and qualification | The seed release describes development of larger independent tiles and ground demonstrations. [1] company claim No production yield, flight qualification report or repeatable delivery capacity disclosed. |
| Launch dependency | The company reports a reserved rideshare no earlier than April 2028. [1] company claim Provider, contract terms and manifested deployment interface are not established. |
| Integration lead | Starcloud and Rendezvous agreed to explore integrated orbital power and thermal systems. [13] company claim MoU and technical exploration, not supplier qualification or paid order. |
Adoption drivers
Evidence and limitations for adoption drivers.
| Topic | Evidence and scope |
|---|---|
| Larger useful structures | The product targets structures that can be expanded after launch, including communications and power applications. [1] company claim Proposed capability. No demonstrated customer saving follows. |
| Change after deployment | Adding or rearranging tiles could change mission capability without replacing a whole structure. [17] analysis Analytical benefit contingent on safe reconnection and full spacecraft operation. |
| Demand for power | Operational ROSA use shows that large power structures have real missions. [19] analysis Demand for arrays does not prove demand for this assembly method. |
| Assembly beyond launch constraints | NASA identifies launch-fairing limits and the ability to update spacecraft in orbit as reasons to develop in-space assembly and servicing. [27] verified Introduction, printed p16. Industry rationale does not establish customer orders or cost savings for Rendezvous. |
Execution blockers
Evidence and limitations for execution blockers.
| Topic | Evidence and scope |
|---|---|
| Flight evidence boundary | The announced seven-tile free-space assembly mission is planned for 2028; it is distinct from the smaller TESSERAE research demonstrations. [1] company claim No demonstrated free-flying commercial system implied. |
| Interface and control risk | Reliable approach, capture, mechanical load transfer and electrical continuity must work together. [17] analysis Failure rates, control authority, structural loads and thermal/radiation margins are unavailable. |
| Programme counterexample | NASA ended OSAM-1 citing technical, cost and schedule issues and lack of a committed partner. [25] analysis Different architecture; useful warning about funded demand and delivery, not a forecast for Rendezvous. |
| Mission permissions | Not established. Mission-specific spectrum, launch safety, debris disposal, collision-avoidance and liability documents were not retrieved. Not established Further primary evidence required. |
| Demonstration is not operational adoption | NASA separates planned demonstrations, flight demonstrations and operational capability. The same distinction is needed when evaluating a tile platform. [27] analysis Figure 2, printed p20. Figure 3 counts collected activities, not market demand or competitors; the survey is not exhaustive. |
Demand evidence
Evidence and limitations for demand evidence.
| Topic | Evidence and scope |
|---|---|
| Starcloud collaboration | The disclosed MoU covers technical pathways and commercial models, with possible future demonstrations. [13] company claim No disclosed minimum purchase, funded backlog or acceptance milestone. |
| Target sectors | The site targets defence, direct-to-device communications and orbital computing. [17] company claim Seller-selected applications, not quantified buyer appetite. |
| Conversion and acceptance | Not established. Paid missions, repeat orders, procurement conversion and original customer or public surveys are unavailable. Not established Further primary evidence required. |
Buyers and payers
Evidence and limitations for buyers and payers.
| Topic | Evidence and scope |
|---|---|
| Prospective mission buyers | Satellite operators, spacecraft integrators and government mission programmes are plausible buyers of assembled capability. [1] [23] analysis Buyer categories are analytical; no named paid customer is established. |
| Partner role | Starcloud is a named exploration partner for power and thermal infrastructure. [13] company claim The MoU does not identify a final payer or a procurement budget. |
| Commercial route | Not established. Hardware, integration, licensing and service revenue shares, prime-contractor responsibilities and acquisition interest remain unestablished. Not established Further primary evidence required. |
Public-company context · 2026-11-01
Listed companies around this market
Listed space-infrastructure comparator selected for deployable structures. No private-company valuation or confirmed trading relationship.
A listed company's share price reflects its whole business. It does not establish demand for this startup, a supplier relationship or a private valuation.
Redwire Corporation
Comparator · analysis
Redwire offers solar arrays and deployable structures that can substitute for parts of the proposed mission. Its current investor page confirms NYSE:RDW. [18] [22]
No supplier or customer relationship with Rendezvous is established. Figures are consolidated US GAAP and include defence activity and acquisitions; no pure-play comparison.
View Redwire Corporation on TradingView. External price data may be delayed or unavailable; filing evidence is shown below.
Consolidated revenue
Consolidated US GAAP revenue, annual USD thousand; includes acquisitions from their closing dates. Units: USD thousand.
| Period | Reported value | Filing and evidence |
|---|---|---|
| 2024-01-01 to 2024-12-31 | 304,101 USD thousand | 2026-02-27 · verified 2025 Form 10-K, Consolidated Statements of Operations and Comprehensive Income (Loss), page 64, Revenues row [20] |
| 2025-01-01 to 2025-12-31 | 335,381 USD thousand | 2026-02-27 · verified 2025 Form 10-K, Consolidated Statements of Operations and Comprehensive Income (Loss), page 64, Revenues row [20] |
Diversified group including acquired operations; not a pure in-space assembly business or Rendezvous benchmark.
PP&E purchases
Consolidated purchases of property, plant and equipment, positive cash-spending magnitude, annual USD thousand; acquisitions excluded. Units: USD thousand.
| Period | Reported value | Filing and evidence |
|---|---|---|
| 2024-01-01 to 2024-12-31 | 6,399 USD thousand | 2026-02-27 · verified 2025 Form 10-K, Consolidated Statements of Cash Flows, page 66, Purchases of property, plant and equipment row [20] |
| 2025-01-01 to 2025-12-31 | 13,479 USD thousand | 2026-02-27 · verified 2025 Form 10-K, Consolidated Statements of Cash Flows, page 66, Purchases of property, plant and equipment row [20] |
Diversified group including acquired operations; not a pure in-space assembly business or Rendezvous benchmark.
Calculated comparisons
2025 PP&E purchases / revenue: 4.02% analysis · calculated, rounded to 2 decimal places
100 × 13,479 ÷ 335,381. PP&E purchases / Consolidated revenue, period ending 2025-12-31. [20]
Ratio of rounded group filing values. Acquisition-driven changes limit comparability; not an estimate of Rendezvous capital needs.
Competitive landscape · 2026-11-01
Who else solves this?
Orbital infrastructure: robotic assembly, deployable structures and complete spacecraft alternatives.
Comparison lens. Rendezvous Robotics proposes distributed modular assembly. The realistic alternatives include using a robotic arm, deploying a structure built on Earth, or buying a complete spacecraft. These solve overlapping mission needs but are not equivalent self-assembling tile products. analysis
Established supplier · United States
Redwire deployable structures
Solar arrays and deployable structures that compact for launch and expand in space.
- Difference
- An alternative when the customer needs deployed area or power rather than reconfigurable robotic tiles. It could also supply components to an assembly system.
- Maturity
- Markets established deployable product families, including ROSA.
- Economics
- Mission-specific array and integration pricing is not public in the inspected portfolio.
- Funding / ownership
- Redwire corporate product line; dedicated funding and product-level revenue are not stated here.
A deployable solar array does not provide general-purpose distributed assembly or tile autonomy.
analysis
Sources and dates
Redwire solar arrays and deployable structures (published date not stated; accessed 2026-11-01)
Alternative approach · Canada
MDA SKYMAKER
Commercial robotic systems and modular components for orbital operations and assembly.
- Difference
- A manipulator-based route to construction; it may compete for an assembly contract or complement a modular structure.
- Maturity
- Announced in 2024 using MDA robotics heritage; the announcement does not prove flight qualification of every new configuration.
- Economics
- Contract pricing and equivalent assembly cost are undisclosed.
- Funding / ownership
- MDA Space identified itself as TSX-listed in the announcement; programme investment is not separately stated.
Canadarm heritage cannot be assigned wholesale to every SKYMAKER configuration.
analysis
Sources and dates
MDA SKYMAKER announcement (published 2024-04-08; accessed 2026-11-01)
Alternative approach · United States; Japan subsidiary
GITAI
Robotic arms and orbital servicing technology for assembly and spacecraft operations.
- Difference
- Arm-based manipulation is a different architecture from distributed self-assembling tiles and may be complementary.
- Maturity
- Reports completed ISS arm tasks in March 2024; current portfolio also lists a 2025 satellite-bus demonstration.
- Economics
- No matched orbital assembly service price is disclosed; demonstration success does not establish economic superiority.
- Funding / ownership
- Current funding total and service-programme allocation were not established from these sources.
Company-reported technology readiness and demonstrations are not proof of routine commercial assembly at scale.
analysis
Sources and dates
GITAI ISS demonstration completion (published 2024-03-19; accessed 2026-11-01) · GITAI current on-orbit services and heritage (published date not stated; accessed 2026-11-01)
Alternative approach · United States
ThinkOrbital ThinkToolkit
A robotic end effector combining welding, cutting and inspection, with additive manufacturing described as future capability.
- Difference
- Joins and inspects structural material rather than assembling standard robotic tiles; could compete for construction work or provide a complementary tool.
- Maturity
- Current page describes the toolkit; it does not establish routine commercial operation of every capability.
- Economics
- No contract price or matched assembly cost is disclosed.
- Funding / ownership
- Product-specific funding and current ownership were not established in the inspected source.
Separate demonstrated functions from future additive manufacturing and from full-platform deployment.
analysis
Sources and dates
ThinkOrbital ThinkToolkit (published date not stated; accessed 2026-11-01)
Alternative approach · United States and New Zealand
Rocket Lab spacecraft
Complete spacecraft platforms integrating core mission subsystems.
- Difference
- Buying a spacecraft built on Earth avoids orbital assembly for missions that fit existing launch and bus constraints.
- Maturity
- Rocket Lab documented delivery of a Photon spacecraft to Varda in May 2023 and markets a broader spacecraft family.
- Economics
- Prices depend on mission and configuration; no matched total-cost comparison is available.
- Funding / ownership
- The delivery announcement identifies Rocket Lab as Nasdaq-listed; platform-specific funding is not stated.
A delivered spacecraft is not evidence for modular in-space reconfiguration, and shipment alone does not prove orbital success.
analysis
Sources and dates
Rocket Lab spacecraft portfolio (published date not stated; accessed 2026-11-01) · Rocket Lab Varda spacecraft delivery (published 2023-05-09; accessed 2026-11-01)
Coverage limits. Five named alternatives are included, with adjacent and potentially complementary systems explicitly distinguished. This search did not establish a like-for-like operational tile supplier, nor does it prove none exists. No matched mission cost or market-share ranking is supportable.
Sources
- 1Rendezvous seed financing original
company | Published 2026-10-28 | Accessed 2026-11-01
- 2Earlier Gen-5 and external mission roadmap
company | Published 2025-12-15 | Accessed 2026-11-01
- 3Payload original financing interview
independent | Published 2026-10-28 | Accessed 2026-11-01
- 4Via Satellite original interview
independent | Published 2026-10-28 | Accessed 2026-11-01
- 5SEC Form D issuer filing
filing | Published 2026-04-02 | Accessed 2026-11-01
- 6SEC filing index and date
filing | Published 2026-04-02 | Accessed 2026-11-01
- 7MIT researcher account of ISS experiments
affiliated-research-interview | Published 2022-05-11 | Accessed 2026-11-01
- 82019 IEEE TESSERAE paper, author-hosted manuscript
paper | Published undated | Accessed 2026-11-01
- 9Aurelia TESSERAE programme and historical ISS plan
research-originator | Published undated | Accessed 2026-11-01
- 10Toyota Ventures investment account
investor | Published 2026-10-28 | Accessed 2026-11-01
- 11Aurelia spinout model
incubator | Published undated | Accessed 2026-11-01
- 12Company profile: privately held
company | Published undated | Accessed 2026-11-01
- 13Rendezvous and Starcloud MoU announcement
company | Published 2025-10-30 | Accessed 2026-11-01
- 14US12617553B2 patent reproduction
patent-reproduction | Published 2026-05-05 | Accessed 2026-11-01
- 15NASA report of deployed roll-out solar array
operator | Published 2021-06-20 | Accessed 2026-11-01
- 16NASA 2025 ISAM survey, including TESSERAE
agency-context | Published 2025-10-01 | Accessed 2026-11-01
- 17Rendezvous, current spacecraft tile architecture
company product description | Published undated | Accessed 2026-11-01
- 18Redwire, solar arrays and deployable structures
manufacturer product description | Published undated | Accessed 2026-11-01
- 19NASA, roll-out solar array impact story
agency technology account | Published undated | Accessed 2026-11-01
- 20Redwire, 2025 Form 10-K
official SEC annual filing | Published 2026-02-27 | Accessed 2026-11-01
- 21SEC, Redwire annual filing acceptance
official SEC filing metadata | Published 2026-02-27 | Accessed 2026-11-01
- 22Redwire investor relations, current listing
issuer listing information | Published undated | Accessed 2026-11-01
- 23MDA, SKYMAKER product announcement
manufacturer product announcement | Published 2024-04-08 | Accessed 2026-11-01
- 24NASA, SPIDER award
agency contract announcement | Published 2020-01-31 | Accessed 2026-11-01
- 25NASA, OSAM-1 discontinuation
agency programme announcement | Published 2024-03-01 | Accessed 2026-11-01
- 26Spaceflight, published rideshare tariff
provider price list | Published undated | Accessed 2026-11-01
- 27NASA ISAM State of Play, 2026 edition
government_report | Published undated | Accessed 2026-11-01