ISS Laptops Get a Long-Overdue Upgrade — And the Real Story Is What That Reveals About Critical Infrastructure

When NASA announces that astronauts aboard the International Space Station are getting new computers, it's easy to file it under "cool space news" and move on. But the ISS laptop upgrade story is actually a window into one of the most underappreciated challenges in modern technology: how do you maintain, upgrade, and secure mission-critical computing infrastructure in environments where failure is not an option?

The crew of Expedition 74 is currently working through a phased computer upgrade, according to NASA via The Verge, replacing network servers first and then activating new HP ZBook Fury G9 laptops. It sounds mundane. It is anything but.

Why the ISS Laptops Upgrade Is More Complicated Than Your Office IT Refresh

Most corporate IT departments treat a laptop refresh as a logistics problem: order the machines, image them, ship them, swap them out over a weekend. Done. The ISS has none of those luxuries.

Every kilogram launched to the station costs an estimated $10,000 to $54,000 depending on the launch vehicle — a figure that has declined significantly with commercial providers like SpaceX, but remains orders of magnitude higher than terrestrial shipping. The HP ZBook Fury G9 is not a light machine; it's a workstation-class laptop designed for demanding professional workloads, weighing in at roughly 2.4 kg. Multiply that by however many units are heading to the station, and you're looking at a non-trivial payload cost before you've even considered the software configuration, testing, and crew training required.

Then there's the environment itself. The ISS operates in low Earth orbit at altitudes between 400 and 420 kilometers, where equipment is exposed to radiation levels roughly ten times higher than on the Earth's surface. Consumer-grade electronics degrade faster. Storage media can be corrupted by cosmic ray events. Thermal cycling — the station experiences roughly 16 sunrises and sunsets per day — stresses hardware in ways that no terrestrial stress test fully replicates.

The fact that NASA chose the HP ZBook Fury G9 — a commercial off-the-shelf workstation laptop rather than a fully custom space-hardened system — is itself a strategic decision worth examining. It suggests NASA is increasingly comfortable with COTS (Commercial Off-The-Shelf) hardware in non-life-critical computing roles aboard the station, trading some radiation resilience for cost efficiency and the ability to source replacement units quickly.

The Phased Rollout: Why Servers Come Before Laptops

The sequencing that NASA described — replace network servers first, then activate the new laptops — isn't arbitrary. It reflects a fundamental principle of infrastructure management that applies equally to data centers, financial trading floors, and orbital platforms: the network layer must be stable before you migrate endpoints.

The ISS's internal network is the backbone through which crew members communicate with Mission Control in Houston, run scientific experiments, monitor life support telemetry, and yes, send the occasional email home. Upgrading the servers first ensures that the new laptops, once activated, are connecting to a validated, tested network environment. Running new endpoints on old, potentially incompatible server infrastructure is a recipe for the kind of cascading failures that are merely embarrassing on Earth and potentially dangerous in orbit.

This sequencing discipline is something that enterprise IT organizations frequently get wrong. The pressure to show visible progress — new shiny laptops on desks — often leads organizations to rush endpoint deployment before backend infrastructure is ready. NASA's methodical approach here is worth noting as a model.

The crew met on Friday to review plans to "first replace network servers then activate their new laptops."

— NASA, via The Verge

What "Mission-Critical" Actually Means in 2026

Here's where the ISS laptop story connects to a broader conversation happening across industries right now.

We are in the middle of a global reckoning with what "mission-critical infrastructure" means in an era of AI integration, supply chain fragility, and accelerating hardware cycles. The ISS upgrade is a clean, extreme-case illustration of tensions that are playing out in far less exotic settings.

Consider the education sector. Missouri S&T recently reported that declining international student applications — partly attributed to visa problems and the disruption caused by AI tools — are creating enrollment and funding pressures. Mississippi College School of Law has gone further, making AI education mandatory for all students, becoming one of the first law schools in the nation to do so. These institutions are grappling with the same underlying question the ISS upgrade surfaces: how do you maintain operational continuity while integrating new technology that changes the fundamental nature of the work?

For law students, the answer appears to be: make AI literacy non-negotiable, because the tools are already embedded in legal practice whether institutions acknowledge it or not. For NASA, the answer is: upgrade methodically, validate at every layer, and never let the desire for newer hardware outpace the stability of the systems that hardware depends on.

a rack of servers in a server room

Photo by Kevin Ache on Unsplash

The Hidden Supply Chain Story Behind the HP ZBook Fury G9

The choice of HP's ZBook Fury G9 as the replacement platform deserves more scrutiny than it has received. HP's ZBook line is aimed at creative professionals and engineers — architects, video editors, data scientists — who need workstation-class GPU and CPU performance in a portable form factor. It is not, on its face, an obvious choice for space operations.

