Imagine if one company could become the railroad, electric utility, and cloud-computing provider of the emerging space economy. That potential fueled excitement around the long-anticipated initial public offering of SpaceX. Investors are not simply betting on rockets anymore. They are betting on an entire orbital ecosystem.

Among the most ambitious and challenging ideas riding this wave of enthusiasm is something that sounds almost like science fiction: orbital data centers. SpaceX may be one of the most well-known companies seeking to build them, but it is not the only one.

The logic is seductive: Launch the data centers into orbit, where solar energy is abundant and land, water, and local power grids are no longer constraints. As artificial intelligence drives an explosion in computing demand, companies are pitching orbital data centers as a way to escape the growing environmental and infrastructure pressures of Earth-based computing. Data centers often also face backlash from the public at having these centers located in their communities.

But there is a vast difference between launching satellites and operating an industrial-scale computing infrastructure in orbit. Space is unforgiving. Radiation damages electronics. The electronics generate enormous amounts of heat, and getting rid of that heat is surprisingly difficult in space. Repairs are extraordinarily expensive, and every pound launched into orbit still carries a significant cost.

We are engineering professors who study data-center design and space systems engineering. Building a space-based data center will involve considerations from both sides.

What Goes Into a Data Center on Earth

First off, consider what goes into an Earth-based data center, like those that you’ve probably begun to see pop up everywhere. These facilities power cloud computing, video streaming, online banking, scientific computing, and increasingly, artificial intelligence. But a data center is much more than a room full of servers.

A data center needs several things to operate reliably. The first is electric power. Servers, networking equipment, and storage devices consume large amounts of electricity, and that power demand is growing rapidly with AI.

The second is cooling. Almost all the electricity consumed by servers eventually becomes heat. If that heat is not removed quickly and reliably, equipment performance drops, failures increase, and the data center can shut down. Cooling systems often include air handling units, chillers, cooling towers, pumps, and increasingly, liquid-cooling equipment. In many facilities, cooling is the largest energy consumer after the computing equipment itself.

The third is physical infrastructure, including the necessary land, buildings, structural support, backup power, water systems, communication networks, and maintenance access. Data centers also need to be close enough to users and network backbones to provide fast digital services.

In short, Earth-based data centers are large electrical and thermal infrastructure systems built around computing hardware.

Placing Them in Space

So what would it take to build these data centers in space, and why are companies finding this possibility such an interesting business proposition?

As on Earth, these data centers would require massive amounts of power. In space, this power would come from solar panels. The sun always shines in space and can’t be blocked by clouds. However, depending on the orbit the solar panels are put in, the Earth may shadow them for some portion of the orbit.

And even the best solar cells available today can convert only about half the sunlight that hits them to electricity.

Another potential advantage found in space is cooling. The cold background of space (roughly -455 degrees Fahrenheit, or -270 degrees Celsius) creates an opportunity: Waste heat from the data center could escape into space through radiators, keeping the electronics cool.

In principle, that design could eliminate some of the bulky and water-intensive cooling infrastructure used on Earth. However, those thermal radiators would require a large amount of surface area, and that would be in addition to the area required by the solar panels.

In space, there is no air to blow across hot equipment and help heat escape. The heat has to leave as infrared radiation, which is a relatively slow process. As a result, removing 10 megawatts of waste heat can require radiator surfaces comparable to the size of two football fields.

Space-based data centers could also avoid some of the local conflicts that come with building large data centers on the ground. Many communities resist new data center developments because of their land use, energy and water demand, and noise and environmental impact.

A space-based system would avoid competing for local land and water resources, and it would not generate neighborhood noise or require local zoning approval in the same way.

However, space is already getting crowded, and launching thousands of large orbital data centers would accelerate this issue. Orbital debris and micrometeorites are hazards because they can puncture the space data center, and a worst-case collision could destroy it and create even more space debris.

The frequency of space launches necessary to send all the equipment to orbit may also become a concern for some communities. SpaceX has had protests at its launch complex in Boca Chica, Texas from local activists who argue its rocket testing and launches damage the surrounding environment.

All that data would need to be sent between Earth and these data centers—and between the data centers themselves—using radio waves or laser communications systems. Although satellite constellations such as Starlink and Amazon Leo have demonstrated that doing this is possible, the amount of data sent to and from space would balloon.

Additional Challenges

These data centers, along with their solar panels and radiators, cannot be launched in one piece and would need to be assembled in space. This process would require new equipment for in-space servicing, assembly, and manufacturing.

Another key challenge is the refresh cycle of computing hardware. Data-center servers are not built to last forever. Operators on Earth usually replace or upgrade hardware every three to five years as chips improve, workloads change, and equipment ages.

