Power scheduling and settlement OS for EO satellite fleets buying beamed energy to unlock more imaging and downlink hours.

1. Fresh institutional funding means orbital power is graduating from research concept to a commercial infrastructure category that operators must plan around.
2. Compatibility with standard solar panels and no custom receivers makes software adoption possible before a full hardware refresh cycle.
3. Seven PPAs and a stated commercial pipeline show there will soon be real power bookings to route, optimize, and settle rather than just demos to monitor.
4. Defense backing and senior Space Force credibility increase the odds that early buyers will have mission urgency and budget for premium operational tooling.
5. A late-2026 beaming mission after prior records and subsystem demos gives operators a near-term deadline to prepare power-aware mission workflows.

Catalyst. Star Catcher's funding, no-retrofit compatibility claim, seven PPAs, and late-2026 demo timeline mean orbital power is moving from physics demo to commercial procurement problem right now.

The product ingests ephemeris, battery state, payload duty cycles, imaging backlog, downlink windows, and available beamed power sessions to recommend when each satellite should buy external energy. It converts those recommendations into operator runbooks, provider booking requests, and mission-level ROI forecasts tied to specific customer SLAs or surge events. A settlement layer maps purchased power to incremental output such as additional images captured, inference jobs completed, or data downlinked, so operators can see whether power spend created profitable mission yield. Over time the platform learns fleet-specific power-response curves and becomes the system of record for orbital energy procurement and dispatch.

What's different. This is not generic satellite mission-planning software and not a hardware bet on the power-beaming network itself. It is the orchestration and settlement layer for a new utility market in orbit, built around the specific economics of buying watts only when a mission spike justifies it. The defensible advantage comes from accumulating real data on beam-window availability, battery-response curves, payload uplift, and power-to-revenue conversion across multiple fleets and providers.

Jobs to be done

flowchart LR
  Buyer[EO constellation operator] --> Pain[Cannot decide when purchased orbital power is worth using]
  Pain --> Product[Orbital power dispatch OS]
  Product --> Outcome[More profitable imaging and downlink from the same fleet]

Executive takeaways

• Star Catcher has pushed orbital power from science-project framing into a near-term procurement problem: it has raised a large Series A, demonstrated no-retrofit beaming, signed PPAs, and is aiming for an on-orbit demo.
• The beachhead buyer is real but narrow: EO and ISR operators already sell speed, revisit, and analytics, so incremental watts matter most when a surge task or onboard processing event has clear mission value.
• Competition is substitute-heavy rather than direct. Generic ground-software suites, automation startups, and vertically integrated operators all attack adjacent workflow pain, but none yet appears to own neutral power booking plus mission-yield settlement.
• The startup’s biggest risks are external: provider rollout timing, unclear beamed-power pricing/SLAs, and the slow trust-building required to sit inside flight-adjacent planning loops.

Market definition

Software that forecasts orbital power demand, books external beamed-power windows, reprioritizes missions, and settles the mission-yield impact for EO and ISR fleets. It sits between orbital power providers and generic mission-operations stacks rather than competing with the power hardware itself.

Customer and buyer

Primary users are mission-operations, planning, and chief-architect teams at EO/ISR constellation operators that already manage time-diverse tasking, battery constraints, and customer SLAs. The economic buyer is the operations or program leader who owns fleet uptime, margin on urgent collections, and customer delivery risk.

Buying triggers

• A fleet signs a pilot power-purchase agreement or demo partnership and needs a safe way to decide when external power should be consumed. [1][7][9]
• A defense or sovereign customer starts paying for rapid revisit and low-latency ISR, raising the value of each extra imaging or downlink window. [14][15][18][20]
• The operator starts layering onboard AI, SAR, or heavier analytics workloads onto satellites that are already power-constrained during peak operations. [3][12][18][24]

Willingness to pay

