Eclipse Space satellite platforms now span three designs: CitraSat for direct-to-device communications, SliceSat for broadband and SurgeSat for in-orbit computing. The September 9 unveiling moves the startup from a general constellation promise to named architectures with sharply different power and payload demands.
Key takeaways
- CitraSat targets phones without a dedicated user terminal.
- SliceSat is built around high-throughput broadband links.
- SurgeSat scales solar generation to 100 kilowatts for orbital compute.
- The designs are announced platforms, not proof of an operating constellation.
What Eclipse Space satellite platforms change
Everyone else is listing three spacecraft; we are explaining why the product split matters. Direct-to-device service, broadband and orbital computing impose different antenna, power, thermal and business requirements. Treating them as separate platforms makes the roadmap easier to examine, but it also exposes how much engineering and customer validation remains.
CitraSat is the near-term priority. Eclipse says it includes an S-band phased-array antenna, multi-gigabit E-band backhaul, V-band links between satellites and dual solar arrays capable of six kilowatts at peak. Payload Space reported that chief executive Derek Huerta expects the company to learn from this direct-to-device platform before pushing the other two markets.
Three products, three different bottlenecks
SliceSat raises peak solar generation to eight kilowatts and combines Ku-band user links with V- and E-band backhaul. The commercial question is not whether the specifications sound fast. It is whether the complete system can deliver capacity, coverage, spectrum coordination and terminal economics that customers can operate.
SurgeSat is the most ambitious. Eclipse describes 100 kilowatts of peak solar generation and a 400-square-metre radiator intended to reject heat from computing payloads. In space, cooling is not a matter of blowing air through a server. Heat must be moved to radiator surfaces and emitted, while power generation, shielding and reliable data movement all compete for mass and cost.
| Platform | Target workload | Peak solar claim |
|---|---|---|
| CitraSat | Direct-to-device communications | 6 kW |
| SliceSat | High-throughput broadband | 8 kW |
| SurgeSat | In-orbit computing | 100 kW |
Why the flat architecture matters
All three designs are intended to fold flat inside a launch fairing. Packing efficiency can reduce the number of launches needed for a constellation, but deployment reliability becomes a key test. A compact launch configuration is valuable only if arrays, antennas and radiators deploy predictably after separation.
Eclipse also pitches an end-to-end system: spacecraft, ground infrastructure, user terminals and launch integration. Customers would own their constellations rather than rent capacity from a single shared network. That sovereignty argument may appeal to national operators and commercial groups that want control over coverage, data and upgrade schedules.
What is still unproven
The company’s first demonstration mission has moved to 2028, according to Payload Space. That means buyers should separate a named product architecture from flight heritage. The next useful milestones are completed design reviews, contracted manufacturing, spectrum progress, launch agreements and hardware tests under thermal-vacuum and radiation conditions.
Cost is another open variable. Eclipse has not made a public price list, delivery cadence or service-level commitment for a full network. Customers must model launch replacement, ground stations, insurance, operations staffing and replenishment rather than compare satellite power figures in isolation.
The launch sits beside wider changes in commercial space. Our coverage of space-data investment and launch-market financing shows why a complete operating system must be evaluated as infrastructure, not a single spacecraft.
What customers should verify next
First, confirm which specifications are locked and which remain design targets. Second, ask who manufactures each subsystem and how supply constraints affect schedule. Third, require evidence for deployment, link performance, thermal control and fault recovery. Finally, compare outright ownership with leasing capacity from an existing constellation.
Why sequence matters
Eclipse is prioritising CitraSat, so the other platforms should not be read as simultaneous commercial availability. A staged roadmap can reduce risk because lessons from communications hardware, ground operations and suppliers may carry forward. It can also push the most ambitious orbital-compute timeline further out. Customers should attach decisions to contracted milestones, not a shared visual family.
Frequently asked questions
What are the Eclipse Space satellite platforms?
They are CitraSat for direct-to-device service, SliceSat for broadband and SurgeSat for orbital computing.
Are the satellites operating now?
No. They are announced platforms; independent reporting says the first demonstration mission is planned for 2028.
Why does SurgeSat need a large radiator?
Computing produces heat, and a spacecraft must radiate that heat into space while maintaining safe component temperatures.
Sources
Primary specifications come from Eclipse’s CitraSat, SliceSat and SurgeSat pages. Direct-event reporting was checked against Payload Space and Via Satellite.
Get the day’s top stories in your inbox
One concise email. No spam, unsubscribe anytime.
