June 16, 2026 | By Admin User | 5 min read

Uganda's First AI Factory

Uganda's Aeonian Project: Africa's First Sovereign AI Factory Is Being Built on the Nile

June 2026 | Infrastructure & AI

A $1.2 billion AI facility is currently taking shape inside the Karuma Hydropower Plant on the River Nile. For tech professionals tracking Africa's infrastructure trajectory, the Aeonian Project is worth paying close attention to - not just as a headline, but as a meaningful architectural shift in how AI compute is provisioned on the continent.

The Problem It's Solving

The statistic that frames this project is stark: approximately 98% of African data is currently processed outside the continent. That means African researchers, startups, and enterprises building AI systems are almost entirely dependent on foreign cloud providers - AWS, Azure, GCP - for the compute they need. The latency, cost, currency risk, and data sovereignty implications of that dependency are significant, and they've been largely accepted as the cost of doing business in Africa's tech ecosystem.

The Aeonian Project is a direct attempt to change that calculus.

What's Actually Being Built

The facility is structured as a 100MW hyperscale Tier-4 Plus hybrid off-grid green energy Data & High-Performance Computing Centre (DHPC), divided into six 15MW AI modules (KRM1-KRM6) plus 10MW dedicated to supercomputing, totalling 100MW at full build-out.

At the core is USIO, a sovereign supercomputer built in partnership with NVIDIA, AI infrastructure firm MDCS.AI, and Belgian automation company Automation NV. USIO runs on NVIDIA's Blackwell GPU platform - the same architecture powering frontier AI workloads globally - making it genuinely competitive hardware rather than a mid-tier compromise.

Rollout timeline:

- H2 2026 - Phase 1: 15MW AI module + USIO supercomputer goes live

- 2027 - Full 100MW capacity reached across all six modules

- 2028 - Sequential completion of remaining modules ensuring modular autonomy

The Engineering Choices Are Deliberate

What makes the Aeonian Project technically interesting is how tightly the infrastructure design is tied to its physical location.

Power: The facility draws on surplus pre-transmission electricity from Karuma's 600MW output - up to 100MW of renewable hydropower that would otherwise be underutilised. This solves one of AI infrastructure's most pressing problems (energy cost and availability) using existing capacity.

Cooling: Rather than energy-intensive mechanical cooling, the facility uses natural Nile river water. Combined with modular heat-reuse technologies, this makes Aeonian one of the few AI data centres globally with a genuinely low environmental footprint by design, not just by offset.

Connectivity: Two leased dark fibre optic cables link the facility to Kampala, and onward via a 2,500 km fibre network to submarine cables in Kenya and Tanzania - plugging Uganda directly into the global internet backbone.

Why Sovereignty Matters for Developers

For engineers and researchers building on this infrastructure, the sovereignty angle isn't just political - it has practical consequences:

Local language model training. One of the persistent gaps in African AI is the lack of models trained on local languages and African contextual data. With sovereign compute on the continent, institutions can train models on Luganda, Kiswahili, and other regional languages without routing sensitive datasets through foreign jurisdictions.

Data residency compliance. As African nations develop their own data protection frameworks, the ability to guarantee that data never leaves the continent becomes a compliance requirement, not just a preference.

Lower latency for regional applications. Applications in healthcare, agriculture, and fintech that depend on real-time inference benefit directly from compute that's geographically close to their users.

The Broader Context

The Aeonian Project isn't happening in isolation. It's part of a coordinated regional push:

- The African Development Bank and UNDP launched an AI 10 Billion Initiative at the 2026 Nairobi AI Forum, targeting a $1 trillion GDP impact by 2035.

- East Africa is actively pursuing an AI sovereignty agenda, prioritising systems built on local data and hosted on regional infrastructure.

- Uganda's Ministry of ICT is finalising a National AI and Emerging Technologies Strategy this month, providing the policy framework that will govern how facilities like Aeonian are used.

International backing includes Germany's GIZ, Finland's HAUS, the EU Development Fund, and other European development agencies - signalling that this is not a speculative venture but an infrastructure bet with multilateral support.

What This Means in Practice

For developers in Uganda and East Africa, the operational launch of Phase 1 in H2 2026 represents something concrete: access to NVIDIA Blackwell-class compute without routing workloads through US or European cloud regions. For startups, that's a meaningful cost and latency improvement. For researchers, it's the possibility of building models that actually reflect African data distributions.

