Insurance for Startups & New Economy

Transporter-18 Put Four Indian Payloads in Orbit: Rideshare Launch, In-Orbit and Data-Service Liability for India's Orbital-Compute Startups

Four Indian payloads reached orbit on SpaceX's Transporter-18, including TakeMe2Space's MOI-1A, which runs AI inference in orbit and has 23 signed customers. This post covers re-flight economics after a launch loss, rideshare contract gaps, in-orbit cover for small satellites and tech E&O for processing data in space.

Sarvada Editorial TeamInsurance Intelligence
10 min read

Listen to this article

Audio version • 10 min read

space techsatellite insurancein-orbit covertech e&oin-space authorisation

Last reviewed: October 2026

What reached orbit on Transporter-18

SpaceX's Transporter-18 rideshare lifted off from Vandenberg at 12:02 am IST on 2 October 2026 carrying about 130 payloads. Four of them were Indian: TakeMe2Space's MOI-1A and payloads from Dhruva Space, SatLeo Labs and EON Space Labs. All four reached orbit under IN-SPACe authorisation, according to GKToday (2 October 2026) and the launch coverage from Space.com and Satellite Today (1 October 2026).

For the insurance market, one of the four is a different kind of risk. MOI-1A is not only a satellite that has to survive launch and work in orbit. It is a computing service. It carries Nvidia Orin NX edge processors rated at 117 TOPS with 2 TB of on-board storage, and the company has 23 signed customers in sectors including agriculture, mining, supply chain and insurance (Reuters, as carried by WSAU and The Star, 27-28 September 2026).

A customer who pays for inference in orbit is buying an output, such as a classified image, a crop-stress flag or a change-detection alert, and will rely on that output in its own decisions. That makes the operator a service provider with contract and negligence exposure on the ground, on top of the hardware exposure in space. The rest of this post works through both: what the launch loss in January taught about re-flight economics, what a rideshare launch agreement leaves uninsured, how in-orbit cover works for a satellite this size, and where technology errors and omissions cover fits.

Nine months after PSLV-C62: re-flight economics after a launch loss

MOI-1A is TakeMe2Space's second attempt. Its predecessor, MOI-1, was lost in January 2026 when PSLV-C62 suffered a third-stage anomaly (Reuters, 28 September 2026). Nine months later the replacement is in orbit on a different launcher.

That sequence is the clearest way to see what launch cover is actually for in a startup. A launch failure destroys the hardware, but the hardware is usually not the biggest cost. The founder also loses:

  • the launch slot and the fee paid for it, which is rarely refunded on a vehicle failure;
  • the months of engineering time spent on integration, environmental testing and launch campaign logistics;
  • revenue and customer momentum that depended on a service start date;
  • in some cases, investor confidence at a point when the next funding round was planned around a working satellite.

A conventional launch policy written on the sum insured of the satellite pays for the first category only if the launch fee is included in the insured value, and pays nothing for the last two unless the wording is extended. Space underwriters can include the launch service cost and a re-flight allowance in the agreed value, and that is usually the more useful structure for a startup than insuring the bill of materials alone.

What a re-flight budget needs to cover

When structuring the next launch, a founder who has already lost one satellite should budget for the replacement unit, a fresh launch slot at current rideshare prices, a second round of environmental testing, and the operating cash burn for the months between the loss and the new launch date. The question to put to the broker is how much of that list a launch policy can absorb as agreed value, and how much has to sit in the company's own reserves or in the investor plan.

What a rideshare launch agreement leaves uninsured

Every Indian payload on Transporter-18 flew as one of roughly 130 co-passengers. On a rideshare, the smallsat operator usually contracts with the launch provider or an aggregator, and the launch services agreement sets the risk allocation before any insurer is involved. The details differ by contract, so the operator needs to read its own agreement, but three points recur.

  1. Cross-waivers of liability. Rideshare agreements commonly include reciprocal waivers under which each party bears its own losses and does not sue the launch provider or the other payload owners. If the launcher fails or a co-passenger damages your satellite at separation, the waiver usually means there is no one to recover from. Your own launch policy is the only source of money.
  2. No re-flight guarantee. A launch provider will often offer a future slot on a best-efforts or paid basis after a failure, but that is not insurance and does not refund the satellite.
  3. Insurance and indemnity flow-downs. The agreement may require the payload owner to carry its own third-party liability cover, to name the provider as an additional insured, and to waive subrogation against it. Those requirements need to appear in your policy wording, or you may be in breach of the launch contract.

