Amazon Leo

Amazon Leo is Amazon's low-Earth-orbit satellite broadband network, formerly known as Project Kuiper.

It is designed to provide fast, low-latency connectivity to consumers, businesses, governments and other customers beyond the reach or reliability of conventional terrestrial networks.

Unlike Marketplace, Prime or AWS, Leo is still in an early deployment and commercial-rollout phase.

That maturity difference should remain explicit.

Explain It in 30 Seconds

thousands of low-Earth-orbit satellites
↓
optical links + ground infrastructure
↓
customer antenna
↓
internet connectivity

Amazon says the planned constellation includes more than 3,000 satellites. [S25]

The network uses multiple customer-terminal designs for different performance and customer requirements. [S25]

Where It Sits in Amazon

Amazon Leo is not a feature of AWS, even though cloud infrastructure can support operations.

It is its own communications infrastructure platform.

AMAZON INFRASTRUCTURE BUSINESSES├── fulfillment / logistics
├── AWS cloud
└── Amazon Leo connectivity

The common theme is capital-intensive infrastructure that can be sold as a service.

The Problem It Tries to Solve

Terrestrial internet access is uneven.

Some locations lack:

  • fiber;
  • cable;
  • reliable fixed wireless;
  • high-capacity mobile coverage.

Remote businesses, ships, aircraft, households and public-sector customers may therefore need alternative connectivity.

Low-Earth-orbit satellite systems can reduce latency compared with older geostationary architectures because satellites orbit much closer to Earth.

How It Works — Simple Version

Satellite layer

A large constellation of satellites moves in low Earth orbit.

Inter-satellite / network layer

The system uses high-speed optical links and ground-network connections. [S25]

Ground stations

Gateways connect the constellation to terrestrial networks.

Customer terminal

Customers use an antenna to communicate with the satellites.

Amazon has described terminals including Leo Nano, Leo Pro and Leo Ultra. [S25]

From Project Kuiper to Amazon Leo

Project Kuiper was the original project name.

Amazon renamed the system Amazon Leo in November 2025. [S25]

The relationship should therefore be treated as:

aliases:
  - Project Kuiper

as historical naming.

The canonical page should use the current name.

Deployment

Full-scale constellation deployment began in 2025. [S25]

Amazon continued launching satellites through 2026 and said service would roll out more broadly as it added coverage and capacity. [S26]

This is an important editorial distinction:

Amazon Leo is not yet comparable with AWS in commercial maturity.

A current page should explain buildout status rather than imply a mature global subscriber base.

Customer Segments

Amazon Leo targets several categories.

Consumers

Households without strong terrestrial broadband.

Businesses

Remote sites, distributed operations and locations beyond fiber reach.

Governments

Public-sector users needing resilient or remote connectivity.

Maritime

Ships need connectivity far from terrestrial networks.

Aviation

Aircraft can use satellite connectivity for in-flight service.

Telecom partners

Future direct-to-device infrastructure can potentially extend mobile-network coverage.

Terminal Strategy

Amazon has designed different antennas for different use cases. [S25]

The broad concept is:

small / lower-throughput terminal
→ portable / lower-intensity use

mid-tier terminal
→ general broadband

high-performance terminal
→ enterprise / high-throughput use

This lets one constellation serve different customer economics.

Amazon Leo + AWS

Leo and AWS are separate products, but there are potential infrastructure synergies.

A remote customer may need both:

connectivity
+
cloud computing

AWS also provides Amazon with deep experience operating global infrastructure.

The connection should be described carefully rather than implying every Leo customer automatically becomes an AWS customer.

Amazon Leo + Globalstar

In April 2026 Amazon announced an agreement to acquire Globalstar. [S27]

The strategic rationale included adding direct-to-device capabilities to future generations of the Amazon Leo network.

Globalstar brings:

  • satellites;
  • spectrum;
  • operational expertise.

But the transaction is pending.

Globalstar's Q2 2026 update said the transaction was still going through regulatory approvals and was expected to close in 2027. [S28]

Therefore:

DO NOT WRITE:
Amazon acquired Globalstar in 2026.

WRITE:
Amazon agreed to acquire Globalstar in 2026; the transaction remains pending.

Direct-to-Device

Traditional satellite broadband uses a dedicated user terminal.

Direct-to-device aims to connect supported mobile devices more directly through satellite networks.

The proposed Globalstar transaction would help Amazon expand toward this capability. [S27]

That potentially broadens Leo from:

broadband terminal network

into:

broadband
+
mobile coverage extension

if the transaction closes and the technology is deployed successfully.

How It May Make Money

Commercial economics are still emerging.

Potential models include:

  • consumer broadband subscriptions;
  • enterprise connectivity;
  • government contracts;
  • aviation / maritime partnerships;
  • wholesale connectivity;
  • future telecom partnerships.

Do not present unannounced pricing or mature margins as established fact.

What It Depends On

Launch cadence

A constellation needs enough satellites to provide coverage and capacity.

Spectrum

Satellite communications require access to regulated radio spectrum.

Ground infrastructure

Satellites alone do not create an internet service.

Terminals

Customer hardware must be affordable and reliable.

Capital

Satellite networks require large upfront investment.

Regulation

Multiple jurisdictions regulate launches, spectrum and communications services.

What Depends on Amazon Leo

Today, fewer established Amazon businesses depend directly on Leo than on AWS or fulfillment.

Potential future dependencies include:

  • remote Amazon operations;
  • enterprise connectivity partnerships;
  • aviation and maritime services;
  • direct-to-device offerings.

This is another reason not to overstate its current role.

Why It Matters to Amazon

Leo extends a recurring Amazon pattern:

build difficult infrastructure
↓
operate at scale
↓
sell access as a service

The pattern resembles AWS and logistics conceptually.

The market, technology and economics are entirely different.

Before / After

Before Leo

Amazon's infrastructure businesses centered mainly on:

physical commerce logistics
+
cloud infrastructure

With Leo

Amazon is attempting to add:

communications infrastructure

That creates a new boundary for the company.

What Most People Misunderstand

“Amazon Leo is still called Project Kuiper.”

No.

Project Kuiper is the former name. [S25]

“Leo service is already globally mature.”

No.

The network is still expanding coverage and capacity.

“Amazon owns Globalstar.”

Not yet.

The proposed acquisition is pending and expected to close in 2027 if conditions are satisfied. [S28]

“Leo is part of AWS.”

It is an Amazon infrastructure platform, but not simply an AWS service.

Key Milestones

Project phase

Amazon develops Project Kuiper as a LEO broadband program.

2025

Full-scale deployment begins. [S25]

November 2025

Project Kuiper becomes Amazon Leo. [S25]

2026

Constellation launches accelerate and commercial rollout progresses. [S26]

April 2026

Amazon announces proposed acquisition of Globalstar. [S27]

2027 expected

Globalstar transaction expected to close, subject to approvals and conditions. [S28]

Evidence

  • [S25] Amazon Leo Overview
  • [S26] 2026 Deployment
  • [S27] Proposed Globalstar Acquisition
  • [S28] Globalstar Q2 2026 Transaction Update

Connected Entities