The comparison MDCS.AI co-founder Niels Van Rees draws is pointed: "Data and AI will define economic opportunities in the coming decades. This facility positions Africa to lead in innovation rather than follow." Whether that ambition materialises depends on execution - but the technical and financial foundations being laid at Karuma are more serious than anything the continent has attempted in AI infrastructure before.

The Nile has powered Uganda for decades. In 2026, it's starting to power something else entirely.

Related Insights

May 22, 2026

Choosing A Tech Course the Right Way

Navigating the Maze: Why Choosing a Tech Course Feels So Hard (And How to Fix It)   So, you have decided to break into tech. You open a course platform, type in "coding," and suddenly you are staring at 50,000 results. Python, UX design, cloud architecture, cybersecurity, data science: the options are endless. Very quickly, excitement turns into total paralysis. Choosing a tech course is uniquely overwhelming. Here is an honest look at why this choice feels so incredibly hard, and a simple framework to help you cut through the noise. Why the Choice Feels Impossible If you are struggling to pick a path, you aren't lazy or indecisive. The tech education landscape is specifically designed to confuse beginners for three main reasons: 1. The Hype Machine Every bootcamp advertisement promises that their specific language or tool is the golden ticket to a six-figure job. One week "AI is replacing everything," the next week "cybersecurity has a massive worker shortage." It is hard to choose when the industry's marketing changes every month. 2. The Illusion of Choice In tech, there are ten different ways to solve the exact same problem. You can build a website using WordPress, React, Python, or No-Code tools. As a beginner, it is impossible to know which ecosystem is worth your time and money. 3. Fear of the "Wrong" Choice   Tech moves fast. It is completely normal to worry that by the time you spend six months finishing a course, the tool you learned will be obsolete or replaced by artificial intelligence. The Reality Check: Where the Difficulty Actually Lies   The difficulty of a tech course isn't just about the coding syntax. It depends heavily on how you think. Before you swipe your credit card, match your natural brain type to the actual day-to-day work: [ Your Brain Type ] │ ├──► Logic & Math Heavy ───► Data Science / AI / Backend │ ├──► Visual & Creative ────► UI/UX Design / Frontend Development │ └──► Process & Systems ────► DevOps / Cybersecurity The Logic Trap (Data and Backend): If you hate math, statistics, or abstract problem-solving, a Python Data Science course will feel like a mountain. The Creative Trap (UI/UX and Frontend): If you hate tweaking colors, layouts, and thinking about human psychology, frontend development will frustrate you quickly. The Chaos Trap (Cybersecurity and DevOps): If you like predictable, structured tasks, these fields will overwhelm you. They require hunting for hidden errors in massive systems. How to Choose Without the Regret   To beat the analysis paralysis, stop looking for the "perfect" course. Instead, follow this three-step filters framework:   Step 1: Pick a Bucket, Not a Language Do you want to build things people look at (Frontend/Design), handle the invisible logic behind the scenes (Backend/Cloud), or find stories in numbers (Data Science)? Pick one bucket first.   Step 2: Date the Field Before You Marry It Never buy a $1,000 bootcamp or a long university course on day one. Go to YouTube. Spend 5 hours watching free, absolute-beginner tutorials. Try to build a tiny project. If you want to throw your laptop out the window after two hours of HTML, you just saved yourself thousands of dollars.   Step 3: Look for "Building," Not "Watching" When you are ready to buy a course, look at the syllabus. If it is 40 hours of a lecturer talking over slides, skip it. The only way to learn tech is by breaking things. Choose courses structured around building real projects for a portfolio.   The Bottom Line There is no single "right" course. The secret of the tech industry is that most skills overlap. Learning the basics of logic in a JavaScript course will help you if you later switch to Python.   Pick one introductory course today, commit to it for two weeks, and see how it feels. Action cures anxiety every single time.  

May 17, 2026

Starlink Finally Lands in Uganda: What It Means for Internet Access

