Insurance for Startups & New Economy

Launch and In-Orbit Insurance for Indian Smallsat Startups Under the IN-SPACe Regime in 2026

Indian smallsat startups operating under IN-SPACe authorisation and the Indian Space Policy 2023 face a risk that runs from the factory through launch into years of orbital life, and almost none of it can be placed in the domestic market without global reinsurance and Lloyd's capacity. This post sets out the pre-launch, launch and in-orbit phases, third-party launch liability, total-loss versus partial-loss settlement, and the product-liability and contractual flow-downs a spacetech founder and broker have to handle.

Sarvada Editorial TeamInsurance Intelligence
21 min read

Listen to this article

Audio version • 21 min read

smallsatspace-insurancein-spacelaunch-liabilityin-orbitspacetechreinsurancestartups-new-economy-insurance

Last reviewed: June 2026

The Indian smallsat sector and the regime it operates under

India's private space sector has moved from a standing start to a real industry in a few years, and smallsat startups (companies building and operating small satellites for earth observation, communications, internet-of-things connectivity and technology demonstration) sit at the centre of it. Companies such as Pixxel, Dhruva Space, GalaxEye and Digantara are building and flying smallsats, and a growing set of launch-service and component startups support them. The enabling change was policy: the Indian Space Policy 2023 opened the sector to non-governmental entities, and the Indian National Space Promotion and Authorisation Centre (IN-SPACe), set up in 2020, became the single-window authoriser and regulator for private space activity, working alongside ISRO and the commercial arm NewSpace India Limited (NSIL).

Under this regime, a smallsat operator needs IN-SPACe authorisation for its space activity, whether that is building and operating a satellite, providing a launch service, or operating a ground segment. The authorisation process examines the technical, safety, debris-mitigation and liability aspects of the activity, and it is the gateway through which the activity becomes lawful. India is a party to the international space-law treaties (the Outer Space Treaty 1967, the Liability Convention 1972 and the Registration Convention 1975), under which the launching state bears international liability for damage caused by space objects, so the state has a direct interest in the liability arrangements behind every authorised activity. The authorisation framework and the eventual domestic space legislation are building out the liability and insurance expectations that operators must meet.

For a smallsat startup the insurance problem is unusual in two ways. First, the risk runs across a long lifecycle, from the factory through transport, integration, launch and orbital insertion into years of operational life, and each phase is a different exposure with a different insurance answer. Second, space risk is one of the hardest classes to place anywhere, and especially in India, because the sums at risk are large relative to the frequency of events, the losses are total and catastrophic when they happen, and the technical underwriting depends on a small global pool of specialist capacity. An Indian insurer fronting a space policy is almost entirely dependent on global reinsurance and the London and Lloyd's market for the capacity and the expertise, which shapes how these covers are placed and priced. The sections that follow set out the phases, the third-party liability, the total-versus-partial question, the product-liability and contractual flow-downs, and the market reality a founder and broker have to work within.

Pre-launch: the phase before the rocket lights

The first insurable phase is everything before launch: the manufacture, assembly, integration and testing of the satellite, its transport to the launch site, and its integration onto the launch vehicle. This pre-launch phase is, in insurance terms, closer to a property and transit exposure than to a space exposure, and it is the phase a smallsat startup can most readily insure in the domestic market.

What pre-launch cover protects

While the satellite is being built and tested in the cleanroom, it is a high-value asset exposed to the ordinary perils of a manufacturing environment: fire, accidental damage during handling and testing, contamination, and the destruction of expensive flight hardware by a test gone wrong. A property or all-risks cover on the satellite and its components, written on the value of the flight hardware, protects this. As the satellite moves to the launch site, often a long road and air journey to Sriharikota or to a foreign launch site for a ride on a foreign vehicle, a transit and cargo exposure arises, and the satellite needs cover for damage in transit. At the launch site, during storage, fuelling and integration onto the vehicle, the pre-launch cover continues until the agreed handover point to the launch risk.

Why the pre-launch phase matters for the smallsat startup

