Subscribe
Share
Share
Embed
Chapters
00:00 Today's headlines
01:04 SpaceX FCC authorization for satellites
02:49 SpaceX to acquire low-band spectrum
04:32 NASA proposal on contractor positions
06:07 Kratos space-intelligence awards
07:56 Amazon's 1,000th Leo satellite built
09:26 FAA scoping for Starship operations
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.
Can a satellite phone service become a real business when regulatory permission, spectrum and spacecraft all have to line up? This week, SpaceX got an FCC authorization for 15,000 direct-to-device satellites, then agreed to acquire nationwide low-band spectrum for Starlink Mobile. Those are two different steps in a plan to connect ordinary phones from space, and neither one means the service is already operating. Before we get to the details, NASA proposed moving 7,500 contractor positions into the civil service, Kratos reported more than $100 million in space-intelligence contracts, Amazon built its 1,000th Leo satellite, and the FAA opened public scoping for a possible Starship launch and landing program at Cape Canaveral. Welcome back to Space Stakes, your daily brief on the business of space. It's Saturday, October 10, 2026. This is the week in review: six stories about who controls the infrastructure, who pays for it, and what has actually moved from plan toward delivery. Let's get into it.
On Thursday, October 8, we looked at the FCC's authorization for SpaceX to deploy 15,000 satellites for direct-to-device service. Via Satellite reported that the authorization covers Mobile Satellite Service spectrum and supplemental coverage from space in the United States, with related service outside the country. In plain English, the goal is for satellites to help connect phones in places where ordinary cellular coverage is limited. The FCC also deferred action on the 2020–2025 megahertz band and heavy federal-use bands. That distinction matters: approval for this deployment is a substantial regulatory step, while some requested spectrum decisions remain unresolved. So what changed the shape of the story this week? The next day brought a separate deal: SpaceX agreed to acquire nationwide low-band spectrum from Grain, subject to FCC approval. That's a second piece of the service plan, not evidence that customers can use it today. Put the two developments together and the ambition becomes easier to see: satellites and spectrum are being assembled into a mobile offering. But authorization is not deployment, and a spectrum grant by itself doesn't establish that phones will connect reliably in daily use. You don't need to know the radio engineering to see the business test. SpaceX has to build and launch the satellites, and the service has to work with the devices people actually carry. My read: this week strengthened the case that SpaceX wants a direct role in mobile service, not only a role as a satellite provider to existing carriers. The hard proof is still operational service that works for customers. For you, the payoff would be a phone that can reach a network where towers don't; the practical question is whether that connection has enough capacity to be useful. The authorization gives the project room to move, and the deferred bands leave part of the spectrum picture open.
Friday, October 9, we covered the second half of SpaceX's mobile-spectrum push: its agreement where SpaceX and Grain Management said SpaceX will acquire 14 megahertz of paired spectrum in the 800 MHz band. Via Satellite reported that the deal is subject to FCC approval and that its financial terms were not disclosed. The practical distinction is frequency: low-band spectrum can help coverage reach indoors, while the story describes SpaceX's 2 gigahertz spectrum as a capacity layer. Capacity is how much traffic a network can carry; coverage is where it can reach. Those layers solve different problems for a phone user. Why does this matter alongside the FCC's satellite authorization? The satellite approval supplies a route to direct-to-device service, and this proposed spectrum acquisition would add a nationwide low-band resource. The deal is still pending, so it hasn't transferred yet. That stage matters when you're trying to judge what a company has secured versus what it plans to use. The price also remains undisclosed. For a public-interest read, the question is what the FCC will require when it considers the transfer, and how the decision affects competition. The reporting gives us the deal's spectrum amount, coverage and capacity rationale, and approval condition; it doesn't provide the terms of the transaction. So there's no honest way to price the move from the information here. My read is that spectrum is the quiet asset behind the eye-catching satellite number. A spacecraft can be visible overhead and still need the right frequencies and regulatory permissions to connect your phone. SpaceX's agreement adds a new piece to that puzzle, but FCC approval and working service remain separate milestones. The next important development is the agency's decision on the transfer, because that determines whether this particular piece of the plan can proceed.
On Wednesday, October 7, we revisited NASA's proposal to move 7,500 contractor positions into the civil service, a reversal of decades of contracting-out that accelerated midway through the Shuttle era. Ars Technica's headline asks the right question: why bring those jobs in-house? The proposed change is about who does NASA's work, and how the agency organizes responsibility for it. It is still a proposal. That word carries real weight here: it doesn't establish that the positions have transferred, or tell us what the transition would cost or when it would happen. What would a taxpayer get from the change? The reporting gives the scale—7,500 positions—and the direction of travel, but the case depends on whether bringing roles into the civil service improves NASA's ability to manage and retain important work at a cost the public can assess. Those answers matter more than the org chart alone. A contractor arrangement and a civil-service role aren't interchangeable labels; they shape how the agency hires and manages its workforce. But a change in employment status doesn't prove better mission performance by itself. My read is that the proposal puts a legitimate management question on the table: which capabilities should NASA keep inside the agency? To evaluate it fairly, the public needs a cost comparison and an implementation schedule, alongside a clear account of what work the proposed positions would perform. Until then, this is a significant proposed shift, not a demonstrated result. The plan may have a strong rationale, but the test is whether it produces accountable work and better mission execution without obscuring the cost.
Tuesday, October 6, we covered Kratos Defense & Security Solutions and its reported space-intelligence awards. Via Satellite reported that Kratos received multiple contracts worth more than $100 million combined to provide space-intelligence data, prototype mission applications and cyber capabilities. The company's KnownSpace radio-frequency collection network and Recon+ terminals are part of the work described. Radio-frequency collection means gathering signals; the mission applications are intended to make that data useful to customers. That's the concrete capability in the announcement: data collection and processing, alongside prototype applications and cyber work. The word "prototype" matters, because it describes work aimed at developing or demonstrating applications, not a claim that every capability is already a mature operational service. The company did not disclose specific contracts, customers or periods of performance. That leaves an important gap for anyone trying to understand how the combined value maps to specific government needs. Which customer receives which capability, over what period, and on what terms? The reported total tells us the awards have meaningful scale, while the undisclosed details limit how precisely we can judge delivery or competition. The story also raises the standard question for public contracts: what does the taxpayer receive, and when? The information here identifies the broad types of work, but doesn't give the contract-level schedule or terms needed to assess performance against a price. My read is that space intelligence becomes economically interesting when collected signals turn into useful decisions for the customer. Kratos's reported work is aimed at that link, from RF collection to mission applications and cyber capabilities. The next useful evidence would be specifics on the individual awards and their performance periods, so the announced total can be matched to delivered work.
Friday, October 9, we also covered a hardware milestone for Amazon: the company manufactured its 1,000th Leo satellite at its factory in Kirkland, Washington. Ars Technica reported in its article that Amazon was weeks away from first commercial service, with an upcoming Vulcan return-to-flight and another Vulcan this year carrying Leo spacecraft. That's a striking point in the buildout, and the manufacturing count is a real milestone. But a satellite built on Earth isn't automatically a satellite in orbit, and a planned service debut isn't the same as customers already receiving service. Amazon's stated timing depends on launches. Why should a broadband customer care about another constellation? Because a second large-scale satellite internet system would give the market another potential provider. The business test starts after the launch hardware is built: spacecraft have to reach orbit, the service has to begin, and customers have to receive a connection that works. The story supplies a clear manufacturing achievement and a near-term commercial-service expectation, but the timing remains company-stated and launch-dependent. It doesn't give the number of satellites that will be operational at service entry, so the count built can't be treated as the same thing as working network capacity. My read is that this is a meaningful step toward competition, and it deserves to be celebrated as a production milestone. The stronger commercial proof comes when the spacecraft launch and the service begins. For you, the prospect is another choice for internet access; for Amazon, the challenge is converting a factory achievement into a functioning service. The launch sequence is the next test of that promise.
Monday, October 5, we covered the FAA's environmental review process for proposed SpaceX Starship-Super Heavy operations at Space Launch Complex 37 at Cape Canaveral. The FAA opened public scoping through October 14, 2026, on a Supplemental Environmental Impact Statement, a review of the potential effects of the proposed operations. The scope covers up to 76 launches and 152 landings per year. Those are proposed annual limits under review, not approved operating rates. The scoping period is an opportunity for the public to identify issues the environmental review should examine. Why does this matter for the launch business? A proposed cadence on that scale would be consequential if it were approved and achieved, but reaching it requires more than a number in a review document. The FAA still has to complete the environmental review, and the proposal also requires a modified vehicle operator license. That's the practical distinction between describing a possible future program and being cleared to carry it out. The next decision is not simply whether a large number sounds plausible; the review has to assess the proposed operations and the requirements attached to them. My read is that the scoping process is a meaningful early gate for Starship operations at this site. It gives the agency a chance to define what needs analysis before any conclusion about the proposed scale. For the public, the important questions are what the review requires and what the resulting license permits. The October 14, 2026, deadline for scoping comments is the next concrete marker: it will show what issues are raised for the FAA to consider, not whether the proposed launch rate is approved.
If you want a clear view of the business behind the rockets, follow Space Stakes 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 Concrete Compute: a daily briefing on the AI buildout. The datacenters, the megawatts, and who actually pays for them. Find it wherever you get your podcasts.