The practical consequence is that the cross-waiver moves the whole first-party risk onto the payload owner. A startup that declines launch cover because the premium looks high relative to a small satellite is choosing to self-insure a loss it cannot recover from anyone else.

For more on how the launch, commissioning and in-orbit phases hand over between policies, see our guide to launch and in-orbit insurance for Indian smallsat startups.

In-orbit cover for sub-50 kg satellites

Once a satellite separates and completes commissioning, the launch policy ends and in-orbit cover begins. For satellites at MOI-1A's scale (14 kg on one report, under 50 kg on another), the in-orbit decision is mostly about economics.

Why many smallsat operators self-insure in orbit

Smallsat in-orbit cover is placed into the international space market through a domestic fronting insurer, with most of the risk carried by reinsurance capacity abroad. Minimum premiums, survey costs and the underwriting effort per satellite do not fall in proportion to satellite value. For a low-cost satellite with a short design life, the annual premium can approach a large share of the depreciated value, and many operators conclude it is cheaper to plan for a replacement unit than to insure the one in orbit.

That reasoning works for a constellation operator with spares on the shelf. It works less well for a single-satellite service provider whose entire revenue depends on one craft. If MOI-1A were to fail early in its life, TakeMe2Space would face the same re-flight cycle it went through after PSLV-C62, with 23 customers waiting.

What to negotiate if you do buy in-orbit cover

  • Total and partial loss definitions. An orbital-compute satellite can lose value through a failed processor or storage module while the bus is fine. A wording that only pays on loss of the spacecraft will not respond. Ask for capacity-based partial-loss triggers tied to compute and storage availability.
  • Commissioning period. Early-life failures cluster in the first weeks. Make sure the launch policy's commissioning window and the in-orbit policy's start date leave no gap.
  • Agreed value. Include the cost of re-flight, not just the hardware.
  • Radiation and software exclusions. Underwriters may exclude losses from known design defects or from software uploads that were not tested on the ground. Edge-compute payloads that receive model updates in orbit need clarity on this point.

Data-service liability: when the satellite sells inference

A traditional imaging satellite sells raw or lightly processed data, and the customer does the analysis. MOI-1A runs the analysis on board. That shift changes who is responsible when an output is wrong.

Consider the sectors Reuters listed among TakeMe2Space's customers. An agriculture customer might use an in-orbit model to flag crop stress and time an input purchase. A supply chain customer might rely on a change-detection alert. An insurance customer might use outputs to support crop or property loss assessment. In each case, a misclassification, a corrupted file, a missed delivery window or a model that drifts after an update can lead to a financial loss for the customer, and the customer will look to the contract and to the operator.

The exposures a property or space policy does not touch

  • Errors in output. A wrong classification or a missed detection that causes a customer to act on bad information.
  • Service failure. Downtime because the satellite is in safe mode, a ground station is unavailable or a processing queue fails, leading to missed service levels.
  • Data handling. Customer data or models uploaded to the satellite, stored on 2 TB of on-board storage and downlinked through third-party ground stations, create a security and confidentiality exposure on the ground segment.
  • Intellectual property. Customer-supplied models running on shared hardware raise questions about who owns derived outputs and what happens if one customer's workload affects another's.

None of these is a space risk. Space hull and in-orbit wordings insure the physical asset and, at most, its revenue-generating capacity. They do not cover the operator's legal liability to customers for the quality of a service. That gap sits with a separate liability line.

Tech E&O and cyber cover for processing data in orbit

The natural home for the data-service exposure is technology errors and omissions cover, typically written as a professional indemnity policy with a technology services definition, often combined with cyber insurance for data breach and network security events. Indian insurers write tech E&O for SaaS and IT services companies routinely, and the structure carries over to an orbital-compute operator with some adjustments.