For a startup, the satellite represents a large share of the company's capital and often years of work, and a loss in the cleanroom or in transit, before any space risk has even attached, can be existential. The pre-launch cover is comparatively straightforward, can be placed with Indian insurers drawing on standard property, marine cargo and erection-type wordings, and is the phase where the founder has the most control and the most conventional insurance options. The cover should value the satellite on a basis that reflects the true cost of rebuilding and re-qualifying flight hardware, which is more than the bill of materials, because re-manufacturing a one-off satellite to flight standard and re-running the qualification testing is expensive and slow.

The handover to launch risk

The critical wording point in the pre-launch phase is where it ends and the launch risk begins. The transition is usually defined by a precise event, commonly intentional ignition of the launch vehicle, sometimes a defined point in the countdown or the moment of integration onto the vehicle. The pre-launch property and transit cover terminates at that point and the launch cover (a different cover, in a different market) attaches. The founder and broker must make sure the two covers meet exactly at the defined handover, with no gap and no overlap-with-dispute, because a loss at the launch site in the final hours before ignition must fall clearly on one cover or the other. Getting the attachment and termination definitions aligned across the pre-launch and launch policies is the central structuring task of this phase.

Launch and in-orbit: the space risk proper

The space risk proper begins at ignition and runs through the launch, the orbital insertion, the early commissioning of the satellite, and then through its operational life in orbit. This is where the large sums and the catastrophic losses sit, and where the dependence on the global market is total.

Launch risk

Launch insurance covers the loss of, or damage to, the satellite from ignition through the ascent, separation and placement into the intended orbit, and usually through an initial in-orbit commissioning or testing period (commonly the first few months, sometimes to the first year) during which early-life failures show up. The launch and early-orbit period concentrates the risk: a launch-vehicle failure destroys the satellite entirely, a deployment failure can strand it in a useless orbit, and an early commissioning failure can render it a total loss before it ever earns revenue. Launch is the single riskiest moment in a satellite's life, and the premium rate for launch-plus-commissioning cover is correspondingly high, historically a substantial double-digit percentage of the insured value in a hard market, varying with the track record of the launch vehicle and the complexity of the satellite. For a smallsat the rating is shaped by how it flies. Most smallsats reach orbit as secondary payloads on a rideshare, sharing a launch with many other smallsats on a proven vehicle, which means the smallsat's launch-risk profile is partly the launch vehicle's record and partly the rideshare dispenser and deployment sequence that releases it among the cluster. A smallsat as one of dozens on a proven rideshare is rated differently from one flying as a primary payload on a new small-launch vehicle, and the operator also has to consider deployment-specific risks (a dispenser failure, a collision risk in a tightly-packed deployment) that a dedicated primary payload does not carry. The rideshare model lowers the launch cost per satellite but introduces these shared-launch deployment exposures into the rating and the wording.

In-orbit life cover and the smallsat self-insurance decision

Once the satellite is commissioned and operating, in-orbit life insurance covers it for its operational life against failure or degradation that causes a loss of the satellite or of its capacity. In-orbit cover is typically written for annual periods and renewed through the satellite's life, with the rate reflecting the satellite's health, its remaining design life and the reliability record of its type. The perils include the failure of subsystems (power, attitude control, payload, communications), collision with debris, and the gradual degradation that ends the useful life early.

The in-orbit decision is where smallsat economics diverge most sharply from large-satellite practice. A smallsat often has a short design life (sometimes only a few years) and a modest insured value relative to the launch-and-commissioning premium it has already paid, so carrying annual in-orbit cover across that life can cost a meaningful fraction of the asset value over time. Many smallsat operators conclude that the rational programme is to insure the launch and early orbit heavily, where the loss is most likely and most total, and then to self-insure the operational phase, absorbing an in-orbit failure on the balance sheet rather than paying years of premium on a low-value, short-life asset. A constellation operator faces the same calculation across many satellites at once, and may choose to self-insure individual in-orbit failures while relying on the redundancy of the fleet, since the loss of one smallsat in a constellation is not the loss of the mission. The self-insure-versus-insure call is a deliberate commercial judgement particular to the smallsat model, not a default, and the operator should make it explicitly against its design life, asset value and the revenue each satellite carries.

