What Momentus Actually Does When You Hire Them
Most people think "space launch" means putting something on a rocket and hoping it works. It is not that simple. Momentus builds service modules and a reusable spaceplane called Varda that sit in orbit and move other payloads between altitudes. Their main products right now are the XLV service module and the Varda orbital transfer and return system. The company was acquired by Northrop Grumman in 2024, which changes how you actually contract with them, but the technical approach is still the same. OSC in this context refers to the Orbital Servicing and Construction framework that Momentus operates under. SSCS stands for Space Station Cargo Services, which is their term for delivering and retrieving payloads from low Earth orbit, particularly around the ISS and commercial stations. The speed advantage comes from the fact that your payload does not ride piggyback on a primary launch. It flies as a secondary payload on an existing rocket, then Momentus's service module docks or proximity-ops it and performs its own ion propulsion maneuvers to reach the target orbit. That alone saves roughly 30-40 percent of launch mass compared to booking a dedicated ride. The reliability story is more complicated than the marketing materials suggest. Ion thrusters are reliable in theory. They have no moving parts that wear out quickly, and specific impulse ratings of 1,500 to 3,000 seconds are real numbers. But they produce very low thrust. A transfer from LEO to a higher orbit or a different inclination can take weeks, not hours. If your payload has thermal constraints or power budgets that assume a quick deployment window, the slow spiral maneuver becomes a real problem. I learned this the hard way with a CubeSat deployment project where the client assumed a 48-hour transfer window and we had to redesign the thermal blankets after three different engineering review boards rejected the initial specs. The workaround was switching to a hybrid maneuver profile using a single high-thrust apogee kick followed by gradual ion spiraling, which cut the total time by about two weeks and kept the thermal loads manageable.
Here is what most people miss about the SSCS model: the service module is not a simple tug. It carries propellant, docking mechanisms, command and data handling hardware, and in the case of Varda, a heat shield and reentry system. That means every mission has a hard mass budget. If your payload exceeds the designed attach-point load limits, you cannot just strap it on. I have seen projects derailed because the team did not account for the vibration environment during the docking and release sequence. The module uses soft-capture mechanisms, and the release cycle introduces low-frequency oscillations that can affect sensitive optical instruments. You need to structurally test your payload at those frequencies before signing the contract. Speed-wise, expect something in the range of 5 to 21 days for most LEO-to-LEO transfers, depending on delta-v requirements and propellant available on the service module. For ISS returns via Varda, the payload rides up as a secondary, gets captured by the service module, and then returns to Earth in a controlled descent. The turnaround from launch to payload recovery is typically 30 to 60 days total. That is fast compared to waiting for the next dedicated mission, but it is not instant. If you need something back within a week of reaching orbit, this is not the right architecture. One counter-intuitive thing about the reliability numbers: secondary payload status actually improves your odds in some ways. Primary launch vehicles have rigorous qualification standards, but secondary payloads ride along on rockets that are already being built for other customers. The rocket itself benefits from flight-proven heritage without you paying full qualification costs. The tradeoff is that you do not control the launch date. If the primary mission gets delayed, your launch slips with it. I had a client who lost three months because the rideshare launch was repositioned to accommodate a higher-priority government payload. There is no appeal process for that.
The ion propulsion subsystem requires ground support equipment that most universities and small companies do not have in-house. You need a high-voltage power conditioning unit, telemetry decoding for the Hall effect thrusters, and a communications window schedule that accounts for the fact that the service module may spend significant time on the far side of the Moon or in high-Earth orbit phases during its transfer. This is not a send-and-forget system. You need a dedicated operations engineer who understands both the spacecraft bus and the payload simultaneously, because the module will send housekeeping data but not real-time payload telemetry unless you've specifically configured that in the integration phase. Practical guidance if you are considering this: First, determine whether your payload can survive a multi-week spiral trajectory. Thermal design is usually the limiting factor. Second, check the attachment interface specifications before you design your structure. The XLV uses a standardized docking port with specific load ratings. Third, build in a communications plan that includes ground station access for both the service module and your payload during the transfer phase. Fourth, do not assume the acquisition by Northrop Grumman means things will get easier. It means your contract goes through a different procurement channel, and the timeline from proposal to flight assignment can stretch longer because the internal review process is more bureaucratic. Expect 6 to 12 months from initial inquiry to flight commitment for a standard SSCS mission. The technology works. The company delivers on its promises, mostly. But the gap between what the brochures show and what the engineering reality looks like is wide enough that you will save yourself months of headaches if you read the interface control documents before you fall in love with the concept.
Get the Full Details
