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

Search and observability without sending a single log outside Nigeria.

Search, logs and text analytics that stay in the country

Apache Solr and OpenSearch, deployed and supported on your own infrastructure. Replace foreign observability SaaS, power customer search in the digital channel and run AML screening, all inside the CBN perimeter.

  • OpenSearch
  • Apache Solr
  • OpenSearch Dashboards
  • Data Prepper

The technologies we cover

Products in this family

  • OpenSearch

    Apache 2.0 search and analytics engine, the open fork of Elasticsearch 7.10, used for log management, security analytics and application search.

    Bare metalKubernetesPrivate cloudAir-gapped

    Official support

  • Apache Solr

    Mature Lucene-based search platform with SolrCloud clustering, fine-grained relevance tuning and a long track record in banking and retail catalogues.

    Bare metalKubernetesPrivate cloudAir-gapped

    Official support

  • OpenSearch Dashboards

    Visualisation, alerting and reporting layer for OpenSearch, with role-based access and audit-ready saved searches.

    KubernetesPrivate cloudAir-gapped

    Official support

  • Data Prepper & Fluent Bit

    Lightweight collection and enrichment pipelines that move logs, traces and audit events from hosts and clusters into OpenSearch.

    Bare metalKubernetesAir-gapped

    Official support

Why it matters for data localisation

Where this family meets the CBN directive

The CBN data-localisation directive requires that primary processing, databases, backups, identity and access management, encryption keys and audit logs for Nigerian financial data be kept in the country by 1 January 2027, without dependency on a foreign cloud provider. Logs are the item most often overlooked.

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 run Solr and Elasticsearch-family clusters in production for European banks, insurers and retailers since the SolrCloud era, including catalogue search for one of Europe's largest fashion retailers and log platforms for retail banks under ECB supervision. Since the licence change in 2021 we have migrated several of those estates to OpenSearch without downtime. Our engineers handle shard design, JVM tuning, relevance work and the security plugin day to day, and the same team carries the support contract.

Sectors

  • banking
  • insurance
  • retail
  • industry

12+

Years with these technologies

25+

Production deployments

40-node OpenSearch cluster indexing 20 TB of logs per day

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 OpenSearch, Solr and Dashboards
  • Security patches for the supported release lines
  • Access to the knowledge base and ticket portal
  • Guidance on index, shard and retention settings

Business

Coverage
24×7
P1 response
1 h
  • Everything in Essential
  • Proactive cluster monitoring (heap, shard balance, queue depth)
  • Quarterly health checks and capacity review
  • Version management and minor-upgrade execution
  • Relevance and pipeline tuning sessions

Mission Critical

Most chosen
Coverage
24×7 with a named engineer
P1 response
15 min
  • Everything in Business
  • Named engineer who knows your cluster
  • Architecture review twice a year
  • Major-upgrade support (Solr 8 to 9, OpenSearch 2 to 3)
  • Support during CBN inspections and evidence extraction

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

100 % local log and audit platform

A bank ships application and infrastructure logs to a foreign observability SaaS. The logs contain customer identifiers and access events, and the CBN inspection team has asked where they are stored. The institution needs an equivalent platform in Nigeria, with retention and traceability it can demonstrate.

Technologies

  • OpenSearch
  • Data Prepper
  • Fluent Bit
  • Apache Kafka
  • MinIO

Expected outcome

All logs and audit trails are produced, stored and retained inside Nigeria, with a defined retention schedule and an evidence pack the CBN can inspect. The foreign SaaS subscription is decommissioned.

Metric: Retention of 12 months searchable and 7 years archived, with the SaaS contract closed within one quarter

100 % local log and audit platformA bank ships application and infrastructure logs to a foreign observability SaaS. The logs contain customer identifiers and access events, and the CBN inspection team has asked where they are stored. The institution needs an equivalent platform in Nigeria, with retention and traceability it can demonstrate. All logs and audit trails are produced, stored and retained inside Nigeria, with a defined retention schedule and an evidence pack the CBN can inspect. The foreign SaaS subscription is decommissioned.1Collect at sourceFluent Bit2Buffer and decoupleKafka3Enrich and routeData Prepper4Index with tiersOpenSearch5Snapshot locallyMinIO6Alert and inspectOpenSearch Dashboards
  1. 1Collect at source. Fluent Bit agents on hosts and Kubernetes nodes pick up application, system and access logs without changing application code.
  2. 2Buffer and decouple. Events land on Kafka topics so that indexing load and collector load are independent and nothing is lost during maintenance.
  3. 3Enrich and route. Data Prepper parses, masks sensitive fields where required and routes events to the right index by system and criticality.
  4. 4Index with tiers. OpenSearch stores hot data on NVMe, moves warm indices to larger nodes and rolls cold data off through Index State Management.
  5. 5Snapshot locally. Daily snapshots go to S3-compatible object storage in a second Nigerian data centre for retention and disaster recovery.
  6. 6Alert and inspect. Dashboards, alerting and saved searches give operations and compliance the same view; audit access to the platform is itself logged.

Use case 02

Customer and operations search in the digital channel

Use case 03

AML and sanctions-list screening

Reference architecture

What a compliant deployment looks like

Search and log platform inside the Nigerian perimeterSearch clusters supported by NuxFamilyPipelines and consumersExternal component being replaced

Migration path

From where you are to a compliant platform

  1. 01

    2-3 weeks

    Assess

    Activities

    • Inventory every log source, index and dashboard in the current SaaS or Elasticsearch estate
    • Classify which streams contain customer or payment data
    • Measure daily ingest volume, query patterns and retention obligations
    • Agree target retention tiers with compliance and internal audit
  2. 02

    3-5 weeks

    Design and build

    Activities

    • Size the OpenSearch and Solr clusters for peak ingest plus 40 % headroom
    • Deploy on Kubernetes or bare metal in the primary Nigerian data centre
    • Configure security plugin, SSO integration and field-level masking
    • Set up snapshot repository on S3-compatible storage in the secondary site
  3. 03

    4-6 weeks

    Dual-run

    Activities

    • Ship logs to both the old platform and the new one in parallel
    • Rebuild dashboards, alerts and saved searches on OpenSearch Dashboards
    • Migrate Solr collections and re-index from source with relevance regression tests
    • Train operations and compliance users
  4. 04

    1-2 weeks

    Cut over and decommission

    Activities

    • Switch collectors to the local platform only
    • Export historical data from the SaaS provider for the retention period
    • Confirm deletion of data at the foreign provider and keep the certificate
    • Produce the localisation evidence pack
  5. 05

    Ongoing

    Operate

    Activities

    • 24×7 support under the agreed tier
    • Quarterly capacity and retention review
    • Minor upgrades on a planned cadence; major upgrades with a rehearsal cluster

FAQ

Questions architects ask us

The directive covers audit logs explicitly, and application logs frequently contain customer identifiers and transaction data that fall under primary processing. In our experience it is one of the most common findings in localisation assessments. Whether a given stream is in scope depends on its content, so we start with a classification of every log source. This is not legal advice; your compliance function should confirm the interpretation.

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.