And equipment failures can require replacing components. The refresh and repair processes are relatively straightforward on Earth, where workers can physically remove and replace servers.

In space, refresh and repair becomes much harder. Hardware sent to orbit may be difficult or too expensive to upgrade. If the computing platform cannot be updated, or too many components fail, it may become obsolete long before the surrounding infrastructure reaches the end of its useful life.

In a field where performance improves so rapidly and demand from computing continues to increase, this hurdle could prove a major economic and operational challenge.

Then there is the harshness of space. These data centers would be in a near vacuum, with constant radiation hitting them. And depending on their orbit, they would go from hot when in the sunlight to cold in Earth’s shadow many times a day. All of these challenges, and more, are issues that will need to be addressed.

So, Do They Still Make Sense?

Despite these challenges, companies are moving forward with designing space-based data centers. SpaceX just announced the design for its AI1 Compute Satellite, which it hopes to use as an orbital data center spacecraft. However, this satellite is 100 to 1,000 times less capable than current Earth-based data centers.

Not every computing task makes sense to do in space. Many data center applications depend on fast response times and close connections to users on Earth. Financial transactions, interactive AI services, and most cloud applications are extremely sensitive to delay.

More feasible early applications may be those that are less latency-sensitive and more tightly connected to space operations. Examples could include processing Earth observation data from satellites, military or intelligence data processing, scientific computing related to space missions, or specialized computing for satellites and other space assets.

In other words, the first viable space data centers may serve space-based customers before they compete with mainstream cloud data centers on Earth.

This article is republished from The Conversation under a Creative Commons license. Read the original article.

The post Orbital Data Centers Are Seductive on Paper, but They Face Daunting Challenges in Reality appeared first on SingularityHub.

Last week AWS Summit New York City brought together thousands of customers, partners, and builders for a free, one-day event showcasing the latest in cloud and AI innovation. Dr. Swami Sivasubramanian, VP of Agentic AI at AWS unveiled a stack of AI launches in his keynote, all built around one thesis: agents that compound value over time.

• Agents for working – You can launch autonomous agents and access a smarter activity feed with new Amazon Quick features, which now let you create and run multi-step agents directly in the desktop app and consolidates email, Slack, calendar, and tasks into a single prioritized view with personalized rules.
• Agents for securing – You can shift from reactive to proactive security with AWS Continuum, a new AI-native security service that reasons, validates, and acts at machine speed across the full code vulnerability lifecycle. AWS Security Agent (now part of AWS Continuum) adds new features: threat modeling; pull request code scanning with remediation across major Git platforms; and IDE integrations via Kiro power, Claude Code plugin, and MCP.
• Agents for building – You can write, ship, and modernize code in one continuous loop with Kiro, AWS DevOps Agent, and AWS Transform. Kiro introduces a native iOS app; AWS DevOps Agent adds release management capabilities to assess code changes before production; and AWS Transform continuous modernization reduces tech debt autonomously.
• Agents customers create – You can go from agent idea to production in minutes with Amazon Bedrock AgentCore, which now includes a GA harness for infrastructure and orchestration, Web Search, Managed Knowledge Base, policy integrations with Guardrails, and the new AWS Context service for mapping organizational data relationships.

To learn more, visit the Summit recap from our top announcements blog post and Amazon News post.

Last week’s launches
Here are last week’s launches that caught my attention:

• AWS Local Zone in Hanoi, Vietnam – This new Local Zone is one of the first AWS Local Zones in the Asia Pacific with support for Amazon S3 and Amazon EBS Local Snapshots, enabling customers to meet data residency requirements by storing and backing up data locally. To get started, enable the Hanoi Local Zone (ap-southeast-1-han-1a) from the Regions and Zones tab in the AWS Global View or by using the ModifyAvailabilityZoneGroup API.
• AWS Blocks, an open-source TypeScript framework for application developers (preview) – AWS Blocks runs a fully functional local environment with Postgres, authentication, and real-time messaging, no AWS account required. When you’re ready to deploy, the same application code runs on production AWS services with zero changes, and you can drop into AWS CDK at any point for direct resource configuration.
• Grok 4.3 from xAI in Amazon Bedrock – You can use the Grok 4.3 model on Amazon Bedrock, giving you even more choice as you build generative AI applications across reasoning, agentic, and enterprise workflows. Grok 4.3 runs on a new inference engine in Bedrock designed for price performance, with support for tool calling, structured output, and response streaming.
• Amazon S3 annotations: attach rich, queryable context directly to your objects – Amazon S3 now lets you attach up to 1 GB of rich, mutable, and queryable context directly to your objects using annotations, purpose-built for AI agents and autonomous workflows that need to discover, understand, and act on data at scale without maintaining separate metadata systems.
• Amazon ECS announces faster service auto scaling – Amazon ECS service auto scaling now detects and responds to load changes faster with support for high resolution (20-second) metrics and metric publishing optimizations. In AWS benchmarking tests, time to trigger scale-out improved from 363 seconds to 86 seconds (76% faster), and total time to scale and provision new tasks improved from 386 seconds to 109 seconds (72% faster).
• Amazon EC2 G7 instances accelerated by NVIDIA RTX PRO 4500 Blackwell Server Edition GPUs – AWS is the first major cloud provider to support NVIDIA RTX PRO 4500 Blackwell Server Edition GPUs. G7 instances are accelerated by these GPUs with custom sixth-generation Intel Xeon Scalable processors, delivering up to 4.6x AI inference performance and up to 2.1x graphics performance compared to G6 instances.
• Strands Agents introduces new capabilities – Strands is an open source toolkit for building production agents. You can now use better context management in Harness SDK, a new isolated execution environment with Strands Shell, and chaos testing and red teaming in Strands Evals.
• AWS Management Console Private Access – You can access the AWS Console from VPCs without internet connectivity, allowing enterprises to manage their AWS infrastructure through the console while maintaining strict network security controls in air-gapped environments.
• AWS Marketplace Storefront is now generally available – AWS Partners can create and deploy their own branded catalog of solutions and services on their website or application in hours. Channel Partners and Independent Software Vendors can now simplify how they manage their cloud marketplace business and make it easier for customers to discover and purchase their solutions from AWS Marketplace.
• Palo Alto Networks (PANW) Advanced DNS Security on Amazon Route 53 Resolver DNS Firewall (preview) – You can now enforce DNS threat protections from Palo Alto Networks directly on Route 53 DNS Firewall rules, without deploying separate firewalls or modifying VPC configurations — by subscribing to PANW from the DNS Firewall console through the embedded AWS Marketplace widget.

For a full list of AWS announcements, be sure to keep an eye on the What’s New with AWS page.

Price reductions 
AWS continues to look for ways to increase performance and lower prices for our customers. I noticed a few such efforts last week, so I’d like to share them:

• Amazon S3 Vectors reduces query charges by up to 80% for large vector indexes – This reduction lowers costs for customers running similarity search across large-scale AI, RAG, and semantic search workloads. The new pricing applies automatically with no application changes required.
• Amazon GameLift Servers introduces free network bandwidth – Amazon GameLift Servers provides network bandwidth in and out of AWS at no additional charge for all instance types from generation 6 and later, including On-Demand and Spot, with no commitment required. You now pay only for your Amazon GameLift Servers instance hours; all network bandwidth is free.
• AWS Marketplace reduces listing fee for professional services to 0.5% from 2.5% – This reduction makes it more cost-effective for consulting partners, systems integrators, managed services providers and independent software vendors to transact their services through AWS Marketplace, while retaining the procurement and billing benefits that come with it.

Learn more about AWS, browse and join upcoming AWS-led in-person and virtual events, startup events, and developer-focused events as well as AWS Summits and AWS Community Days. Join the AWS Builder Center to connect with builders, share solutions, and access content that supports your development.

That’s all for this week. Check back next Monday for another Weekly Roundup!

— Channy

AI companions in games have long been constrained by fixed dialogue. PUBG Ally is a different kind of system. Built by KRAFTON for PUBG: BATTLEGROUNDS, this AI...

AI companions in games have long been constrained by fixed dialogue. PUBG Ally is a different kind of system. Built by KRAFTON for PUBG: BATTLEGROUNDS, this AI teammate is powered by NVIDIA ACE and its suite of efficient models and tooling. PUBG Ally uses automatic speech recognition, a 2B-parameter small language model, and text-to-speech to understand player voice…

Source

When a group of academics started making open-source robotics hardware, a generation of roboticists got years of their lives back. Now, the bigger challenge is getting robots to think—and that’s starting to be open sourced too.

The shift is still early, but companies including Hugging Face, Nvidia, and Alibaba have all made significant bets on open-source robotics in the last two years, releasing tools and models aimed at the higher-level work of getting robots to reason, decide, and act.

The open source movement that accelerated other AI applications is now being applied to the problem of making robots smarter. If these attempts to bring AI to robotics with open-source platforms succeed, the barrier to building a capable robot could fall as fast as the barrier to building an AI application did.

The world ROS built

