Commercial / procurement briefing
Licence, implementation, and support — with a public RFP outline you can take to committee. Named local partners appear in the response, not as uncontracted logos.
How sovereign programmes are bought
Inject Group Ltd (United Kingdom, company 16282987) licenses core software. In-country accredited system integrators deploy it. Local operations and 24/7 SLAs sit with those partners, backed by Inject’s UK engineering group.
-
1. Core platform licence
Annual enterprise licence of the Nexus engine from Inject Group Ltd — UK intellectual property, not a local reseller white-label.
-
2. Local partner integration
An accredited in-country SI maps APIs, hosting, and data-centre or sovereign-cloud posture. We do not publish a partner roster until a jurisdiction contract names them.
-
3. Sovereign SLA and support
Tiered 24/7 operations via the local partner, with Inject Group Ltd retaining core engineering, security patches, and ISO 20022 / protocol evolution.
Commercial model: licence, implementation, support
| Layer | Who | What you buy |
|---|---|---|
| Core platform licence | Inject Group Ltd (UK, 16282987) | Annual enterprise licence of the Nexus engine. UK intellectual property. Warranty of title and defect repair on the licensed core, under the statement of work. |
| Implementation | Named in-country system integrator | API mapping, hosting, data-centre or sovereign-cloud posture, staff on the ground. Training for operators is in the SI statement of work. |
| Support — Standard | SI + Inject UK engineering | Business-hours local support; Inject patches the core. |
| Support — Elevated / Sovereign | SI (24/7) + Inject core | Tiered 24/7 operations via the local partner. Inject retains security patches and ISO 20022 / protocol evolution. SLA numbers are contracted, not published as marketing KPIs. |
We name the local partner in the RFP response, not on this website, until a contract exists.
Outcomes procurement committees buy — not module names
Figures below are design targets for a licensed deployment with a local SI. They are not live production SLAs and not regulator-endorsed results.
| Capability | Intended operating outcome | Design target vs status quo |
|---|---|---|
| Real-time IMTO telemetry | Message-level alerting instead of reconstructing corridors from delayed files. | T+0 inspection vs monthly / multi-week packs. |
| Alert latency | Supervisors see high-risk authorised pushes before gross settlement, not after the credit. | Seconds-scale alerts (design target), not end-of-day dumps. |
| Native ISO 20022 inspection | Preserve pacs.008 / pacs.009 / camt.053 fields without lossy MT-to-MX translation. |
Originator/beneficiary data survives supervision. |
| Non-bank IMTO onboarding | Supervisory profile, licence status, and corridor mapping in one console. | Days once SI integration is in place, vs quarter-scale paper programmes. |
| Report cycle | On-demand corridor, FX, and hold-queue extracts for FIU / board packs. | Same-session export vs month-end reconstruction. |
Named local partner model
Central banks typically require local support, local-currency billing, and in-country security clearances. Inject Group Ltd supplies the core licence and IP. Accredited Tier-1 IT integrators (for example in Dubai, Riyadh, Lagos, or Nairobi) would supply deployment headcount, local licences, and on-the-ground SLAs.
We do not name firms here until a contract exists. Listing uncontracted “partners” is a credibility failure. Procurement teams should ask for the named SI in the RFP response, not on this website.
RFP outline you can leave behind
Use these headings in a first-round questionnaire. The NDA pack on Google Drive answers them in full after signature — this page is the public checklist, not a downloadable PDF.
- Legal OEM, company number, registered office, named director.
- Licence vs local implementation vs support tiers.
- Data ownership, residency, NDPR/UK GDPR, and deletion on exit.
- Source-code escrow and audit rights (contract term, not a public dump).
- Staff clearance and in-country headcount (SI, not a fake Lagos branch).
- Local-content / in-country value: SI jobs, hosting, currency of invoice.
- Security questionnaire (Cyber Essentials evidence; ISO programme status).
- ISO 20022 message catalogue and sandbox access path.
- Training, warranty, and exit assistance.
- References: anonymised demonstration stills now; named CB references only with consent.
Architecture plates for government forwarding
Civil servants forward static figures. These are illustrative architecture plates from sample evaluation data — not a website PDF download, not production screenshots, and not a claim that a named central bank is live on Nexus. The signed architecture PDF is issued on Google Drive after NDA.
pacs.008 inspection path (illustrative).Evaluation pack (under NDA)
These files are not published on this website. Plates and stills here are sample / illustrative evaluation data. Use the hosted enquiry form from an institutional address. Do not attach customer PII. After NDA we issue the pack on Google Drive (Google Workspace):
- One-page executive summary (1-pager PDF)
- High-level technical architecture specification (architecture PDF)
- Vendor security and data-governance questionnaire
- RFP response outline (same headings as the public checklist)
There is no public PDF dump and no third-party marketing CRM. Confirmation email and a two-business-day reply SLA apply.
Studio work is a different buy path
Research, product engineering, and business support follow Discovery → Build → Operate from the UK studio. Nexus sovereign programmes follow the three-step licence model above.
Procurement questions
Who is the legal OEM behind Nexus?
Inject Group Ltd (United Kingdom, company 16282987) is the intellectual-property owner. Core software is licensed to sovereign buyers and deployed with in-country system integrators. There is no Nigerian CAC/RC number because the OEM is not a CAC-registered Lagos company.
What is the local-content story?
UK OEM licence + named local SI for implementation, 24/7 support, local-currency billing, and in-country hosting. That is the local-content model. We do not list uncontracted partner logos.
How do we obtain a vendor security pack?
Use the hosted enquiry form with your institution, corridor, and NDA contact. After NDA we issue the pack on Google Drive: 1-pager PDF, architecture PDF, security questionnaire, and RFP outline. Those files are not hosted on this website; figures here are sample evaluation data. See how to request a Nexus vendor pack.