For years, Ugandans have heard about Starlink — the satellite internet service from SpaceX — transforming connectivity in remote parts of the world. Now, after months of speculation, negotiations, and regulatory discussions, Starlink is officially coming to Uganda. The development could mark one of the biggest shifts in Uganda’s internet landscape in years. Uganda Gives Starlink the Green Light In May 2026, the Ugandan government officially approved Starlink to operate in the country after reaching an agreement with the Uganda Communications Commission (UCC). The deal followed extensive talks around licensing, taxation, national security, and compliance with local telecom laws. Government officials described the agreement as a major step toward expanding internet access across the country — especially in regions where traditional telecom infrastructure has struggled to reach. Before the approval, Starlink had faced regulatory resistance. Earlier in the year, Ugandan authorities warned citizens against using unauthorized Starlink equipment because the company had not yet received an operating license. That situation has now changed. Why Starlink Matters in Uganda Internet access in Uganda has improved significantly over the past decade, but large gaps still remain. In many urban areas like Kampala, users can access fiber internet and relatively strong 4G or 5G networks. But in rural districts, connectivity is often slow, expensive, or unavailable altogether. That’s where Starlink becomes interesting. Unlike traditional internet providers that rely on cell towers or underground fiber cables, Starlink uses thousands of low-Earth orbit satellites to deliver broadband internet directly to a small dish installed at a home, school, or business. This means places that were previously difficult or expensive to connect could suddenly gain access to high-speed internet. Potential beneficiaries include: Rural schools needing online learning tools Health centers requiring telemedicine access Farmers using digital market platforms Remote businesses and tourism lodges NGOs and humanitarian operations Content creators and remote workers outside major cities Could Starlink Change Internet Prices? That’s the big question. Uganda’s internet market is currently dominated by major telecom providers like MTN Uganda and Airtel Uganda. These companies already serve millions of users through mobile data and fiber services. Starlink’s arrival introduces a new kind of competition. While Starlink is unlikely to replace mobile internet for most people anytime soon, it could pressure providers to improve speeds, reliability, and pricing — especially for home and business broadband customers. However, affordability may still be a challenge. In many African countries where Starlink already operates, the initial hardware kit can cost several hundred dollars, with monthly subscriptions also priced higher than standard mobile bundles. Uganda’s official pricing has not yet been fully announced, but many observers expect cost to be one of the biggest barriers to widespread adoption. Where to Buy Starlink in Uganda As Starlink officially enters Uganda, customers are expected to purchase kits through: Authorized local resellers and technology stores Online ordering through the official Starlink website Selected internet and ICT service providers Installation partners offering setup services for homes and businesses Customers should always confirm that the seller is authorized and that the equipment is genuine before making payment. For inquiries, installation assistance, or Starlink updates in Uganda: WhatsApp: https://wa.me/256763206676 The Bigger Picture: Africa’s Internet Race Uganda joins a growing list of African countries embracing satellite internet technology. Across the continent, governments are under pressure to close the digital divide and improve access to education, e-commerce, fintech, and digital public services. Reliable internet is increasingly viewed as essential infrastructure — just like roads and electricity. Starlink’s expansion into Uganda reflects a broader trend: global tech companies are seeing Africa as a major growth market for connectivity. At the same time, regulators are trying to balance innovation with concerns about sovereignty, taxation, cybersecurity, and market fairness. What Happens Next? Several details are still expected in the coming months: Official Ugandan pricing for Starlink packages Retail and installation partnerships Importation procedures for Starlink kits Coverage expansion timelines Customer support structures inside Uganda For now, one thing is clear: Uganda’s internet sector is entering a new phase. Whether Starlink becomes a niche premium service or a true connectivity revolution will depend on pricing, accessibility, and how quickly the company can scale across the country. But after years of waiting, the satellite internet era has officially arrived in Uganda.

Jul 01, 2026

Our first PPPOE Set Up in Uganda: Luxenetworks

