Mission-readiness OS for European sovereign smallsat programs to prove propulsion maneuvers and crowded-orbit compliance before flight.

1. A public €6.3 million EIC award is a concrete sign that European institutions are actively funding sovereign propulsion capacity, which creates real programs that need supporting software.
2. BeaconSat ties the technology to Austria's first military satellite, so maneuver-readiness is no longer hypothetical research but a near-term defense workflow.
3. Rideshare orbit transfer being called out as a demand driver means more missions will need software to prove how they safely move from insertion orbit to mission orbit.
4. Rendezvous and proximity operations are becoming relevant for smaller sovereign programs, increasing the value of structured maneuver planning and evidence capture.
5. Crowded-orbit regulation raises the burden of proof around maneuvers, which makes compliance-ready records a buying trigger instead of a nice-to-have.

Catalyst. GATE Space's EIC-backed industrialization, BeaconSat integration, and cited demand from rideshare transfer, RPO, and crowded-orbit regulation show that sovereign missions need maneuver-assurance software now, not after fleets scale.

The product acts as the system of record for propulsion-enabled mission readiness. It combines propulsion-vendor performance data, mission design, and customer or regulatory constraints into a single workflow that outputs maneuver budgets, required ground tests, exception logs, and approval packets. Teams can run pre-launch what-if scenarios for rideshare insertion, orbit transfer, and proximity operations without rebuilding the review deck from scratch each time. Once in flight, the software becomes the audit trail for executed maneuvers, deviations, and lessons learned, which compounds into a proprietary benchmark set for future sovereign missions.

What's different. Most space-software tools either optimize mission design for engineers or focus on fleet operations after launch. This company sits in the neglected approval layer between propulsion vendors, satellite primes, and sovereign customers, where launch dates and compliance risk create budget urgency. By owning maneuver-readiness evidence across programs, it can build the best dataset on what actually blocks or clears propulsion-enabled sovereign missions.

Jobs to be done

flowchart LR
  Buyer[Mission operations lead] --> Pain[Propulsion maneuvers lack auditable readiness proof]
  Pain --> Product[Orbital mobility certification OS]
  Product --> Outcome[Faster launch approval and safer sovereign missions]

Executive takeaways

• The real wedge is not generic astrodynamics; it is turning propulsion, rideshare, and SST inputs into an auditable readiness packet a sovereign reviewer can sign.
• European sovereignty spending makes the pain budget-backed, but the initial buyer pool is still measured in dozens of programs rather than hundreds.
• Substitutes are abundant—STK, FreeFlyer, in-house Orekit/PATRIUS stacks, and STM platforms already sell into the same teams—so the product must look like workflow closure, not another solver.
• If the company captures data from early RPO, refueling, and sovereign ISR missions, it can expand from pre-launch readiness into in-flight maneuver, anomaly, and compliance infrastructure.

Market definition

Mission-readiness software for propulsion-enabled smallsat programs that sits between flight-dynamics tools, propulsion vendors, launch providers, and SST/compliance systems to generate maneuver plans, verification evidence, and approval packets.

Customer and buyer

Day-to-day users are mission-operations leads, flight-dynamics engineers, and propulsion integration teams at European sovereign or dual-use smallsat programs. The economic buyer is usually the chief engineer, mission-operations VP, or satellite program manager who owns launch readiness, ministry signoff, and schedule risk.

Buying triggers

• A rideshare or institutional launch slot is fixed, and the team must prove pressure-system, maneuver, and integration readiness without slipping the manifest. [15][16][17]
• A sovereign ISR or defense mission adds maneuverability, proximity-operations, or rapid-retasking requirements that legacy launch/readiness packets were not built for. [1][7][8][18][19][20][21]
• Collision-avoidance, deorbit, or debris-governance expectations force operators to show clearer traceability between propulsion capability, planned maneuvers, and compliance posture. [9][10][11][13][14]

Willingness to pay

Willingness to pay is tied to already-funded mission infrastructure, not experimental software budgets. Gate's Jetpack S alone lists a €450k base price, Germany committed $1.9B to a sovereign SAR constellation, the UK is adding £1.4B of defence-space investment, and ICEYE markets sovereign systems that can be operational within 12 months. A workflow layer that reduces launch-slip or approval risk can credibly capture a small fraction of those mission budgets. [1][2][7][8][20][21]

Category dynamics

Growth signal 12.2% CAGR (top-down satellite-propulsion market, 2024-2030)

Validation signals

• Gate Space already sells a standardized mobility system with a €450k base price and names rideshare, RPO, and crowded-orbit regulation as live demand drivers.
• Isar says European defense-side launch demand is already far enough out that 2029 capacity must be booked now.
• EU SST already serves 400+ organizations and 600+ satellites, which shows operators will adopt external safety/compliance services when they are useful.
• ICEYE markets sovereign space systems that can be launched, deployed, and operational within 12 months, proving buyers reward faster, vertically packaged mission infrastructure.

