Skip to content
CBN data localisation deadline, 1 Jan 2027: 99d 00h 31m left.Talk to us
NuxFamily

Proving compliance starts with knowing where every datum lives.

Know where every datum lives, and keep it in Nigeria

OpenMetadata for catalogue, classification and lineage; S3-compatible object storage and HDFS for the data itself. The block that gives your Chief Compliance Officer evidence instead of assurances.

  • OpenMetadata
  • MinIO
  • Ceph
  • Hadoop / HDFS

The technologies we cover

Products in this family

  • OpenMetadata

    Open-source metadata platform: data catalogue, automated discovery, classification tags, column-level lineage, data quality tests and policy enforcement.

    KubernetesPrivate cloudAir-gapped

    Official support

  • MinIO

    High-performance S3-compatible object storage in a single binary, with erasure coding, Object Lock (WORM), versioning and site replication.

    Bare metalKubernetesPrivate cloudAir-gapped

    Official support

  • Ceph

    Unified software-defined storage delivering S3 object (RGW), block (RBD) and file (CephFS) from the same cluster, for multi-petabyte estates.

    Bare metalKubernetes (Rook)Private cloud

    Official support

  • Apache Hadoop / HDFS

    Distributed file system and YARN scheduler for existing data lakes; supported in place or as the source of a migration to object storage and Iceberg.

    Bare metalPrivate cloudAir-gapped

    Official support

Why it matters for data localisation

Where this family meets the CBN directive

The CBN data-localisation directive sets a deadline of 1 January 2027 for primary processing, databases, backups, identity and access management, encryption keys and audit logs to reside in Nigeria, with no dependency on a foreign cloud. The hardest part of that obligation is not moving the data; it is proving where it is.

The journey with NuxFamily

  1. 01Assess
  2. 02Design
  3. 03Build
  4. 04Migrate
  5. 05Operate
  6. 06Evolve

Every family is delivered through the same six-stage journey, with official 24×7 support and knowledge transfer built in.

Our expertise

Credentials, not adjectives

We have built Hadoop data lakes for banks and insurers since the early 2010s, and over the past five years we have migrated most of them to S3-compatible object storage with Iceberg tables on top. Our team runs MinIO and Ceph clusters for regulated customers where retention and immutability are contractual, and has deployed OpenMetadata as the catalogue of record for data-protection programmes under GDPR. That combination of catalogue and storage is what the CBN directive now asks of Nigerian institutions.

Sectors

  • banking
  • insurance
  • retail
  • industry

10+

Years with these technologies

20+

Production deployments

8 PB of S3-compatible object storage across two data centres

Largest scale delivered

Official vendor support

Support tiers for this family

Essential

Coverage
8×5, Nigeria business hours
P1 response
4 h
  • Corrective support for OpenMetadata, MinIO, Ceph and HDFS
  • Security patches for the supported release lines
  • Access to the knowledge base and ticket portal
  • Guidance on connector, bucket and lifecycle configuration

Business

Coverage
24×7
P1 response
1 h
  • Everything in Essential
  • Proactive monitoring of storage health, capacity and replication lag
  • Quarterly health checks: erasure-set balance, scrub results, catalogue freshness
  • Version management and minor-upgrade execution
  • Assistance with new ingestion connectors and lineage coverage

Mission Critical

Most chosen
Coverage
24×7 with a named engineer
P1 response
15 min
  • Everything in Business
  • Named engineer who knows your storage and catalogue estate
  • Architecture review twice a year
  • Major-upgrade support (Ceph releases, MinIO server, OpenMetadata majors)
  • Support in CBN inspections: residency evidence and lineage extracts

CVE commitment

Version policy

Response times and tier names are indicative and confirmed contractually.

Use cases

How it is used in a regulated bank

Use case 01

Data mapping for the CBN directive

A bank must show the regulator which systems process, store and back up Nigerian customer and payment data, and where each of them runs. The information is spread across spreadsheets maintained by different teams and is out of date within weeks. The CCO wants an automated, evidenced map.

Technologies

  • OpenMetadata
  • PostgreSQL
  • Apache Kafka
  • MinIO

Expected outcome