Public price sheets for beamed power are not disclosed, but willingness to pay is still visible: Star Catcher reports signed PPAs, BlackSky sells contract-backed assured access, Capella surfaces estimated tasking costs in workflow, and EO buyers increasingly buy bundled hardware, software, and commercial data. That implies budget exists when software can prove mission uplift rather than offer generic dashboard value. [1][7][15][17][20]

Category dynamics

Growth signal 7.9% broad EO CAGR; 15.9% EO smallsat CAGR

Validation signals

• Star Catcher reports seven PPAs, multiple government contracts, and a large qualified pipeline before live service.
• Payload reports sovereign customers increasingly buy bundled software and commercial data alongside hardware.
• BlackSky, Capella, and ICEYE all market rapid revisit, low latency, or fast delivery, implying meaningful value for extra power during urgent collections.
• Cognitive Space and NASA both describe manual satellite operations as slow, costly, and increasingly unfit for larger fleets.

Regulatory & technical constraints

• Novel commercial space activities still sit inside evolving U.S. supervision frameworks and treaty-based state responsibility.
• Smallsat electrical power systems remain mass- and volume-constrained, especially through eclipse periods and peak-duty operations.
• Ground and mission operations remain integration-heavy across APIs, command systems, and communications workflows.
• National-security use cases add security, sovereignty, and approval burdens beyond standard commercial EO workflows.

The market today is defined by substitutes: incumbent mission-ops suites, newer autonomy vendors, open-source or in-house command stacks, and vertically integrated EO operators that optimize their own fleets. A neutral multi-provider dispatch-and-settlement layer remains largely open.

Why incumbents do not win by default

• Broad mission-ops suites. They already handle C2, scheduling, and telemetry, but they do not appear designed around external power booking, beam-window arbitration, or revenue attribution.
• Automation specialists. AI-native ops vendors reduce manual planning, but their public positioning is constellation automation broadly, not power-market-specific orchestration.
• Vertical EO operators. Planet, BlackSky, Capella, and ICEYE all optimize revisit and delivery, but they sell imagery outcomes or sovereign capability first, not neutral software for third-party fleets.
• Open-source and in-house stacks. These remain credible because operators can assemble flexible control layers cheaply, but they push integration, safety, and economics modeling back onto the customer.

Orbital Power Dispatch OS sells a narrow workflow at the moment orbital power shifts from physics demo to procurement problem: helping EO constellation operators decide when purchased beamed power is worth using and proving whether that spend lifted mission yield. The first customer is a U.S. or European EO operator with roughly 8-30 satellites that is entering its first external-power pilot, surge-collection contract, or high-power onboard-inference program on standard solar-powered buses. The product starts as a dispatch and settlement layer that forecasts demand, books power windows, recommends operator-approved mission reprioritization, and ties purchased energy to incremental images, analytics jobs, or downlink output. Research supports the timing signal: Star Catcher has raised a large Series A, reports seven PPAs, claims no-retrofit compatibility, and plans a late-2026 demo, while EO and sovereign ISR buyers already pay for faster revisit and lower-latency delivery. The strategic choice is to start with EO fleets rather than broader mission-ops software because urgent imaging and downlink events create the clearest before-and-after ROI case for external power purchases. The market is still small and externally constrained, with an estimated $4.5M near-term SAM and the biggest risk tied to provider rollout timing and unclear commercial power pricing. Public evidence on actual beamed-power SLA and price terms remains missing, so the first 12 months must prove not just interest but live operator willingness to pay for dispatch software before power supply is routine.

Problem

• EO operators still manage battery limits, duty-cycle tradeoffs, and event-driven mission spikes with spreadsheets, fixed flight rules, and manual mission-ops calls, so they cannot consistently decide when extra orbital power would create positive mission ROI.
• If external power becomes purchasable without retrofit, the bottleneck moves from hardware scarcity to booking, prioritizing, and settling power use across fleets in a way operators and finance teams can trust.

Solution