The economics sharpen once the operator runs the fleet as a serially-produced line rather than as one-off bespoke spacecraft. A constellation built on a repeated satellite bus, manufactured in batches and launched on a regular replenishment cadence, is closer in spirit to a depreciating vehicle fleet than to a single irreplaceable asset, and the operator can spare-and-swap an attritional in-orbit failure by bringing the next production unit forward rather than claiming on a policy. When a smallsat dies, much of its insurable worth has often already amortised over the operational months it flew, so the residual value that an in-orbit claim would protect is the depreciated remainder, not the launch-day figure. A short-life smallsat near the end of its planned mission is frequently uneconomic to insure at all, because the annual premium load approaches the writeoff value the policy would pay. The rational programme for a serially-replenished constellation is therefore often to insure the launch heavily, carry the early commissioning, and then let the fleet's spares and replenishment schedule absorb attritional in-orbit losses, treating the constellation's redundancy as the operator's own self-funded cover. A bespoke single high-value smallsat with no replacement waiting reaches the opposite conclusion, and the founder should decide which model the company actually runs before fixing the in-orbit strategy.

Why this all routes through global reinsurance

The Indian market has very limited domestic appetite and expertise for launch and in-orbit risk, so these covers are placed through Indian insurers fronting capacity assembled from the global space-insurance market, principally London, Lloyd's and the specialist European and US space underwriters and reinsurers. The technical underwriting (assessing the launch vehicle's reliability, the satellite's design, the failure modes) is done by a small global community of space underwriters, and the capacity for a single launch is syndicated across many of them because no single insurer carries the whole value. An Indian smallsat operator's launch and in-orbit cover is therefore, in substance, a placement into the global space market arranged through a domestic insurer, and the broker's job is to access that market and assemble the capacity, not to find it onshore.

The clean way to think about the lifecycle is three insurance regimes, not one. Pre-launch (factory, transit, integration) is a property and cargo exposure that the Indian market can write on conventional wordings. Launch-plus-commissioning is a high-rate, catastrophic-loss exposure placed into the global space market. In-orbit life is an annually renewable space exposure the operator may carry or self-insure on commercial judgement. The covers must meet exactly at the defined handover points (intentional ignition, end of commissioning) so no loss falls between them.

Rideshare and secondary-payload deployment: the smallsat's distinctive launch exposure

The defining commercial fact about a smallsat is how it gets to orbit. Very few smallsats buy a dedicated launch; the overwhelming majority ride as a secondary payload on a rideshare mission, sharing a single launch vehicle with anywhere from a handful to over a hundred other smallsats. SpaceX Transporter flights, ISRO's PSLV co-passenger slots and the dedicated rideshare aggregators have made this the default route to orbit, and it reshapes the smallsat's launch-risk profile in ways a dedicated-launch satellite never sees. The rating, the wording and the recovery mechanics all bend around the rideshare arrangement, so a founder and broker have to underwrite the deployment, not just the rocket.

The shared-ride deployment chain adds its own failure points

A dedicated primary payload sits on top of the vehicle and separates once. A rideshare smallsat sits inside a dispenser or deployer (a port-style ejection mechanism, often supplied by a third-party integrator, not the launch provider) and is released in a choreographed sequence among many co-passengers. That chain introduces exposures the primary-payload satellite simply does not carry: a dispenser spring or door that fails to actuate, a release that imparts the wrong tip-off rate and tumbles the satellite, a mis-timed ejection that risks recontact with another co-passenger, and the recontact and conjunction risk inherent in releasing a dense cluster into nearly the same orbit within minutes. The smallsat's launch-risk profile is therefore part launch-vehicle reliability and part deployer-and-sequence reliability, and the underwriter prices both. A flight-proven vehicle carrying the smallsat through a novel or lightly-flown dispenser is not the clean low-risk story the vehicle's track record alone suggests.

How the rideshare arrangement shapes the rating