Open-source robotics software has been around since the mid-1990s, with early projects like Carnegie Mellon University’s Inter-Process Communication package and the Player Project in the early 2000s laying the groundwork. But these were often tied to specific research groups, and the field remained fragmented.

The Robot Operating System, ROS, changed that when it made its debut in 2007. By bundling tools and attracting more users, it became the de facto standard. The story of open-source robotics, in many ways, starts there.

Despite its name, ROS is not actually an operating system. Rather, it is a software framework that sits on top of Linux and handles robotic fundamentals like moving data between components, talking to hardware, building maps, planning paths, and supporting developer tools, such as data logging and visualization. Before ROS, every robotics team wrote that infrastructure themselves. It often took a year or two before a lab could get to the research it actually cared about.

Brian Gerkey, who helped build ROS in the mid-2000s, says he was drawn to the project because of how much open source had already changed the world, pointing out that nearly the entire internet is built on it.

“I’m a tool builder, and I like to share everything as openly as I possibly can, because I think that’s where we get the most impact out of what we build,” says Gerkey, board chair of Open Robotics and now CTO at Intrinsic, a robotics and AI unit of Google.

As it was developing, the AI community largely took the same approach, sharing research, models, and data openly, and the field accelerated faster than almost anyone predicted. Now some of those same advancements are arriving in robotics.

Open-source AI for robotics

Computer vision, once a hard problem, has advanced dramatically in just a few years, says Spencer Huang, Nvidia’s director of product for robotics. What once required significant expertise can now be done in a few lines of code. Simulation tools have become accurate enough to be useful for training, and access to the tooling that once required a specialized lab is now widely available, much of it open source.

“To get into robotics, you no longer need a Ph.D.,” he says. The result is a much larger pool of people who can contribute, and the field is starting to look less like a specialized discipline and more like a platform that anyone can build on.

Nvidia has built out an open-source robotics stack that covers the full development pipeline. Its Cosmos world models generate synthetic training data and simulate physical environments. Its GR00T models give robots the ability to reason through and execute complex tasks. And its Isaac frameworks handle the orchestration that ties training, simulation, and deployment together. Not everyone needs to train the robots from scratch, Huang says, and most people probably shouldn’t.

“If you gate pre-training, the field just never grows,” he says. “We should be able to provide a high-quality, state-of-the-art pre-trained model that anyone can go and take and fine tune for their own purposes.”

All of Nvidia’s open-source models live on Hugging Face, the open-source AI platform that has become the default place to share models and datasets. Hugging Face launched LeRobot, a community platform for robotics AI, in May 2024. Since its launch, the number of robotics datasets on the platform grew from 1,145 at the end of 2024 to more than 58,000 today, making it the single largest dataset category on the hub.

Hugging Face has also moved into hardware, acquiring robotics company Pollen Robotics. The acquisition came from a realization that software alone was not enough, according to Clement Delangue, Hugging Face’s CEO. The goal, as with the software, was to bring more people in.

The contributors to LeRobot include the biggest names in the industry, academic labs, and hobbyists building robots in their spare time. For instance, earlier this year, Alibaba released RynnBrain, an open-source foundation model for physical AI that the company claims outperforms comparable offerings from Google and Nvidia on benchmarks. That diversity of projects, Delangue says, is important.

“It is not just one model or one dataset or one hardware,” he says. “It is a lot of small contributions that everyone can be part of.”

Commercial incentives muddle the field

The stakes, Delangue says, go beyond convenience. A world where only a few proprietary systems control the robots in people’s homes is a concerning one. “Having robots at home that you don’t really understand, that you don’t really control, that a few people in Silicon Valley control is a scary thought,” he says. “Open source gives an alternative path.”

But getting there is not straightforward. The open sourcing happening now looks different from what produced ROS, which emerged largely from academics pooling their work with no commercial stake in the outcome. The biggest contributors today are companies with clear business reasons to want more people building on their platforms. That’s not necessarily a bad thing, says Bill Smart, a professor at Oregon State University, in Corvallis, who was part of the early open-source robotics community. But the incentives are worth being aware of.

He also worries that the lowered barrier to entry has a downside. Researchers coming from AI without a robotics background are sometimes solving problems the field already solved. A newcomer might spend a week training a neural network to move a robot’s hand from one point to another, unaware that the same task can be accomplished with a few lines of code using decades-old techniques. The incentives are not always pointing in the same direction as the progress.

Smart is not without hope though. Whatever the motives behind the open sourcing, he says, the effect is real. More people are in the field than ever before, the tools are genuinely easier to use, and the community is bigger and more diverse than anything that existed when ROS was getting started.

“Anyone can make a robot move now,” he says. “As an old tech guy, that makes me happy and sad, because I’m no longer special.”