• The MVP ingests ephemeris, battery state, payload duty cycles, imaging backlog, downlink windows, and provider power availability to recommend which satellite should buy power, when, and for which mission event.
• The same workflow generates booking requests, operator runbooks, and settlement reports that map purchased power to incremental output such as added images, faster delivery, or extra onboard inference completed.

Why we win

• The company owns a narrower control point than generic constellation software: neutral external-power dispatch and mission-yield settlement across operators and providers.
• If it wins early pilots, it compounds fleet-specific power-response curves, beam-window reliability data, and power-to-revenue attribution that adjacent mission-ops vendors and in-house stacks do not naturally capture.

Milestones

flowchart LR
  Wedge[EO power dispatch wedge] --> MVP[Shadow-mode dispatch and settlement MVP]
  MVP --> Proof[Paid pilots with mission-yield proof]
  Proof --> Expansion[Provider integrations and adjacent ISR or compute expansion]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least 5-10 beachhead EO or ISR fleets will evaluate external-power dispatch software within the next 24 months.
• Mission and operations leaders will pay for a third-party planning and settlement layer before live beaming supply is routine.
• At least one provider will expose booking rights, workflow hooks, or APIs that a neutral software layer can integrate with.
• Early pilots will demonstrate measurable mission-yield uplift or decision-speed improvement that exceeds software cost.
• Generic mission-ops vendors and in-house stacks will not close the external-power workflow gap fast enough to block a standalone entrant.

Open diligence questions

• What exact booking, pricing, and SLA primitives will early power providers expose to operators and software partners?
• Which EO fleets have both compatible buses and near-term mission events valuable enough to justify purchased power?
• How much integration work is required before operators trust recommendations inside flight-adjacent planning loops?
• Can the company prove event-level ROI without direct access to sensitive customer revenue or payload data?
• If live beaming slips into 2027 or later, does the product remain software or collapse into simulation-heavy services?

Model sanity

• Revenue engine. Base-case revenue comes from 2 paid pilots in Y1 compounding into 6 active fleet logos by Q1Y3 at about $220K blended annual revenue each by Y3.
• Must go right. Provider integrations and reusable fleet adapters must cut onboarding below 4 weeks so gross margin can climb toward the 70% target while logos grow.
• Model breaks if. If power-provider rollout slips by a quarter and blended ACV stays near $180K, cash cushion compresses toward the downside case before a seed raise.
• Next-round proof. A credible seed story is 5 paid fleet logos plus one provider-backed workflow by Q4Y2, showing this is becoming a repeatable control layer rather than bespoke services.

Scenarios

Sensitivity

flowchart LR
  DesignPartners --> PaidPilots
  PaidPilots --> AnnualContracts
  AnnualContracts --> Revenue
  Revenue --> GrossProfit
  GrossProfit --> Cash

Flags: The near-term SAM is only about 25 EO or ISR programs, so losing one lighthouse fleet or one provider partner materially changes the growth curve. · Y1 gross margin is intentionally low because early deployments still look partly like services work before reusable adapters exist. · Base case still exits Y3 slightly EBITDA negative, so the next raise depends on repeatability and proof of expansion, not on profitability alone. · Y3 ARPU assumes buyers accept a modest managed-power or provider-seat uplift even though public power-pricing benchmarks are still thin in the research corpus.

• Provider rollout slips. If orbital power demonstrations or commercial service availability slip beyond 2026, customers may defer buying workflow software. Mitigation: Start with simulation, pilot planning, and contract-readiness modules that deliver value before live power sessions are available.
• Integration friction. Mission-planning, flight-software, and provider-booking systems may be bespoke enough that onboarding each fleet is slow and expensive. Mitigation: Focus first on a narrow set of EO operators using common bus and mission-planning stacks, then productize adapters from those deployments.
• Narrow initial market. The first set of fleets able and willing to buy external orbital power may be small, creating customer concentration risk. Mitigation: Sell into adjacent defense payload programs and emerging power providers, then expand from EO into comms and orbital-compute operators as supply grows.