Subscribe
Share
Share
Embed
The money, missions, and power shaping space. Space Stakes is a daily briefing on the business of the new space race — launches, contracts, constellations, and the capital behind them. Every episode cuts through the industry's hype: signed contracts vs. paper constellations, funded orders vs. "up to" ceilings, launch dates vs. track records. Who pays, who profits, and who actually delivers — told so both aerospace insiders and curious newcomers finish feeling it was made for them. Space Stakes is an AI-voiced podcast, created and built by a real human, Brian Lampert. Nothing on this show is financial advice.
Also from Brian Lampert: Quickly Quantum and Concrete Compute.
7,500 contractor positions: if NASA moves them into civil service, who does the work, and what does the taxpayer actually get? Before that, Europe has approved a collective response to threats against satellites, and a European rocket test has made progress while remaining firmly on the ground. Welcome back to Space Stakes, your daily brief on the business of space. It's Wednesday, October 7, 2026. Let's get into it.
Europe has opened the door to a collective response when a member state's satellites or related ground infrastructure face a threat. Breaking Defense reports that the European Union's 27 member states approved a Council decision allowing a response through political, economic or even military means. The decision, dated September 23, is Council Decision 2026/2195. The mechanism builds on the EU's Space Threat Response Architecture, created in 2021 to address threats to jointly owned or operated systems such as Galileo and Copernicus. The new decision extends the possible response to threats to EU or member-state security even when the affected assets aren't directly linked to EU space systems. That can include cyberattacks, espionage, supply-chain disruptions and problems affecting ground stations. What does that mean in practice? Clayton Swope, deputy director of the Center for Strategic and International Studies' Aerospace Security Project, called the decision an "enabling document." Breaking Defense reported Swope saying it does not add any new military capabilities to EU members arsenals, nor does it guarantee the EU will have the political will to actually go all the way to military action in response to threats or low-level attacks. Michael Gleason of The Aerospace Corporation's Center for Space Policy and Strategy said the EU could decide to help if a member state asks. The distinction matters: a shared process can make a response possible, but the decision doesn't itself supply the tools or ensure that governments will use them. As @eu_eeas posted on X: "New rules protect EU systems and Member States' satellites and space services, with responses from diplomatic statements to sanctions." And the unresolved test is deterrence. Swope asked whether the unified approach can raise the consequences enough to change an adversary's behavior, particularly Russia's. That's the hard measure for a framework whose next step depends on political choices.
Themis has completed a second wet dress rehearsal, a ground test that checks the rocket and its support systems under launch-like conditions. European Spaceflight reports that ArianeGroup and SSC conducted the rehearsal at Esrange in Sweden, with the European Space Agency announcing the completion on October 7. The test itself took place on September 29. The demonstrator was filled with liquid nitrogen, not rocket propellant. Cooled to around minus 200 degrees Celsius, the nitrogen let teams test the vehicle and ground infrastructure at similar cryogenic temperatures and pressures, without the added risk of loading propellant. This second rehearsal also tested parts of the automated ground system intended to support reusable operations. Here's what that system is meant to do after a test: once Themis touches down, robotic equipment is expected to locate the vehicle, connect to it and drain remaining fuel and oxidiser, while people stay at a safe distance. That's a planned capability, not something this rehearsal demonstrated in flight. There's another step before an engine firing. ESA previously said a hot-fire test of Themis's Prometheus engine would follow a full wet dress rehearsal using liquid oxygen and liquid methane. So, unless the test sequence has since changed, at least one further rehearsal is expected before teams progress to hot fire. The SALTO consortium says teams are defining a window for the next test. During the first flight, Themis is expected to climb to an altitude of up to 100 metres, then descend and attempt a vertical landing. A successful rehearsal is useful progress; the next meaningful evidence is a completed test sequence and a hop.
Germany is the next market Dawn Aerospace wants to serve, with an expansion plan that's still taking shape. SpaceWatch.GLOBAL reports that the company plans to establish Dawn Aerospace Deutschland GmbH to support Germany's defense and national security space sectors. Dawn says the expansion is intended to provide a local supply of its propulsion systems. The company is recruiting a Head of Defence Sales for Germany and plans to open a physical office in either Bremen or Düsseldorf after that appointment. Those are plans, and the location has not yet been selected in the account. The backdrop is a statement by Germany's Defence Minister Boris Pistorius in 2025 that the country would invest €35 billion in space-related defense capabilities through 2030. Dawn argues that new surveillance and communications constellations will need propulsion systems, and says existing domestic suppliers lack the scale for high-volume defense procurement. That's Dawn's description of the market, not an independent assessment in this article. The company says more than 50 of its non-toxic propulsion systems are operating in orbit and that its manufacturing pipeline produces dozens of turnkey systems annually. Its systems are designed for satellite orbital maneuvering and station-keeping. Dawn is also developing on-orbit refueling and reusability capabilities; those remain in development. Chief Revenue Officer Jeroen Wink said the rollout is designed to engage with German Space Command and defense primes. Chief Executive Officer Stefan Powell argued that government partners require scale and flight heritage. The commercial question for you is what turns this expansion into a customer relationship: an office and a sales hire create a local presence, while contracts and delivered systems would show whether the demand becomes business. That question leads to the larger NASA story—who performs publicly funded space work, and where accountability sits.
NASA's workforce is also procurement strategy: moving 7,500 contractor positions into civil service changes who works for the agency and how the agency holds responsibility for mission-critical work. Ars Technica reports that NASA Administrator Jared Isaacman is pursuing the shift as part of a "workforce initiative," with the stated goal of rebuilding what he calls "core competencies." The article does give a useful history for understanding the argument. Gerry Griffin, a former NASA flight director and Johnson Space Center director, described how responsibility and teamwork worked during Apollo. As flight director, Griffin led several lunar landings and helped bring the Apollo 13 crew safely back to Earth. He credited the trust and communication among people in Mission Control, including John Aaron and Jerry Carr, with making a difference. Ars Technica reported that the rocket and spacecraft survived, going on to complete the second lunar landing. Griffin's point is about the relationship between work and responsibility. During the Apollo era, he said, NASA brought in contractors to supplement its workforce, while Mission Control positions remained NASA jobs. The agency retained responsibility for mission outcomes. Later, Griffin said, contractor roles expanded into Mission Control. "Midway through the space shuttle era, I was surprised to find that a lot of the jobs in Mission Control had gone to contractors," he said. The article is careful not to treat contractors as the problem. Griffin said they play a critical role by extending NASA's expertise for subsystems built for the agency. His concern is that critical work was outsourced over time, often as a way to increase headcount without raising NASA's civil-service count. That distinction is important for a newcomer: contractors are employees of outside companies working for NASA under contracts; civil servants are federal employees. Changing the employer may change how expertise is retained and how teams are organized, but the reported plan alone doesn't tell us whether it lowers costs or improves schedules. So what does the taxpayer get? The reporting identifies the proposed shift—7,500 roles—and the stated goal of rebuilding core competencies. It doesn't identify the affected centers or contract vehicles, or provide figures that would let us judge price against capability. Those details matter because a workforce change can move responsibility and costs between NASA and contractors without, by itself, showing what mission performance improves. The mechanism is easier to see through Griffin's example. In a time-critical mission-control situation, people need to communicate and trust one another, and the agency remains responsible for the mission. Griffin's account supports the value he places on integrated teams. It doesn't establish that every role now performed by a contractor should become a civil-service job.
The central question is whether bringing these jobs inside NASA rebuilds expertise that the agency needs to own—or mainly changes the employment category attached to the work. Ars Technica gives us the number and the rationale, but not enough detail to settle that question. There's no cost comparison or schedule result in the account, and no list of the centers and contract vehicles affected. So we can describe the proposed change; we can't responsibly call it a savings plan or say it will speed a mission. Griffin's testimony gives the proposal a serious operational case. Griffin's argument is that NASA's responsibility for mission success makes in-house expertise especially valuable in roles where coordinated decisions matter. That's a compelling principle. His account also recognizes that contractors contribute critical expertise, including on subsystems built for the space agency. Here's my read: moving 7,500 roles into civil service is credible as a strategy only if NASA can show which capabilities it needs to retain, what those roles will cost, and how the change improves the work. A headcount shift on its own doesn't answer those questions. The proof should be specific: which roles move, what capability NASA gains, and how the agency will assess whether the new arrangement serves missions better. There's a real management trade here. Contractors can extend an agency's workforce; civil servants can keep knowledge and responsibility within the agency. But that's analysis, not a measured outcome in this account. The best case for the initiative is that NASA needs durable expertise in jobs central to mission decisions. The case against an unexamined shift is that moving people onto the federal payroll doesn't automatically make a team more effective. The reporting gives us Griffin's experience and Isaacman's stated objective, not evidence that the proposed change has already delivered a result. And accountability is the point worth holding onto. Griffin describes NASA as ultimately responsible for mission outcomes even when contractors contribute to the work. That responsibility doesn't disappear when NASA buys expertise from outside, and changing the employer doesn't prove that accountability becomes clearer. I'd want the public to see the work being brought in, the cost, and how NASA will judge the outcome. My standard for a major public workforce decision is the same one I'd apply to a large contract: explain what the public gets and how the agency will know it got it. This also changes the emphasis from an earlier NASA debate about partnerships. The prior question was what NASA should expect from partners; this account puts the focus on who performs the agency's own work and where expertise sits. The connection is a management question, not proof that one policy resolves the other. Time for the Hype Check. My substance rating is 5 out of 10: the 7,500-role goal and the core-competencies rationale are concrete, but the account doesn't provide cost, affected contract details or evidence of improved performance. If NASA identifies the affected centers and contract vehicles, that will tell us whether this is a targeted capability shift or a broad change in staffing; those specifics are the next test of the proposal.
If you value a space-business show that follows the work as closely as the hardware, follow today's episode wherever you listen. This has been Space Stakes, an AI-voiced podcast, created and built by a real human using today's cutting-edge technology. Nothing you heard on this show is financial advice. I'm Brian Lampert, and I'll catch you all tomorrow — take care!
Watching on YouTube? Hit subscribe, and tomorrow's briefing will be waiting for you. I also host Quickly Quantum: a daily quantum computing briefing you don't need a physics degree to follow. The breakthroughs, the funding rounds, and how much substance is really under each claim. Find it wherever you get your podcasts.