Flying as one of dozens on a high-heritage rideshare vehicle generally attracts a keener launch rate than flying as the primary on a maiden small-launch vehicle, because the dominant variable, the vehicle's flight record, is favourable. But the rideshare introduces aggregation and attribution questions that feed the rate and the wording. If a vehicle anomaly destroys the whole stack, every co-passenger's insurer pays at once, an accumulation the space market watches closely on the densest rideshares. And where a deployment failure strands or damages one smallsat among many, the wording has to pin down whether the loss is the vehicle's, the dispenser integrator's or no one's contractually, because that determines whether the smallsat's own launch policy responds or the operator chases a contractual remedy that the inter-party waivers may have signed away. The rideshare lowers the price of a ticket to orbit and raises the importance of reading exactly where the deployment risk lands.

The aggregator contract sits between the smallsat and the launch provider

A further wrinkle peculiar to rideshare is that the smallsat operator often does not contract directly with the launch provider at all. It buys a slot from a rideshare aggregator or integrator that books bulk capacity on the vehicle and resells it to many small operators, supplying the dispenser and the integration service. The smallsat's insurance, liability allocation and inter-party waivers are then governed by the aggregator's terms rather than the launch provider's prime contract, and those terms flow the launch provider's waivers and indemnities down to the smallsat through an intermediate layer. The broker has to read the aggregator agreement, not just the headline launch contract, because that is the document that actually sets the smallsat's insurance obligations, its waiver position and what it can recover if the deployment goes wrong.

Why space risk is so hard to place in the Indian market

The structural fact a smallsat founder has to absorb is that space risk does not sit comfortably in the Indian insurance market, and understanding why explains how the cover actually gets placed and priced.

The nature of the risk

Space risk has a shape that is uncomfortable for any insurer: the sums at risk on a single satellite are large, the frequency of losses is low but the severity when a loss occurs is near-total, and the technical assessment of whether a launch vehicle or a satellite will fail demands deep, specialist engineering judgement that very few underwriters anywhere possess. A class with high severity, low frequency and a tiny pool of expertise is a class that no single insurer can write on its own balance sheet, because one loss can wipe out years of premium, and a class that cannot be assessed without specialist knowledge cannot be priced by a generalist. These features hold worldwide, and they hold more sharply in India, where the domestic market has neither the accumulated space-underwriting expertise nor the appetite to carry the severity.

How the cover is actually placed