Regulatory & technical constraints

• SpaceX rideshare missions require pressure-vessel qualification and integrated leak-test evidence for propulsion systems.
• ECSS-E-ST-35C Rev.1 imposes functional, environmental, quality, operational, and verification requirements across liquid, solid, and electric propulsion.
• EU SST access is registration-based and increasingly part of the operating baseline for European collision avoidance, re-entry, and fragmentation workflows.
• The proposed EU Space Act would add harmonized licensing, debris, cybersecurity, and collision-avoidance obligations for operators serving the EU market.

Incumbents cover pieces of the workflow: mission-design suites calculate trajectories, open-source stacks let engineers script anything, and STM vendors triage conjunction risk. The white space is the system-of-record layer that packages propulsion data, launch constraints, SSA inputs, and reviewer-facing evidence for one sovereign mission.

Why incumbents do not win by default

• Mission-analysis suites. STK and FreeFlyer are powerful physics and operations environments, but their public positioning centers on modeling and execution, not a sovereign approval packet that unifies propulsion, launch, and compliance evidence.
• Open-source / in-house flight dynamics. Orekit, PATRIUS, and Basilisk give technical teams flexibility and low license cost, but they push validation, workflow design, and auditability back onto the customer.
• Space safety / STM platforms. GMV, Neuraspace, OKAPI:Orbits, and Slingshot reduce conjunction and orbital-awareness burden, yet their center of gravity is on alerting and safety operations rather than pre-launch propulsion-readiness orchestration.
• Servicing and mobility operators. ClearSpace, Astroscale, and Orbit Fab are creating the missions that make mobility assurance valuable, but they are hardware and mission operators first, which leaves room for a neutral software layer across multiple vendors and primes.

European sovereign and dual-use smallsat programs can now buy industrialized chemical propulsion—GATE Space's €6.3M EIC Accelerator win and BeaconSat integration confirm this—but the bottleneck has shifted from hardware availability to mission-readiness evidence. Mission teams assembling maneuver budgets, rideshare compliance packs, and ministry approval decks today rely on STK or GMAT analyses, vendor PDFs, and spreadsheets coordinated over email, which extends review cycles and creates launch-slip risk when rideshare dates are fixed. Orbital Mobility Certification OS is the system of record that ingests propulsion-vendor performance data, mission constraints, and SST inputs to generate auditable maneuver plans, verification evidence, and approval packets sovereign buyers can defend. The immediate beachhead is European defense-space primes and sovereign smallsat builders preparing first rideshare-launched ISR or military demonstration satellites with third-party chemical propulsion—a pool of dozens of active programs backed by more than €3B in visible sovereign commitments. The product's data moat compounds: every mission ingested adds maneuver outcomes, reviewer feedback, and anomaly patterns that make future programs faster and the dataset harder to replicate. Two evidence gaps remain that must be resolved in the first 90 days: buyer procurement timelines and exact ministry reviewer acceptance criteria for software-generated packets have not been directly confirmed, and structured propulsion-vendor data sharing is unverified.

Problem

• European sovereign smallsats can now fly with maneuver capability, but mission teams have no repeatable workflow to generate the auditable readiness evidence ministries and primes require before flight.
• STK or GMAT analyses, propulsion-vendor PDFs, and manual review decks are stitched together per program, extending review cycles by weeks and increasing rideshare launch-slip risk when timelines are fixed.
• Crowded-orbit and EU SST compliance obligations raise the proof burden: teams must now produce traceability between propulsion capability, planned maneuvers, and regulatory posture—not just technically correct simulations.
• RPO and proximity operations are entering smaller sovereign programs, but no purpose-built workflow packages the evidence those maneuver classes require for approval.

Solution

• A mission-readiness OS that ingests structured propulsion-vendor performance envelopes, mission design parameters, launch constraints (SpaceX rideshare guide, ECSS-E-ST-35C), and EU SST feeds to produce maneuver budgets, compliance records, and reviewer-facing approval packets.
• Pre-launch what-if scenarios for rideshare insertion, orbit transfer, RPO, and deorbit that re-run instantly when mission parameters change, eliminating the need to rebuild the review deck from scratch each time.
• Immutable decision lineage tying CDM responses, propulsion-test results, and operator overrides to approved maneuver plans—creating the audit trail sovereign customers need and accumulating a cross-program benchmark dataset with each mission ingested.

Why we win