The bank has a living inventory of in-scope data with a location for each copy, refreshed automatically. Remediation work is prioritised from the gap list rather than from memory.

Metric: Full inventory of in-scope assets within 6 weeks, with 100 % of payment-data columns tagged and located

Data mapping for the CBN directiveA bank must show the regulator which systems process, store and back up Nigerian customer and payment data, and where each of them runs. The information is spread across spreadsheets maintained by different teams and is out of date within weeks. The CCO wants an automated, evidenced map. The bank has a living inventory of in-scope data with a location for each copy, refreshed automatically. Remediation work is prioritised from the gap list rather than from memory.1Connect every sourceOpenMetadata2Discover automaticallyIngestion3Classify payment dataClassification4Attach locationCustom properties5Find the gapsOpenMetadata6Produce the evidenceReporting
  1. 1Connect every source. OpenMetadata connectors are pointed at core databases, the warehouse, Kafka, object storage buckets and the BI layer.
  2. 2Discover automatically. Schemas, tables, topics and buckets are crawled on a schedule; new assets appear without manual registration.
  3. 3Classify payment data. Pattern and sample-based classifiers tag columns holding BVN, account numbers, card data and personal identifiers; stewards confirm.
  4. 4Attach location. Each asset is tagged with hosting site, jurisdiction and provider, including backup targets and key-management location.
  5. 5Find the gaps. A saved query lists every asset tagged as payment data whose location is outside Nigeria or unknown.
  6. 6Produce the evidence. The map is exported as a signed report with timestamps and the crawler run history behind it.

Use case 02

End-to-end lineage of a regulatory report

Use case 03

Archiving and retention on S3-compatible storage in Nigeria

Reference architecture

What a compliant deployment looks like

Catalogue and storage layer with residency evidenceCatalogue and storage supported by NuxFamilySources, keys and consumersForeign component being repatriated

Migration path

From where you are to a compliant platform

  1. 01

    2-3 weeks

    Discovery

    Activities

    • Inventory data platforms, backup targets and storage contracts, including foreign cloud buckets
    • Interview data owners and compliance to agree classification categories
    • Deploy OpenMetadata in a sandbox and connect the first three sources
    • Draft the retention and immutability matrix
  2. 02

    4-6 weeks

    Catalogue rollout

    Activities

    • Connect all in-scope databases, warehouse, streams, BI and object stores
    • Run classifiers and have stewards validate payment-data tags
    • Enable OpenLineage on pipelines and parse SQL lineage
    • Define location properties and the gap query
  3. 03

    4-8 weeks

    Storage build and repatriation

    Activities

    • Deploy MinIO or Ceph across two Nigerian sites with local key management
    • Migrate foreign bucket contents with checksum verification
    • Repoint backup software and applications to the local endpoint
    • Bring HDFS under support or plan its migration to object storage
  4. 04

    2-3 weeks

    Retention and evidence

    Activities

    • Apply Object Lock and lifecycle rules per retention class
    • Register every bucket and lake path in the catalogue with its class and location
    • Produce the first residency evidence pack and lineage extracts
    • Confirm and document deletion at the foreign provider
  5. 05

    Ongoing

    Operate

    Activities

    • 24×7 support under the agreed tier
    • Quarterly restore tests and catalogue freshness review
    • Capacity planning and controlled upgrades

FAQ

Questions architects ask us

Institutions are expected to show where in-scope data is processed, stored and backed up, who can access it and where encryption keys are held. In practice that means an inventory with a location for every copy, kept current, plus the contracts and technical controls behind it. OpenMetadata gives you the inventory and the history of how it was produced. This is not legal advice; confirm the required format with your compliance function.

Over two decades

Built by the team behind the platforms of Santander, ING, Bankinter, Mapfre and Inditex

More than twenty years designing, building and operating private clouds for institutions that cannot afford to fail, and a delivery model where we stay with you from assessment to operation.

See our track record

20+

Years building private clouds

40+

Private clouds delivered

Talk to an architect about this family

Tell us where you are today and we will come back with a first view of the target architecture and the migration path.

No mailing lists, no automated follow-ups. We reply personally within one working day.