But that's precisely the point. As scientific computing aboard the ISS has evolved — from basic telemetry monitoring to running complex simulations, processing high-resolution imagery from Earth observation instruments, and supporting increasingly sophisticated experiments in microgravity biology and materials science — the computational demands on crew workstations have grown substantially.

The ZBook Fury G9 ships with Intel's 12th-generation Core HX processors and supports NVIDIA discrete GPUs, configurations that would have been considered supercomputer-class hardware just a decade ago. For NASA to be deploying this level of compute to the ISS suggests that the nature of work being done on those machines has changed significantly.

There's also a supply chain resilience argument. By standardizing on a commercial platform with broad enterprise adoption, NASA gains access to a supply chain that is vastly more robust than any custom-developed space hardware program. If a unit fails, a replacement can, in principle, be sourced and manifested on the next resupply mission without a multi-year procurement cycle.

This mirrors a broader trend I've been tracking across infrastructure-intensive industries: the shift from bespoke, purpose-built systems toward hardened commercial platforms. It's the same logic driving Amazon's bet on managed electric freight services through Einride rather than building a proprietary truck fleet — a dynamic I analyzed in depth in Amazon's Einride Bet: What Electric Trucks Reveal About the Everything Store's Infrastructure Gamble. When commercial solutions reach sufficient maturity and reliability, the cost and risk calculus of custom development shifts decisively.

The Security Dimension No One Is Talking About

Here is the angle that the celebratory "astronauts get new laptops" coverage almost universally misses: cybersecurity in space is a genuinely unsolved problem, and every hardware upgrade cycle is also a security event.

The ISS is connected to Earth via a complex network of ground stations and relay satellites. It transmits and receives data continuously. That connectivity is a vulnerability surface. In 2008, a NASA laptop infected with the Gammima.AG worm was carried aboard the ISS, demonstrating that even orbital platforms are not immune to terrestrial cybersecurity failures. The NASA Office of Inspector General has repeatedly flagged cybersecurity as a persistent challenge for the agency's IT infrastructure.

When you replace laptops on the ISS, you are not just swapping hardware. You are introducing new firmware, new operating system configurations, new potential attack surfaces. The validation and hardening process for those machines before they leave Earth is extraordinarily rigorous — but rigorous is not the same as perfect.

This connects directly to a broader concern I've written about regarding AI tools being integrated into infrastructure management: the governance gap between deployment speed and security validation. As I noted in an earlier analysis of AI-driven cloud encryption decisions, the pattern of deploying technology before establishing adequate oversight frameworks is one of the most consistent failure modes in modern IT. The ISS upgrade, done right, is a counter-example — a case study in what disciplined, sequenced deployment actually looks like. You can read more about the governance dimension of infrastructure security in AI Tools Are Now Deciding How Your Cloud Encrypts Data — And No One Signed Off on That.

Lessons for Enterprise IT Professionals

The ISS laptop refresh is, at its core, an extreme stress test of principles that apply to any organization managing critical computing infrastructure. Here's what I think is genuinely actionable from this story:

1. Sequence Your Upgrades Like Your Life Depends on It

NASA's decision to upgrade servers before activating new laptops isn't bureaucratic caution — it's engineering discipline. In any infrastructure refresh, validate the foundation before you build on it. The number of enterprise IT disasters that trace back to endpoint deployments on unvalidated backend infrastructure is depressingly high.

2. COTS Hardware Is a Strategic Choice, Not a Compromise

Choosing the HP ZBook Fury G9 for the ISS signals that commercial hardware has matured to the point where it can meet demanding operational requirements. For most organizations, the residual advantages of custom-built systems rarely justify the cost and procurement complexity. The question is whether your validation and hardening processes are rigorous enough to compensate for the loss of bespoke control.

3. Every Hardware Refresh Is a Security Event

Treat it that way. New firmware, new OS versions, new drivers — each represents a changed attack surface. The organizations that get this right build security review into the procurement and deployment process, not as an afterthought after the machines are already on desks (or in orbit).

4. Operational Continuity Requires Explicit Planning

The ISS crew didn't just receive new laptops one day. They met to review the upgrade plan, understood the sequencing, and were prepared for the transition. Crew training is part of the deployment. This is basic change management, but it's remarkable how often it's skipped in terrestrial IT refreshes.

The Bigger Picture: Infrastructure at the Edge of Human Capability

There's something worth sitting with in the image of astronauts 420 kilometers above Earth, reviewing upgrade plans for their laptops before swapping out network servers. It's simultaneously mundane and extraordinary.