How We Set Up PPPoE for a Client: A Luxenetworks Walkthrough At Luxenetworks, we get a lot of calls that start the same way: "My internet was working fine, then the ISP switched us to a new connection type, and now nothing works." More often than not, the culprit is PPPoE (Point-to-Point Protocol over Ethernet). Last week, we handled exactly this kind of job at a 50-unit apartment complex whose ISP had just migrated the property onto a PPPoE-based connection. Here's how we approached it, the equipment we used, and the steps we took, in case it helps you understand what a proper PPPoE setup actually involves at scale. First, What Is PPPoE and Why Does It Matter? PPPoE is a networking protocol that many ISPs, especially DSL and fibre providers, use to authenticate and manage customer connections. Instead of your router just grabbing an IP address automatically (like with DHCP), PPPoE requires your router to "dial in" using a username and password supplied by the ISP, much like old-school dial-up internet, just running over Ethernet instead of a phone line. The upside for ISPs is better control over billing, session management, and security. The downside for customers is that if it's not configured correctly, the connection simply won't come up: no internet, no clear error message, just a blinking light and a frustrated household. The Property and the Situation This job was for a 50-unit apartment complex. The building had just been switched over to a new connection by their ISP, and the property manager reached out after residents across multiple units started reporting the same issue: Wi-Fi showing as connected, but no actual internet access. With that many units relying on one shared connection point, even a small misconfiguration at the network core cascades into a building-wide outage, so we prioritized the visit. They called us with three symptoms: The core router showed a physical link to the ISP's line but no internet access The ISP-provided PPPoE username and password weren't being accepted Wi-Fi devices connecting through the access points on different floors could see the local network but had no external connectivity This is a textbook PPPoE misconfiguration, so we scheduled a visit. The Equipment We Used For a property of this size, we relied on a compact but capable equipment stack: MikroTik RB951: our core router, chosen for its RouterOS flexibility, reliable PPPoE handling, and the ability to manage NAT and firewall rules for the whole building from a single point Managed switch: sitting between the RB951 and the rest of the building, distributing wired connections out to each access point Tenda F6 wireless routers (x2): repurposed as dedicated Wi-Fi access points to extend coverage across the property, rather than acting as independent routers ISP-provided line: the incoming connection requiring PPPoE authentication Cat5e/Cat6 patch cabling: connecting the ISP termination point, RB951, switch, and each Tenda F6 in the chain This combination gave us a single, centrally managed PPPoE session at the RB951, with the switch and Tenda F6s doing what they do best: distributing that connection cleanly across a larger property without introducing conflicting routers or duplicate DHCP servers. Step 1: Confirming the Physical Layer First Before touching any settings, we always rule out physical and cabling issues. With this setup, the chain ran: ISP line in, then the RB951 WAN port, then the managed switch, then the Tenda F6 access points on different floors, then resident devices. We checked that: The ISP's incoming line was active and delivering a stable signal The cable running from the ISP termination point to the RB951's WAN port was properly seated and undamaged The RB951's WAN port link light was active The cable from the RB951's LAN port into the managed switch was solid, and the switch itself was passing traffic (link lights active on every relevant port) The cabling running from the switch out to each Tenda F6 access point was intact It's tempting to jump straight into software configuration, but a good chunk of "PPPoE won't connect" calls turn out to be a loose cable, a faulty switch port, or a bad patch lead, and in a multi-floor property, tracing that down first saves a lot of guesswork later. In this case, the physical layer was clean end to end, so we moved on. Step 2: Gathering the Correct PPPoE Credentials This is where most self-installs go wrong. PPPoE credentials are not the same as your Wi-Fi password, and they're often formatted in ways that trip people up: extra characters, case sensitivity, or a required domain suffix (like username@isp.net instead of just username). We contacted the ISP's provisioning line to confirm the exact credentials issued to the account, and verified there was no realm/domain suffix required for this particular provider. Small detail, but it's a common point of failure. Step 3: Configuring PPPoE on the RB951 An important decision in a multi-device, multi-floor setup like this is choosing exactly one device to handle the PPPoE dial-up. You never want two devices both trying to authenticate the same session, especially on a property serving 50 units. We chose the RB951 as the PPPoE client, since it's the device sitting closest to the ISP line and has the routing horsepower to handle NAT and firewall duties for the entire building. With confirmed credentials in hand, we logged into the RB951 via WinBox and: Created a new PPPoE client interface bound to the WAN-facing Ethernet port (ether1), rather than leaving it on a plain DHCP client Entered the username and password exactly as provided by the ISP, double-checking for trailing spaces, a surprisingly common issue when credentials are copy-pasted from an email Set the MTU to 1492, the standard value for PPPoE, since it accounts for the protocol's overhead compared to a normal 1500-byte Ethernet frame Set "Add Default Route" and "Use Peer DNS" so the RB951 would automatically pick up routing and DNS information from the ISP once connected Configured NAT masquerading on the PPPoE interface so devices on the LAN side could share the single public IP Enabled the connection and confirmed the PPPoE interface came up with a "running" status and a valid public IP address Step 4: Setting the Switch and Tenda F6s to Their Proper Roles With the RB951 handling PPPoE and routing, everything downstream just needed to pass traffic correctly across the building: The managed switch was configured to carry traffic cleanly from the RB951's LAN port out to every Tenda F6 access point and any wired connections on the property Each Tenda F6 was set to Access Point mode rather than its default router mode, with DHCP disabled on both units. This is a critical step, because if a Tenda F6 is left in router mode, it will try to hand out its own IP addresses and NAT traffic, creating a double-NAT situation that causes exactly the kind of "connected but no internet" symptom residents were seeing Both F6s were connected to the switch via their LAN ports (not WAN), configured with static management IPs on the same subnet as the RB951, and set to the same Wi-Fi SSID and password so residents could roam between coverage areas seamlessly as they moved around the property Step 5: Verifying the Connection End to End With the PPPoE session up on the RB951 and the F6s reconfigured as access points, we ran through our standard checks: Confirmed the RB951's PPPoE interface held a stable public IP with no repeated drops Pinged an external IP from the RB951 to confirm outbound connectivity Resolved a domain name to confirm DNS was working correctly (thanks to "Use Peer DNS" pulling the ISP's DNS servers automatically) Tested speeds on a wired device through the switch and on Wi-Fi through each Tenda F6 Walked the property between coverage areas with a phone to confirm seamless roaming on the shared SSID, with internet access holding throughout Spot-checked connectivity with a few residents on different floors to confirm the fix had resolved the outage building-wide, not just near the core router Everything came back clean. Step 6: Locking In Reliability Getting PPPoE to connect once isn't the whole job. We wanted to make sure it stayed connected. So we also: Enabled the RB951's built-in PPPoE keep-alive behaviour so a brief ISP-side blip wouldn't require a manual reboot or an on-site visit Double-checked that DHCP was fully disabled on both Tenda F6s, so there was no risk of them silently re-enabling and causing IP conflicts across the building Checked firmware/RouterOS versions on the RB951 and the F6s and applied available updates, since outdated firmware is a common cause of intermittent PPPoE drops and Wi-Fi instability Documented the full topology and working configuration (RB951 PPPoE settings, switch layout, and F6 access point settings) securely for the property manager, in case a device ever needs to be replaced or the network expanded to cover more of the building Common PPPoE Pitfalls We See Again and Again If you're attempting a PPPoE setup yourself, especially with more than one networking device on site, here are the mistakes we run into most often: Letting more than one device try to handle PPPoE. If your main router and a secondary access point (like a Tenda F6) both attempt to dial the PPPoE session, or both run DHCP and NAT, you end up with conflicts and double-NAT issues that are painful to diagnose. Leaving access points in router mode. The Tenda F6 is a capable router in its own right, but when it's meant to just extend Wi-Fi, it needs to be switched into access point mode with DHCP turned off. Otherwise it'll hand out its own conflicting IP addresses. Mistyped or copy-pasted credentials with hidden characters. Always type PPPoE credentials manually if pasting isn't working reliably. Ignoring MTU settings. An incorrect MTU on the PPPoE interface can cause some websites to load while others time out, a confusing, hard-to-diagnose symptom. No keep-alive configured on the dialing device. Without it, the connection drops and needs manual intervention, often at the worst possible time. Assuming the switch and cabling are fine without checking link lights first. Physical issues on a switch port masquerade as configuration issues constantly. Wrapping Up For this 50-unit property, the whole process, from diagnosis to a fully stable, building-wide connection, took under a few hours once we were on site. PPPoE isn't inherently complicated, but it does require getting several small details right: correct credentials, correct connection type, sensible MTU, and a reliable reconnect policy. At scale, it also means making sure every downstream device (switch, access points) is configured to complement the core router rather than compete with it. If you're dealing with a similar situation, a new ISP connection that just won't come online, whether it's a single home or a full apartment complex, it's often faster and less frustrating to have someone experienced take a look rather than guessing through router menus. That's exactly the kind of job our team at Luxenetworks handles regularly, and we're always happy to help get your connection stable and secure.