On-premises PaaS and developer platforms for Nigerian banks

Cloud Foundry remains the most complete cf push experience for teams that want to deploy code without managing containers, and it is maintained by the Cloud Foundry Foundation with commercial backing from Broadcom through Tanzu Platform. Korifi brings that same developer contract onto Kubernetes, so an institution can standardise on Kubernetes underneath while keeping the platform workflow. We support both paths and help you choose based on your estate.

The directive requires the processing environment, databases, backups, IAM, encryption keys and audit logs for payment data to be inside Nigeria with no foreign cloud dependency. A PaaS on a Nigerian private cloud keeps the build, runtime, credentials and audit stream within that perimeter, and brokered services keep data on the local data platform. The catalogue also gives you the application inventory a data-mapping exercise requires. This is context, not legal advice.

Tanzu Platform for Cloud Foundry is the commercial, vendor-supported distribution with additional tooling and certified integrations. Cloud Foundry OSS is the upstream project deployed with BOSH on your hypervisor. Korifi reimplements the Cloud Foundry API on Kubernetes without BOSH, which suits institutions already standardising on Kubernetes. All three give developers the same cf push workflow.

Yes. The PaaS is a paved road, not a wall. Teams with a container-native workflow deploy to the Kubernetes family directly, and Backstage presents both paths in the same catalogue with the same ownership and compliance metadata. The choice is made per application, not for the whole bank.

NuxFamily supports the platform control plane, runtime cells, routers, brokers, buildpacks and Backstage as deployed, with the response times of your tier. Where a Tanzu subscription exists we operate it and escalate to Broadcom when a fix requires vendor changes. The scope of L1-L3 responsibility is defined in the support agreement.

A rewrite replaces the whole system in one cutover and hides its risk until the end. The strangler pattern moves one capability at a time behind a routing facade, so each step is small, measurable and reversible. The monolith stays in service throughout, which matters when the deadline is fixed and the core cannot be paused.

Yes. Tanzu Platform, Cloud Foundry OSS and Korifi can be installed and updated from internal mirrors, and buildpacks and base images are delivered as signed bundles. Backstage plugins and documentation are hosted internally. No component requires outbound internet access at runtime.