The ISS has been continuously inhabited since November 2, 2000 — over 25 years of unbroken human presence in orbit. That longevity is not an accident. It is the product of relentless, unglamorous maintenance work: replacing components before they fail, upgrading systems before they become obsolete, and treating every operational decision with the seriousness that a life-support-adjacent environment demands.

The computing infrastructure aboard the ISS has been upgraded multiple times over that quarter-century. Each upgrade cycle has had to balance cost, weight, compatibility, security, and crew workload. The current upgrade to HP ZBook Fury G9 machines is simply the latest iteration of a process that will continue for as long as humans occupy the station.

What makes this moment notable is the context in which it's happening. We are, in April 2026, in the middle of a global conversation about AI integration, infrastructure resilience, and the governance of critical systems. The ISS upgrade is a reminder that the fundamentals of good infrastructure management — sequence carefully, validate thoroughly, plan for security, train your users — don't change just because the technology does.

The astronauts of Expedition 74 will get their new laptops. They will work better, run more sophisticated software, and support more demanding scientific workloads. And somewhere in Houston, a team of engineers will have spent months ensuring that the transition was as close to invisible as possible.

That's what good infrastructure looks like. It's boring by design.

Alex Kim is a former financial wire reporter covering Asia-Pacific tech and finance, now writing independently on global markets, technology infrastructure, and geopolitics. Follow for analysis that bridges East and West perspectives on the stories that matter.

I notice the previous content already includes a complete conclusion and a closing author bio — the piece ends with "That's what good infrastructure looks like. It's boring by design." followed by a full author signature.

That means the article is, structurally, already complete. Appending more content after a clean closing line and author bio would break the piece's integrity.

However, if what you need is an extended final section — perhaps a deeper analytical coda that was cut off before the conclusion was reached — here is a natural continuation that slots in before the closing line, expanding the analysis with fresh material:

The Geopolitical Footnote Nobody Is Talking About

There is one dimension of the ISS laptop upgrade that rarely surfaces in the technical briefings: the supply chain behind the hardware itself.

HP's ZBook Fury G9 is assembled with components that cross multiple jurisdictions — chipsets, memory modules, display panels, and firmware stacks that touch factories in Taiwan, South Korea, Malaysia, and, in some cases, mainland China. For a commercial enterprise deploying these machines in a corporate office, that supply chain complexity is a manageable risk. For NASA, deploying hardware into an environment where a firmware vulnerability cannot be patched with a quick IT ticket, the provenance of every component matters in ways that go well beyond typical procurement checklists.

This is not a hypothetical concern. In 2023 and 2024, U.S. federal agencies accelerated their reviews of hardware supply chains under executive orders tied to critical infrastructure protection. The ISS, while an international scientific platform, operates under U.S. jurisdiction for its American segment — and the computers running that segment are subject to the same scrutiny applied to any federal critical system.

What that means in practice: NASA's procurement process for the ZBook Fury G9 almost certainly included a hardware security review that goes far beyond what HP's commercial customers receive. Firmware integrity verification, component-level audits, and potentially custom security configurations would have been part of the package. The laptop you can buy at Best Buy and the laptop that goes to the ISS share a chassis. They are not the same device.

This matters as a broader lesson for enterprise infrastructure teams navigating the current environment. The instinct, particularly in cost-pressured organizations, is to treat hardware procurement as a commodity exercise — find the spec, find the price, place the order. What NASA's process illustrates is that for systems where failure has serious consequences, procurement is itself a security function. The hardware decision and the security decision are the same decision.

Why This Matters Beyond the Station

The ISS upgrade cycle also offers a useful lens for thinking about the wave of AI-adjacent infrastructure investment currently sweeping through enterprise technology budgets.

In April 2026, organizations across every sector are being pitched on GPU clusters, edge inference hardware, and AI-optimized workstations. The sales narrative is almost always about capability — what these machines can do. The ISS experience is a reminder to ask a different set of questions: What happens when this hardware reaches end-of-life in a system that cannot afford downtime? How does the upgrade path work when the environment is constrained? Who is responsible for validating that the new system behaves identically to the old one in every scenario that matters?

These are not glamorous questions. They do not make for compelling vendor presentations. But they are precisely the questions that separate organizations that manage infrastructure well from those that discover its importance only after something breaks.

The astronauts aboard the ISS are, in a sense, the most demanding enterprise users on the planet — or rather, above it. Their computing environment has zero tolerance for the kind of "we'll fix it in the next patch" culture that has become normalized in commercial software development. Every upgrade has to work. Every transition has to be planned. Every failure mode has to be anticipated before the hardware leaves the ground.

That standard is not achievable for most organizations. But the discipline behind it — the insistence on sequencing, validation, security review, and user preparation — is transferable to any environment where the cost of failure is high.

That's what good infrastructure looks like. It's boring by design.

NOCODE TECH STACKER