Amazon Leo (formerly Project Kuiper) entered enterprise commercial beta on 8 April 2026 with launch partners including Verizon, AT&T, Vodafone, JetBlue, and NASA. The NCC granted Amazon a 7-year Nigerian landing permit on 28 February 2026, with roughly 270 production satellites in orbit at the beta launch. For institutional buyers in Nigeria, the most interesting thing about Amazon Leo isn't whether it 'beats' Starlink on any single metric, it's that for the first time, Nigerian organizations will have a credible second LEO option, and the regulatory groundwork is already in place.
Why a second LEO matters
A monoculture is a risk. If your business-continuity plan depends on Starlink and Starlink has a bad month, pricing change, regulatory friction, capacity congestion in your beam, you have no fallback in the same category. Amazon Leo's arrival changes that. Two independent LEO operators on a managed SD-WAN means your satellite-based resilience plan is no longer single-vendor.
What we're watching
- Nigerian licensing and ground-station footprint timelines.
- Per-Mbps pricing relative to Starlink Business and local ISPs.
- Enterprise-grade SLAs (vs. consumer-class terms) for institutional contracts.
- Integration support, how clean is the SD-WAN underlay story going to be?
With the NCC landing permit secured but Nigerian commercial pricing and enterprise SLAs not yet published, we're treating Amazon Leo as a near-term procurement option, not a planning abstraction. The constellation density still trails Starlink materially in 2026 (~270 satellites vs. thousands), so we're recommending it as a second LEO leg rather than a primary path. The architecture conversations we're having with public-sector buyers already account for it: hybrid designs that can absorb a second LEO operator without re-engineering the network.