Points to settle in the wording

  1. Definition of professional services. The policy should describe the business as including processing, storage and delivery of data using space-based computing infrastructure. A generic IT services definition may leave room to argue that satellite operations fall outside it.
  2. Space exclusions. Some liability wordings exclude any loss arising from aircraft, spacecraft or satellites. That exclusion, if left in, could remove cover for the core service. Ask for it to be deleted or narrowed to physical damage to the spacecraft.
  3. Contractual liability. Customer contracts often include service credits, warranties and indemnities. E&O policies generally cover liability that would exist without the contract, so the operator should cap its contractual promises at levels the policy can respond to.
  4. Cyber and ground segment. Breach costs, ransomware on ground infrastructure and third-party data liability belong in cyber cover. Check that the cyber policy treats the satellite and its uplink as part of the insured's computer system, or at least does not exclude them.
  5. Limit sizing. With 23 customers across agriculture, mining, supply chain and insurance, the limit should reflect the largest single customer's potential loss and an aggregate across several customers affected by one failure, such as a faulty model update.

Our guide on tech E&O insurance for SaaS startups in India sets out the policy mechanics in more detail. Most of it applies directly to a company that sells inference from orbit rather than from a data centre.

What comes next: GalaxEye, Vikram-1 and the renewal queue

Transporter-18 was not the only signal in the past few weeks. GalaxEye raised $6.7 million from the RDI Fund (Inc42 weekly funding report, 26 September 2026), and Skyroot is targeting its second Vikram-1 launch by the end of 2026, likely carrying commercial and technology-demonstration payloads, after the first Vikram-1 reached orbit on 18 July 2026 (WION and NewsBytes, August to September 2026).

For brokers and founders, that points to a busy few months. More Indian payloads will need launch cover, and a domestic launcher with one flight in its record will be rated very differently from a Falcon 9 rideshare. Operators choosing between launchers should get indicative launch premium quotes for each option before signing, because the insurance cost can change the comparison.

A checklist for orbital-compute and smallsat operators

  • Read the launch services agreement for cross-waivers, insurance requirements and subrogation waivers before placing cover.
  • Decide whether the launch policy's agreed value includes re-flight costs.
  • Make the in-orbit decision deliberately, comparing self-insurance against a single-satellite revenue dependency.
  • Put tech E&O and cyber cover in place before the first paying customer output is delivered, and check both for satellite exclusions.
  • Align customer contract caps with the E&O limit.

The earlier guide on insurance for Indian space-tech and satellite startups covers the wider set of policies a space company needs on the ground, from cleanroom property to directors' and officers' liability.

Frequently Asked Questions

Does a SpaceX rideshare launch include insurance for my satellite?
Generally no. The launch services agreement sets the risk allocation, and rideshare contracts commonly include cross-waivers under which each party bears its own losses. If the launcher fails or a co-passenger damages your satellite, you usually cannot recover from them. The payload owner has to buy its own launch cover, and the agreement may also require it to carry third-party liability cover and waive subrogation against the provider. Read your own contract, because terms vary.
Is in-orbit insurance worth buying for a satellite under 50 kg?
It depends on how the business earns money. For a constellation operator with spare units ready, self-insuring and replacing a failed satellite is often cheaper than paying annual premium on a depreciating asset. For a single-satellite service provider whose revenue depends on one craft, the cost of a failure includes customer losses and a full re-flight cycle, so cover with capacity-based partial-loss triggers can make sense. Get quotes and compare them against the full replacement cost, not just the hardware.
Will my space insurance cover claims from customers if an in-orbit AI model produces a wrong result?
No. Launch and in-orbit policies cover physical loss of the satellite and, at most, loss of its capacity. Liability to customers for errors, missed service levels or data handling sits under technology errors and omissions cover, usually written as professional indemnity, often alongside cyber insurance. Check those liability wordings for exclusions relating to spacecraft or satellites, because such an exclusion could remove cover for the core service.
Can launch insurance pay for re-flying a satellite after a launch failure?
Only if the policy is built for it. A launch policy written on the satellite's hardware value pays for the bill of materials and little else. Space underwriters can set the agreed value to include the launch service fee and a re-flight allowance, which is usually the more useful structure for a startup. Lost revenue, delayed customer contracts and months of operating burn before the next launch are not covered unless the wording is specifically extended, so most founders need reserves or an investor plan for that part.

Related Glossary Terms

Related Insurance Types

Related Industries

Related Articles

Sarvada Intelligence

Ready to see Sarvada in action?

Explore the platform workflow or start a product conversation with our underwriting automation team.

Explore the platform