The consequence is that an Indian smallsat operator's launch and in-orbit cover is, in substance, placed into the global space-insurance market through an Indian insurer that fronts the policy. The domestic insurer issues the policy that satisfies the regulatory and contractual requirement for cover from a registered Indian insurer, but the risk is largely ceded to the global reinsurance market, principally the specialist space underwriters and reinsurers in London, Lloyd's, Europe and the US who carry this class. The technical underwriting (the assessment of the launch vehicle's flight record, the satellite design, the failure modes and the orbit) is done by that small global community, and the capacity for a single launch is syndicated across many reinsurers because no one carries the whole value. The premium reflects the global market's view of the risk, the launch vehicle's track record and the hard-or-soft state of the space market at the time, not a domestic rate.

What this means for the founder and the broker

For the founder, the practical implications are concrete. The broker has to be one that can reach the global space market, because the cover cannot be assembled onshore, and the placement has to be started early, because accessing global capacity, presenting the technical case for the satellite and the launch, and negotiating terms takes time. The technical information the underwriters need (the launch vehicle and its record, the satellite design and qualification, the orbit and the mission) has to be prepared to a standard that a specialist space underwriter will engage with, which is more demanding than a domestic property submission. And the cost has to be planned for: launch-plus-commissioning rates running into double-digit percentages of insured value are a material line in a smallsat company's budget, and the founder should build the insurance cost into the mission economics from the start rather than discover it late. The dependence on the global market is not a problem to be solved but a reality to be worked within, and the broker's access to that market is the single most important factor in whether the cover can be placed at all.

Third-party launch liability and the launching-state interest

Separate from the cover on the satellite itself is third-party liability: the liability of the launch and the satellite operator for damage caused to third parties by the launch vehicle or the satellite, on the ground, in the air or in space. This is the exposure the state cares about most, because under the international space-law treaties the launching state is liable to other states for damage caused by its space objects.

Why the liability is the state's problem too

Under the Liability Convention 1972, the launching state is absolutely liable for damage caused by its space object on the surface of the earth or to aircraft in flight, and liable on a fault basis for damage caused in space to another space object. So if an Indian-authorised launch or satellite causes damage to a third party, India as the launching state can be held internationally liable, and the state then looks to the operator that conducted the activity. This is why the authorisation regime examines liability and insurance, and why the framework points toward requiring operators to carry third-party liability cover and, in many regimes worldwide, to indemnify the state above the insured amount. The Indian framework is building out these expectations through the IN-SPACe authorisation process and the developing space legislation.

What third-party launch-liability cover does

Third-party launch-liability insurance covers the operator's legal liability for death, injury or property damage to third parties arising from the launch and, in the relevant cover, from the satellite in orbit and on re-entry. For a launch, the exposure includes damage on the ground near the launch site, damage to other aircraft, and damage to other space objects in orbit. The cover is written to a limit set by reference to the maximum probable loss to third parties and to any limit the authorisation or the launch contract requires. A smallsat operator flying as a payload on someone else's launch vehicle has its liability exposure shaped by the launch contract: the launch provider typically arranges the launch third-party liability and allocates the liability and the indemnities between the parties through the contract, so the smallsat operator's own third-party position is partly determined by what the launch agreement assigns to it.

Re-entry and debris

A further liability dimension is re-entry and debris. A satellite that re-enters the atmosphere, whether at the planned end of life or after a failure, can in principle cause damage on the ground, and the debris-mitigation obligations in the authorisation (de-orbiting plans, collision-avoidance, end-of-life disposal) bear on both the safety case and the liability exposure. As low-earth orbit gets more crowded and collision risk rises, the third-party-in-space liability for a collision becomes a more live exposure, and an operator running a constellation carries this across every satellite. The liability cover and the operator's debris-mitigation practice are connected, and both feed the authorisation and the insurance assessment.

Total loss, partial loss and the product-liability flow-downs

Two technical features of space cover shape what a smallsat operator actually recovers and what it remains exposed to: how total and partial losses are settled, and how product-liability and contractual obligations flow through the chain of suppliers and launch providers.

Total loss versus partial loss

Space policies distinguish a total loss, where the satellite is destroyed or rendered completely useless, from a partial loss or constructive total loss, where the satellite survives but with reduced capacity or shortened life. A launch failure that destroys the satellite is a clean total loss and the policy pays the insured value. The harder cases are partial: a satellite that reaches orbit but with a failed solar array, a degraded payload or a control problem that cuts its capacity or its life. Space wordings define a constructive total loss by reference to a percentage of lost capacity or value (for example, a loss of a defined percentage of the satellite's functional capability or revenue-generating capacity is treated as a total loss), and they provide for partial-loss settlement scaled to the degree of capability lost. The definitions matter intensely, because a smallsat with a partially-failed payload may be commercially crippled but not clearly a total loss under the wording, and whether the operator recovers depends on how the capacity-loss thresholds are written. The founder and broker must read the total-loss and partial-loss definitions carefully and match them to how the satellite actually earns its value, so that a failure that destroys the business case also triggers a recovery.

Product liability and contractual flow-downs

The space supply chain is a chain of contracts, and liability and risk flow through it. A smallsat operator buys launch services, buys subsystems and components from suppliers, and sells data or capacity to customers, and each contract allocates risk. Product liability arises where a component or a service the operator supplies causes loss, and a smallsat startup that builds satellites or supplies data carries product-liability and professional-indemnity-type exposure to its own customers. Flowing the other way, the launch contract and the supply contracts impose obligations on the operator: launch agreements commonly require the customer to carry insurance to defined limits, to waive subrogation against the launch provider and the other payloads (an inter-party waiver of subrogation is standard in launch contracts so that each party bears its own loss and does not sue the others), and to indemnify in defined circumstances. The operator's insurance has to be arranged to meet these contractual requirements, which means the broker has to read the launch and supply contracts and structure the cover to satisfy the insurance, waiver and indemnity clauses, or the operator is in breach of its launch contract and exposed where it assumed it was covered.

The market reality and the founder's path

The practical reality for an Indian smallsat founder is that space cover cannot be bought off a shelf in the domestic market. The pre-launch property and transit cover can be placed onshore, but the launch, in-orbit and third-party-liability covers require a broker who can access the global space-insurance market, assemble syndicated capacity through an Indian fronting insurer, and structure the programme around the authorisation requirements, the launch contract, the loss definitions and the supplier flow-downs. The founder should engage this early, because the insurance requirements feed the IN-SPACe authorisation and the launch contract, and a cover that is arranged late or that does not match the contractual obligations can hold up the launch or leave the company exposed at exactly the moment of greatest risk.

Doing this well depends on reading the launch, in-orbit, liability and supply-contract wordings closely enough to see where each cover attaches and terminates, how the total-loss and partial-loss thresholds are set, and how the waiver and indemnity clauses bind. Sarvada gives commercial insurance brokers structured, searchable access to insurer policy wordings, so the space, liability and contract-driven covers can be compared and matched to the authorisation and launch-contract requirements before a smallsat programme is placed. Request Access to ground your spacetech placements in the actual wording detail across the launch, in-orbit and liability covers.

Frequently Asked Questions

Can an Indian smallsat startup buy launch and in-orbit insurance from an Indian insurer?
In substance the cover is placed into the global market through an Indian fronting insurer, not written onshore. The pre-launch phase (manufacture, testing, transit and integration) is a property and cargo exposure that Indian insurers can write on conventional wordings. The launch, in-orbit life and third-party-liability covers are different: the Indian market has very limited domestic appetite and technical expertise for space risk, so these are placed through an Indian insurer fronting capacity assembled from the global space-insurance market in London, Lloyd's and the specialist European and US underwriters. The technical underwriting is done by a small global community of space underwriters, and the capacity for a single launch is syndicated across many of them because no single insurer carries the whole value. The broker's job is to access that global market and assemble the capacity through a domestic insurer.
What happens if my satellite reaches orbit but only works partially?
Whether you recover depends on the total-loss and constructive-total-loss definitions in the wording. Space policies distinguish a total loss (the satellite is destroyed or rendered completely useless) from a partial loss or constructive total loss (it survives with reduced capacity or shortened life). A constructive total loss is defined by reference to a percentage of lost capacity or value, so a satellite that loses a defined share of its functional capability or revenue-generating capacity is treated as a total loss, and partial losses are settled scaled to the capability lost. The danger is that a satellite with a degraded payload may be commercially crippled yet fall short of the capacity-loss threshold for a constructive total loss, leaving you with a useless asset and no full payout. Match the loss definitions to how your satellite actually earns value and negotiate the thresholds before placing the cover.
Who is liable if a launch or satellite causes damage to a third party?
Under the Liability Convention 1972, the launching state is absolutely liable for damage caused by its space object on the surface of the earth or to aircraft, and liable on a fault basis for damage in space to another space object. So India, as the launching state for an IN-SPACe-authorised activity, can be held internationally liable, and the state then looks to the operator that conducted the activity. That is why the authorisation regime examines liability and insurance and points toward requiring third-party liability cover. Third-party launch-liability insurance covers the operator's legal liability for death, injury or property damage to third parties from the launch and the satellite. When flying as a payload on another vehicle, the launch provider typically arranges the launch third-party liability and the launch contract allocates the liability and indemnities between the parties, so your own position is partly set by the launch agreement.
When should a spacetech founder start arranging insurance?
Early, because the insurance feeds both the IN-SPACe authorisation and the launch contract. The authorisation process examines the liability and insurance arrangements behind the activity, so the cover has to be developed alongside the authorisation rather than after it. The launch contract commonly requires the customer to carry insurance to defined limits, to waive subrogation against the launch provider and the other payloads, and to indemnify in defined circumstances, and your insurance has to be structured to meet those clauses or you are in breach of the launch contract. A cover arranged late, or one that does not match the contractual obligations, can hold up the launch or leave the company exposed at the moment of greatest risk. Engage a broker who can access the global space market early, so the programme is built around the authorisation, the launch contract, the loss definitions and the supplier flow-downs from the start.

Related Glossary Terms

Related Insurance Types

Related Industries

Related Articles

Sarvada

Ready to see Sarvada in action?

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

Explore the platform