• The product occupies the neglected approval layer between propulsion vendors, primes, and sovereign customers—a gap incumbents (STK, FreeFlyer, GMV) do not centrally address because their center of gravity is physics modeling or safety operations, not multi-stakeholder readiness orchestration.
• By owning the system-of-record role early, the company builds a cross-mission dataset of propulsion envelopes, reviewer outcomes, and anomaly patterns that is costly to replicate and grows more accurate with each program ingested.
• European sovereignty urgency creates budget-backed demand now: more than €3B in visible program commitments (Germany SAR constellation, UK Defence Space Strategy £1.4B, ICEYE Series F >€1B) means customers already have funding and schedule pressure to adopt a purpose-built readiness workflow.
• Distribution enters through propulsion vendors and launch integrators who already access the customer at the moment maneuverability requirements become mandatory, reducing cold-outreach CAC versus direct-only sales.

Milestones

flowchart LR
  Wedge[First sovereign mission pilot] --> MVP[Approval packet MVP]
  MVP --> Proof[Signed readiness packet and cycle-time evidence]
  Proof --> PropPartner[Propulsion vendor data partnership]
  PropPartner --> Expansion[Multi-mission accounts and RPO module]
  Expansion --> Dataset[Cross-program benchmark dataset]
  Dataset --> Moat[Switching-cost moat and upsell tiers]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least 15 European sovereign or dual-use smallsat missions integrating third-party chemical propulsion are fundable and scheduled to launch in 2027-2029, providing a reachable initial customer pool.
• Mission teams will pay $250-400k per year for a readiness workflow that demonstrably reduces approval cycle time and launch-slip risk by more than the cost of one additional flight-dynamics engineer.
• At least one propulsion vendor (GATE Space, ThrustMe, or equivalent) will share structured performance data in a machine-readable format that enables automated packet generation.
• Ministry or prime assurance reviewers will accept software-generated readiness packets as a primary review document within 12-18 months of first production use.
• The cross-program maneuver dataset creates measurable switching costs by the second mission per account, enabling net revenue retention above 120%.

Open diligence questions

• Can the founding team name 5 European sovereign programs entering propulsion integration in 2026-2027 and confirm their flight-readiness review timelines and reviewer requirements?
• Will GATE Space, ThrustMe, or Bradford share machine-readable propulsion performance and qualification data under a data-sharing agreement, and on what terms?
• What does a ministry or prime assurance reviewer actually require in a readiness packet—checklist, immutable log, third-party certification—and would a software-generated document satisfy that requirement today?
• How many flight-dynamics engineers does a typical target prime currently dedicate to one mission's readiness workflow, and what is the fully loaded annual cost versus the proposed ACV?
• Which incumbent (STK reseller, GMV, or in-house Orekit team) is most likely to expand into the readiness-packet layer, and on what timeline?
• Is the founding team's astrodynamics and sovereign-procurement credibility sufficient to win a first pilot without a recognized domain-expert advisor on the cap table?

Model sanity

• Revenue engine. The base case is driven by one Y1 production conversion, 4 production customers by Y2 end, and 10 by Y3 end at a blended $330K annual ARPU.
• Must go right. At least one propulsion vendor must share structured data and reviewers must accept the generated packet so the company keeps 72% gross margin instead of falling into services-heavy delivery.
• Model breaks if. If sales cycles slip by about one quarter and Y3 exits with 8 accounts instead of 10, the model gives up roughly $220K of Y3 revenue and about $238K of ending cash.
• Next-round proof. The seed round is justified if the company reaches 4 production accounts and one live vendor integration by Q4Y2, which is the bridge to the Y3 10-account and $3M+ ARR Series A narrative.

Scenarios

Sensitivity

flowchart LR
  Leads --> Pilots
  Pilots --> ProductionCustomers
  PropulsionData --> ProductionCustomers
  ProductionCustomers --> Revenue
  Revenue --> GrossProfit
  GrossProfit --> Cash

Flags: Base case requires 10 paying accounts by Y3 in a SAM measured in dozens of programs, so concentrated-account execution risk remains high. · The model excludes pilot and onboarding revenue for conservatism; if those services become mandatory to win deals, gross margin and hiring assumptions need to be revisited. · If reviewers accept the product only as an internal engineering aid, BP operating assumptions imply ACV could compress by 30-40%, which would make the current hiring ramp too heavy.

• Niche market timing. European sovereign smallsat programs may still be too few in the near term to support a large standalone business. Mitigation: Start with propulsion-heavy sovereign missions, then expand into adjacent dual-use and commercial in-orbit mobility programs using the same readiness workflow.
• Integration burden. Mission teams may resist adopting another system if it cannot fit existing astrodynamics, assurance, and document-review tools. Mitigation: Integrate first with the tools teams already use and export approval packets into existing ministry and prime review formats.
• Trust and liability. If customers treat the software as a formal certification authority, any maneuver failure could create legal and reputational exposure. Mitigation: Position the product as an auditable decision-support and evidence layer while partnering with mission-assurance experts for final signoff.