Core Platform
Nexus SupTech Ltd — UK OEM
The core software engine, licensed or granted under the commercial form you choose.
Procurement
How you buy Nexus
Data, keys, and runtime stay on the institution’s estate. Nexus SupTech Ltd remains the UK OEM. An accredited integrator deploys on site, and a local partner can run the 24/7 SLA. The commercial form — term licence, perpetual rights plus updates, managed handover, escrow, or a national-edition buyout — is chosen in the written agreement, not assumed from this page.
Delivery model
How you buy Nexus
Procurement can treat delivery as three line items: the UK core, local implementation, and sovereign operations. Written agreements govern each layer. How those layers are paid for — term, perpetual, managed handover — is the commercial menu below.
Local Partner Integration
Accredited system integrator
On-site deployment, API mapping, and data-centre integration.
Sovereign SLA & Support
24/7 managed operations
On-premise or local-cloud operations with tiered support.
Commercial form
How central banks contract Nexus
Delivery stays on-premise. The written agreement chooses the form. “Own the system” in a committee file usually means perpetual use, operational handover, and escrow — not a deed of copyright on the Nexus core.
1 · Term licence
Annual or multi-year
The current default. The institution licences the core for a stated term. Data and runtime stay on its estate. IP of the Nexus core remains with Nexus SupTech Ltd.
2 · Perpetual licence + updates
Use this version forever
A perpetual right to run the contracted version, even if the institution later stops paying. Updates, patches, and new ISO or FATF packs sit on an optional annual maintenance programme — the form RTGS and core-banking vendors use. Nothing in that stream is pushed live without the institution’s review and formal approval; see change control.
3 · Managed then handover
Build, operate, transfer operations
Nexus or the accredited SI installs and operates for an agreed term (typically several years), with knowledge transfer. Their staff then take L1/L2. Nexus stays the OEM for L3 and the release train. Operations transfer; copyright of the global Nexus core does not. A buyout, if any, is a frozen national fork only.
4 · Source escrow + step-in
Continuity if the vendor cannot
A copy of the deployed version is held with an escrow agent or in-country custodian. It releases on insolvency, prolonged breach, or sanctions. The institution does not gain a right to resell Nexus.
5 · Foreground IP
Their connectors and reports
Scheme adapters, IMTO feeds, bilingual reports, and other work built for that institution are assigned to the buyer. The Nexus core stays licensed. Their national overlay is theirs.
6 · National-edition buyout
A frozen fork, when the file requires it
A high-value option where statute or an RFP requires the Kingdom or the bank to own a national instance. They receive a frozen fork (source, docs, build) of that named edition. Copyright of the global Nexus engine stays with Nexus SupTech Ltd; other central banks can still licence the main line. This is not assignment of Nexus core, not the default, and not priced here.
IP and operations
What transfers, and what does not
The institution controls
Supervisory data, keys, and the production runtime on its estate or designated cloud. After a managed handover, day-to-day operations. Foreground IP: connectors, reports, and custom modules built for that file. With escrow, a step-in copy of the deployed version.
Nexus SupTech Ltd retains
Background IP of the Nexus core — the engine sold to more than one central bank. A national-edition buyout, if signed, is a frozen fork of a named instance; it does not assign that global engine. Use of the software is still governed only by the written licence or buyout, not by this website.
For tender files
Who the central bank contracts with
Software
Counterparty: Nexus SupTech Ltd, or an authorized master reseller.
Scope: The Nexus core engine and UK OEM relationship, under the commercial form in the written agreement (term, perpetual plus updates, managed handover, escrow, foreground IP, or national-edition buyout).
Deployment
Counterparty: Named accredited system integrator for that country or institution.
Scope: On-site installation, API mapping, and data-centre integration.
Operations
Counterparty: Local operating partner under a sovereign SLA.
Scope: 24/7 managed on-premise or local-cloud support, with Nexus SupTech Ltd engineering as the product backstop.
This page describes the delivery model and commercial options for evaluation. It is not an offer, a tender response, or a commitment to deploy. Licensed or granted use is governed by a written licence and, where applicable, implementation, operations, escrow, or buyout agreements — see our Terms of Service. Named people, infrastructure partners, and regional delivery teams are on who delivers Nexus.
Next step
Move from model to a named proposal
A procurement briefing covers the commercial form (term, perpetual plus updates, managed handover, escrow, or buyout), accredited integrator options, and the on-premise or local-cloud SLA shape for your institution.