How Nigeria’s Digital Postcode Could Become Another Case of Nigerian Technology Sitting on Foreign Infrastructure
There is a sentence Nigerians need to stop using as if it settles the sovereignty question:
“It is a Nigerian company.”
No.
That is not enough.
There is another sentence:
“It was built by Nigerians.”
Still not enough.
And another:
“The government owns the system.”
Still not enough.
Because there is a much harder question:
Who actually controls the infrastructure on which the system runs?
That is the question Nigeria should be asking about the new National Digital Alphanumeric Postcode System.
The system is a major technological achievement. The Federal Government launched it nationally on October 1, 2026, describing it as nationwide digital addressing infrastructure capable of giving addressable buildings a precise and verifiable digital location identity. It is intended to support commerce, logistics, emergency response, financial services and public-service delivery.
Milsat, a Nigerian geospatial technology company founded by Taslim Saluadeen and Adedamola Baderinwa, has been identified as the technology company behind the system.
Milsat deserves credit.
NIPOST deserves credit.
The Ministry of Communications, Innovation and Digital Economy deserves credit for finally pushing Nigeria towards a modern addressing infrastructure.
But none of those facts answer the sovereignty question.
Because:
Built in Nigeria is not the same thing as controlled from Nigeria.
A Nigerian company is not the same thing as Nigerian infrastructure.
A Nigerian domain is not the same thing as Nigerian data residency.
And perhaps most importantly:
Owning the application is not the same thing as controlling the infrastructure underneath the application.
That distinction matters enormously when the system being built is intended to become a national digital infrastructure layer.
THIS IS NOT JUST A POSTCODE
Calling the National Digital Postcode “a postcode” makes the issue sound harmless.
It isn't.
NIPOST describes the system as an 11-character digital postcode assigned to addressable buildings across Nigeria.
The official platform says organisations can integrate with it through APIs, web and mobile SDKs and bulk access.
The system is therefore designed not merely to help Nigerians find addresses.
It is designed to become infrastructure upon which other systems can depend.
That means a bank can potentially use it.
A logistics company can use it.
An e-commerce platform can use it.
A government agency can use it.
An emergency service can use it.
A financial institution can use it.
A public-service delivery platform can use it.
A security organisation can potentially integrate it.
The Ministry itself says the system is designed to support emergency response, financial services and public-service delivery.
That changes the classification of the problem.
When you are talking about a national database capable of becoming a common location-reference layer for millions of Nigerian buildings, you are no longer talking about an ordinary commercial website.
You are talking about digital public infrastructure.
And digital public infrastructure should be judged by a much higher standard.
THE DNS EVIDENCE IS NOT THE WHOLE STORY — BUT IT IS A WARNING LIGHT
As of the October 6, 2026 investigation, public DNS observations associated with:
milsat-api.milsat.africaapi-dashboard.enumeration.africaapp-api.enumeration.africa
were reported to resolve into AWS infrastructure associated with the US East/Northern Virginia region.
More importantly, an independent technical investigation published by Space in Africa on October 3 reported that the NDAPS website and organisation dashboard were running on AWS infrastructure and that the production API gateway, api.postcode.gov.ng, was an AWS load balancer located in AWS's Ireland region, eu-west-1.
That does not, by itself, prove that the complete postcode database is physically stored in Ireland.
That distinction matters.
A DNS record identifies infrastructure.
It does not automatically reveal:
- database location;
- backup location;
- encryption-key location;
- replication architecture;
- storage buckets;
- administrator location;
- disaster-recovery location;
- or where every piece of personal data is processed.
But that is exactly why the government needs to answer the question.
Because if a national digital infrastructure platform has critical production components sitting in foreign cloud regions, Nigerians deserve to know exactly what those components are doing.
The issue is not that AWS is technologically bad.
The issue is that Nigeria may be building a strategically important national system on infrastructure that Nigeria does not physically own or independently control.
And that is a sovereignty problem.
NIGERIA HAS JUST ANNOUNCED A DIGITAL CLOUD POLICY — SO WHY IS THIS QUESTION EVEN NECESSARY?
Here is where the story becomes particularly uncomfortable.
On August 17, 2026, the Federal Government unveiled its National Digital Cloud Policy.
The policy was explicitly presented as a framework for:
- domestic cloud capacity;
- data infrastructure;
- digital sovereignty;
- government cloud transformation;
- indigenous digital capability;
- and Nigeria becoming a regional digital services and hosting hub.
The Federal Government's own announcement says the policy is intended to move Nigeria beyond simply consuming global cloud services and towards building domestic infrastructure, investment, skills and digital-service exports.
That is the right direction.
But it creates an obvious question.
If Nigeria is now serious about digital sovereignty, why should a newly launched national digital infrastructure platform be dependent on foreign cloud infrastructure at precisely the moment Nigeria is announcing that it wants to build domestic cloud capacity?
That contradiction deserves an answer.
THIS IS THE PART PEOPLE KEEP MISSING: CLOUD IS NOT JUST STORAGE
When Nigerians hear:
“The data is in the cloud.”
Many imagine some magical invisible place called “the cloud.”
There is no cloud.
There are buildings.
Servers.
Storage systems.
Networking equipment.
Power systems.
Security systems.
Physical facilities.
Administrators.
Companies.
Contracts.
Jurisdictions.
And laws.
The cloud is simply somebody else's infrastructure being made available as a service.
There is nothing inherently wrong with that.
Businesses do it every day.
But a government must ask a different question:
Whose infrastructure is it, under whose jurisdiction, and who retains ultimate operational control?
That question becomes more important when the system contains nationally significant location information.
NIPOST'S OWN PRIVACY POLICY MAKES THIS MORE SERIOUS
The strongest evidence does not actually come from the DNS investigation.
It comes from NIPOST itself.
The current NIPOST NDAPS privacy policy says the system may process:
- names;
- telephone numbers;
- addresses;
- geographic coordinates;
- postcode information;
- address-correction information;
- postcode assignment history;
- authentication information;
- IP addresses;
- device information;
- system logs;
- API credentials;
- transaction information;
- communications;
- address-correction submissions;
- and potentially NIN-related information where legally authorised.
That is a serious dataset.
The same policy explicitly says NIPOST may disclose or make personal data available to cloud and technology service providers, cybersecurity providers, government agencies, enterprise customers, API customers and other authorised parties.
And then comes the critical section.
NIPOST explicitly has a section titled:
“International data transfers.”
It states that where personal data is transferred to, accessed from or processed in a jurisdiction outside Nigeria, NIPOST will implement the safeguards and conditions required by Nigerian data-protection law.
In other words, the government's own privacy document does not pretend that international processing is impossible.
It expressly contemplates it.
So the argument is no longer:
“Maybe foreign infrastructure is involved.”
The public documentation tells us that cloud providers and international processing are part of the architecture's legal framework.
The unanswered question is:
Exactly what Nigerian data goes where, under whose control, and why?
AND THAT IS WHERE THE SOVEREIGNTY PROBLEM STARTS
Suppose the government says:
“Don't worry. The cloud provider is secure.”
That misses the point.
Security and sovereignty are related but different concepts.
A foreign cloud provider can be extremely secure.
It can have better physical security than a poorly managed Nigerian server farm.
It can have better redundancy.
It can have better cybersecurity.
It can have better uptime.
None of that answers the sovereignty question.
Because sovereignty asks:
Who has ultimate control?
A Nigerian government system should ideally have a clearly documented chain of control over:
- the cloud account;
- administrator privileges;
- encryption keys;
- database credentials;
- backups;
- infrastructure configuration;
- disaster recovery;
- logs;
- source code;
- deployment pipelines;
- and migration capability.
If a Nigerian government agency cannot independently reproduce its own system outside a particular vendor's environment, then it is not completely sovereign over that system.
It is dependent.
WHO CONTROLS THE KEYS?
This is perhaps the single most important technical question Nigerians should ask.
Not:
“Is the server in AWS?”
But:
Who controls the encryption keys?
If Nigeria controls the keys, that is important.
If the Nigerian government controls the cloud account and the keys, even while using foreign infrastructure, the sovereignty position is stronger.
If a private contractor controls the infrastructure account, that is weaker.
If a contractor controls the keys, weaker again.
If a foreign infrastructure provider ultimately controls critical parts of the access architecture, the sovereignty problem becomes much more serious.
And Nigerians currently do not have enough public information to answer these questions.
That is unacceptable for infrastructure being positioned as national digital infrastructure.
WHO GETS ADMIN ACCESS?
The public also needs to know who has privileged access.
Imagine a database containing millions of geographic records.
Who can enter the administrative console?
NIPOST?
Galaxy Backbone?
Milsat?
A subcontractor?
Cloud administrators?
Foreign technical support?
Cybersecurity vendors?
Multiple companies?
How many privileged accounts exist?
Are they Nigerian government-controlled?
Are all administrator actions logged?
Can a contractor create another administrator?
Can an administrator export an entire database?
Can someone access production without Nigerian government approval?
These questions are more important than whether the company is proudly Nigerian.
Because one compromised privileged account can matter more than the nationality of the company logo on the website.
AND THEN THERE IS THE EXIT PROBLEM
Every government technology contract should have an exit strategy.
Not an exit strategy written after disaster strikes.
An exit strategy written before deployment.
Ask the simplest question:
If Nigeria terminates the relationship with its technology provider tomorrow, can Nigeria take the system and run it somewhere else?
Can the complete database be exported?
Can the database schema be reproduced?
Can the APIs be redeployed?
Can the infrastructure be rebuilt?
Are the deployment scripts available?
Are the encryption keys transferable?
Are the backups portable?
Can Nigeria migrate to another cloud?
Can Nigeria migrate to a Nigerian data centre?
Can Nigeria run the system through Galaxy Backbone?
Can another Nigerian company take over?
How long would it take?
One day?
One week?
Six months?
Two years?
The answer tells you much more about sovereignty than the word “Nigerian” ever will.
VENDOR LOCK-IN IS THE QUIET FORM OF COLONIALISM
This is where Nigeria needs to think beyond today's procurement cycle.
Imagine that thousands of organisations integrate the Digital Postcode API.
Banks depend on it.
Fintechs depend on it.
Logistics companies depend on it.
Government agencies depend on it.
Emergency systems depend on it.
E-commerce platforms depend on it.
The more successful the platform becomes, the more difficult it becomes to replace.
This creates network effects.
And eventually the cost of leaving becomes enormous.
That is vendor lock-in.
The vendor does not need to threaten Nigeria.
Nigeria simply becomes dependent on the architecture.
The longer the system runs, the harder migration becomes.
That is how technological dependency works.
It is usually not dramatic.
Nobody announces:
“Today we surrender our sovereignty.”
Instead, somebody says:
“This cloud service is easier.”
Then:
“This provider is cheaper.”
Then:
“The developers already know AWS.”
Then:
“Migration would be expensive.”
Then:
“Everything depends on it.”
Ten years later, the country discovers that replacing the provider has become almost impossible.
That is the danger.
NIGERIA IS ALREADY SPENDING HUGE AMOUNTS OF MONEY ON DIGITAL INFRASTRUCTURE
This makes the foreign-cloud question even more important.
If Nigeria is going to spend public money developing national digital infrastructure, the economic benefit should not stop at the application layer.
The infrastructure itself should create Nigerian capacity.
Money should support:
- Nigerian data centres;
- Nigerian cloud providers;
- Nigerian network engineers;
- Nigerian cybersecurity professionals;
- Nigerian systems administrators;
- Nigerian storage infrastructure;
- Nigerian disaster-recovery facilities;
- Nigerian cloud-management expertise;
- Nigerian hardware maintenance ecosystems.
Otherwise Nigeria risks doing the most expensive part of digital transformation while allowing the infrastructure rents to leave the country.
THE DOLLAR PROBLEM
There is another very Nigerian reason to care.
Foreign cloud infrastructure is generally priced through global commercial structures.
That means Nigeria can become exposed to foreign-currency costs.
A national system becomes more popular.
Usage rises.
API calls rise.
Storage rises.
Backups rise.
Compute rises.
Traffic rises.
Security services rise.
Monitoring rises.
Suddenly the government's infrastructure bill becomes more exposed to foreign exchange.
This is particularly important because the Digital Postcode is explicitly designed to become an API and integration platform.
It is not just a website.
If Nigeria succeeds in making the system widely adopted, its infrastructure requirements will grow.
The more successful it becomes, the more Nigeria must ask:
Where is the economic value of that infrastructure expenditure going?
THE GOVERNMENT IS TRYING TO BUILD A CLOUD INDUSTRY — SO GOVERNMENT SHOULD BE THE ANCHOR CUSTOMER
This is where Nigeria could turn the problem into an opportunity.
The government does not need to ban AWS.
It does not need to ban Azure.
It does not need to ban Google Cloud.
That would be foolish.
Global cloud providers can be valuable partners.
But Nigeria should use its enormous government workload as an anchor for domestic infrastructure.
Government should create predictable demand for Nigerian data centres and cloud capacity.
Instead of every ministry independently purchasing foreign cloud services, government can aggregate demand.
That is actually one of the purposes of the National Digital Cloud Policy.
Galaxy Backbone is expected to play an important role in coordinating government cloud demand.
So why not make national digital infrastructure the first major proof that this model works?
THERE IS AN EVEN BIGGER PROBLEM: NATIONAL LOCATION DATA IS STRATEGIC DATA
People may say:
“What's so sensitive about a postcode? The postcode isn't secret.”
That argument misses the dataset.
One postcode isn't particularly sensitive.
A national database containing millions of mapped buildings is different.
Now imagine connecting it with:
- business registrations;
- financial accounts;
- tax records;
- identity systems;
- property records;
- telecommunications records;
- health facilities;
- schools;
- government offices;
- logistics data;
- emergency records;
- security information.
Suddenly location becomes the connective tissue between multiple systems.
That is the strategic value.
Location intelligence can reveal:
- where businesses operate;
- where government facilities exist;
- where infrastructure is concentrated;
- where communities are located;
- how settlements are structured;
- where critical facilities sit;
- and how other datasets relate geographically.
The government itself has said the system can support security and public safety.
That should automatically trigger a much higher sovereignty standard.
NIGERIA'S DATA-PROTECTION LAW MAKES CONTROL EVEN MORE IMPORTANT
The Nigeria Data Protection Act 2023 gives data subjects a right to erasure of their personal data under Section 34(1)(d).
This matters because deletion is not simply:
“Press delete on the database.”
Modern systems have:
- primary databases;
- replicas;
- backups;
- logs;
- caches;
- analytics stores;
- disaster-recovery environments;
- security systems;
- third-party processors.
If data crosses several environments, the controller must know where it exists and who processes it.
The NDPC's regulatory framework places significant emphasis on accountability, data-processing agreements, cross-border transfers and data sovereignty.
The Commission's own materials recognise that international transfers require appropriate safeguards.
Therefore, if Nigerian government data is being processed through foreign infrastructure, the question is not merely whether the transfer is legally possible.
The question is:
Can Nigeria actually demonstrate control over the complete lifecycle of the data?
Collection.
Processing.
Storage.
Replication.
Backup.
Access.
Transfer.
Retention.
Deletion.
That is the standard a sovereign digital system should meet.
SECTION 34(1)(D) IS NOT A TECHNICAL FOOTNOTE
The right to erasure becomes especially interesting in a national location system.
Suppose a person asks for lawful erasure.
Where exactly is their data?
If the system is distributed across infrastructure controlled by multiple entities, the government must have a clear process for ensuring that the relevant data is removed or appropriately handled across all applicable environments.
That requires:
data mapping.
processor mapping.
subprocessor mapping.
backup policies.
retention policies.
deletion policies.
audit trails.
The Nigerian Data Protection Act is not asking government agencies to simply say:
“Trust us.”
The entire modern data-protection model is based on accountability.
So Nigeria should apply that same accountability principle to its national digital infrastructure.
THE MILSAT PRIVACY POLICY PROBLEM IS SMALL — BUT SYMBOLIC
Now to Milsat.
Milsat's public privacy policy still identifies the Nigerian Data Protection Bureau (NDPB) as the supervisory authority and gives info@ndpb.gov.ng as the complaint address.
That is outdated.
Nigeria's current statutory data-protection regulator is the Nigeria Data Protection Commission, established under the Nigeria Data Protection Act 2023.
This does not prove that Milsat is mishandling Nigerian data.
It does not prove that the postcode platform is non-compliant.
It does not prove a security breach.
But it raises a legitimate governance question:
Why is a company associated with major government geospatial and enumeration infrastructure still publishing a privacy policy that points citizens toward a regulator that no longer exists in that form?
For an ordinary small company, someone might call this a website-maintenance mistake.
For a company involved in national location and government systems, it should be corrected immediately.
Because documentation is part of governance.
THIS IS ALSO WHY “THE COMPANY IS REGISTERED WITH NDPC” IS NOT ENOUGH
A registration record is useful.
But registration does not answer operational questions.
It does not necessarily tell the public:
- where production data is hosted;
- where backups are hosted;
- who holds encryption keys;
- who has root access;
- which subcontractors have access;
- which cloud regions are used;
- how international transfers occur;
- how data is deleted;
- how migration works;
- whether Nigeria can operate the platform without the original vendor.
A company can be properly registered with a data regulator and still have an architecture that raises legitimate sovereignty questions.
Compliance paperwork and infrastructure sovereignty are related.
They are not the same thing.
THE MOST INTERESTING CLUE IS THAT THE INFRASTRUCTURE APPEARS HYBRID
The public infrastructure footprint reported around NIPOST appears to include both Nigerian-hosted and foreign-cloud components.
Some postcode-related endpoints have been observed pointing towards Galaxy Backbone infrastructure in Abuja.
Other components have been observed on AWS.
That hybrid architecture is not automatically wrong.
In fact, hybrid cloud can be an excellent architecture.
But the public needs to understand which layer sits where.
If:
- public website = foreign cloud;
- API gateway = foreign cloud;
- database = Nigerian infrastructure;
- backups = Nigerian infrastructure;
- encryption keys = Nigeria;
then the sovereignty situation is very different.
But if:
- application = foreign cloud;
- API = foreign cloud;
- database = foreign cloud;
- backups = foreign cloud;
- keys = vendor-controlled;
- administrators = vendor-controlled;
then Nigeria has a much bigger problem.
That distinction cannot be determined simply from DNS.
The government should disclose it.
THE WORST POSSIBLE ANSWER IS “EVERYBODY USES AWS”
That is not a national strategy.
Everybody uses something.
Banks use foreign technology.
Telecommunications companies use foreign technology.
Airlines use foreign technology.
Hospitals use foreign technology.
The question is not whether foreign technology exists.
The question is where Nigeria draws the line.
A national postcode system should be somewhere near that line.
A national identity system should be near that line.
National security systems should be beyond that line.
Critical infrastructure should be beyond that line.
Government data containing sensitive personal information should have clearly defined sovereignty requirements.
That is what serious countries do.
NIGERIA DOES NOT NEED TO BUILD EVERY SERVER
Some people will respond:
“So you want Nigeria to manufacture servers?”
No.
That is a straw man.
Digital sovereignty does not mean manufacturing every processor.
Nigeria can buy:
- Dell;
- HP;
- Lenovo;
- Cisco;
- Nvidia;
- AMD;
- Intel;
- storage systems;
- networking equipment.
There is nothing wrong with using foreign hardware.
The important thing is who controls the infrastructure and jurisdiction in which the data resides.
A Nigerian data centre can contain equipment manufactured by American, Chinese, Taiwanese, European or other companies.
The infrastructure can still be under Nigerian legal and operational control.
That is the difference.
BUILDING SERVER FARMS IN NIGERIA IS NOT “OLD SCHOOL”
Nigeria needs more data centres.
Not because servers inside Nigeria are automatically safer.
They are not.
A badly designed Nigerian data centre can be less secure than AWS.
But Nigeria should build professional domestic infrastructure with:
- multiple availability zones;
- independent power;
- renewable energy where practical;
- redundant fibre;
- physical security;
- professional SOC operations;
- disaster recovery;
- geographic redundancy;
- international connectivity;
- strong encryption;
- independent audits.
That creates capacity.
It creates jobs.
It creates technical expertise.
It creates domestic resilience.
And it gives the Nigerian government something extremely important:
an alternative.
THE ALTERNATIVE IS WHAT CREATES REAL SOVEREIGNTY
A country does not become sovereign because it refuses foreign technology.
It becomes sovereign because it has alternatives.
If Nigeria can operate on AWS today but move to Galaxy Backbone tomorrow, that is flexibility.
If Nigeria can operate on one Nigerian cloud provider and migrate to another, that is flexibility.
If Nigeria can run its core databases in a government-controlled environment while using foreign cloud services for non-sensitive workloads, that is flexibility.
If Nigeria has no realistic alternative, it is dependency.
The goal should therefore not be:
No AWS.
The goal should be:
Nigeria must never be unable to leave AWS.
That is a much smarter position.
THE REAL FEAR IS NOT TODAY'S OUTAGE
People often think sovereignty matters only if AWS goes down.
That is too narrow.
The real risk is structural.
What if the vendor raises prices?
What if Nigeria's currency collapses further?
What if a contract dispute occurs?
What if the vendor terminates an account?
What if a subcontractor is compromised?
What if a foreign regulator demands information?
What if geopolitical tensions change?
What if Nigeria introduces a new data-localisation law?
What if the system becomes classified?
What if the government needs to move the database urgently?
What if the vendor relationship ends?
What if the Nigerian company maintaining the platform disappears?
What if a new administration wants a different provider?
A sovereign system needs answers to all of those questions.
AND THIS IS WHY THE TIMING MATTERS
Nigeria has not merely launched a postcode.
It has launched the foundation of a location ecosystem.
Once millions of Nigerians begin using the codes, once businesses integrate the API, once government agencies depend on the database and once private companies build services around it, the architecture becomes difficult to change.
The time to demand portability is before dependency becomes irreversible.
The time to demand domestic control is before the system becomes critical.
The time to define data residency is before millions of records flow through the infrastructure.
The time to build Nigerian alternatives is before Nigeria needs them.
Not after.
THE GOVERNMENT SHOULD ANSWER THESE QUESTIONS PUBLICLY
This investigation does not require anyone to accuse Milsat or NIPOST of wrongdoing.
The questions are technical and legitimate.
1. Where is the NDAPS production database physically hosted?
Nigeria?
AWS Ireland?
AWS United States?
Galaxy Backbone?
Another provider?
A combination?
2. Where are backups stored?
3. Where is disaster recovery located?
4. Who controls the encryption keys?
5. Who has production administrator privileges?
6. Are those privileges controlled by NIPOST?
7. Can Milsat independently access production?
8. Can any foreign cloud-provider personnel technically access the environment?
9. Which subprocessors process NDAPS data?
10. What data is transferred outside Nigeria?
11. Under what legal mechanism?
12. What data remains exclusively in Nigeria?
13. How long is personal data retained?
14. How does Section 34(1)(d) erasure work across production, replicas and backups?
15. What happens when the Milsat contract ends?
16. Can NIPOST migrate the complete platform without Milsat?
17. Can NIPOST migrate the platform from AWS to Nigerian infrastructure?
18. Has that migration actually been tested?
19. Who owns the infrastructure-as-code?
20. Who owns the deployment credentials?
21. Who owns the source code?
22. Who owns the database?
23. Who owns the postcode dataset?
24. Has a Data Protection Impact Assessment been completed?
25. Under Nigeria's new National Digital Cloud Policy, how has NDAPS been classified?
Those questions would settle much of this debate.
AND THE MINISTER SHOULD WELCOME THESE QUESTIONS
Bosun Tijani has made digital infrastructure one of the central themes of his ministry.
His ministry has now launched a national cloud policy explicitly talking about digital sovereignty.
That is exactly why scrutiny should not be interpreted as hostility.
If Nigeria wants to become a digital infrastructure hub, it must demonstrate that it understands infrastructure sovereignty.
The minister should be able to answer:
“Yes, we use AWS for these components.”
Then explain why.
Or:
“No, the database is entirely Nigerian.”
Then demonstrate it.
Or:
“It is hybrid.”
Then explain the architecture.
Transparency would solve much of the controversy.
Silence will not.
NIGERIA SHOULD NOT OUTSOURCE ITS DIGITAL SOVEREIGNTY BY ACCIDENT
This is the larger lesson.
Nigeria spent decades allowing critical economic infrastructure to become dependent on foreign capital, foreign technology and foreign expertise.
The digital economy gives Nigeria another opportunity.
This time, the country can choose differently.
Nigeria has:
- engineers;
- software developers;
- geospatial experts;
- data scientists;
- telecommunications companies;
- data centres;
- cloud companies;
- cybersecurity professionals;
- universities;
- enormous domestic demand.
What Nigeria lacks is not necessarily talent.
It lacks sufficient scale, coordination and long-term infrastructure policy.
That is what government should fix.
THE POSTCODE COULD BECOME ONE OF NIGERIA'S MOST IMPORTANT DIGITAL ASSETS
That is precisely why Nigerians should care about where it lives.
Imagine Nigeria in 2035.
A person registers a company.
The company receives a digital location.
A bank verifies that location.
A logistics company delivers to it.
An insurance company prices risk around it.
Emergency services locate it.
A government agency uses it.
A fintech platform links an account to it.
A public-service database references it.
A security operation queries it.
All of those systems depend on the same location layer.
At that point, the postcode isn't merely a postcode.
It is digital infrastructure underneath the Nigerian economy.
And if that infrastructure depends on an external provider in another jurisdiction, Nigeria has created a strategic dependency that could become extraordinarily difficult to unwind.
THE FINAL QUESTION IS NOT “WHY AWS?”
It is:
Why doesn't Nigeria control its own critical infrastructure?
AWS is not the villain.
Azure is not the villain.
Google Cloud is not the villain.
Foreign technology is not automatically bad.
The problem is unmanaged dependency.
If Nigeria wants to use foreign cloud infrastructure, fine.
But critical government systems should have:
Nigerian-controlled keys.
Nigerian-controlled accounts.
Nigerian-controlled backups.
Nigerian disaster recovery.
Nigerian data-centre alternatives.
Open standards.
Portable databases.
Documented exit plans.
Tested migration procedures.
Transparent data-location policies.
Clear processor and subprocessor accountability.
And above all:
Nigeria must be able to take the system home.
BUILT IN NIGERIA IS ONLY THE FIRST STEP
Milsat being Nigerian is good.
NIPOST owning the national platform is good.
Nigerian engineers developing geospatial technology is good.
The national postcode itself is good.
But Nigerians should stop allowing those facts to end the conversation.
Because the next question is harder:
Where does the technology actually run?
Then:
Who controls it?
Then:
Who controls the keys?
Then:
Who can access it?
Then:
Where are the backups?
Then:
Can Nigeria leave?
Then:
Can Nigeria operate it without the foreign provider?
If Nigeria cannot answer those questions confidently, then calling the system “Nigerian” is incomplete.
It may be Nigerian software.
It may be Nigerian intellectual property.
It may be Nigerian entrepreneurship.
But sovereignty is about control.
And Nigeria must not repeat the old pattern in digital form:
Nigerian talent builds it.
Nigerian government pays for it.
Nigerian citizens generate the data.
But the critical infrastructure underneath remains somewhere else.
That is not digital sovereignty.
That is digital dependency wearing a Nigerian jersey.
Nigeria has an opportunity to build something much better.
Build the technology here.
Host the critical data here.
Control the keys here.
Train the people here.
Keep the backups here.
Build the alternatives here.
And make sure Nigeria can walk away from every vendor without losing its digital infrastructure.
Because “Built in Nigeria,” “Nigerian company,” and “controlled from Nigeria” are not the same sentence.
And pretending they are is how countries lose sovereignty without ever signing it away.
Comments
Post a Comment