How to buy
You buy a UK licence and a local operating model — not a catalogue of modules. Inject Group Ltd owns the IP; accredited in-country integrators deploy and support it.
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.
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 |
|---|---|
| Real-time IMTO telemetry | Compress FIU / supervisor transaction-file review from multi-week batches toward message-level alerting (seconds-scale, not month-end packs). |
| Native ISO 20022 inspection | Preserve pacs.008 / pacs.009 / camt.053 fields without lossy MT-to-MX translation, so originator/beneficiary data survives supervision. |
| Adaptive settlement delay | Hold high-risk authorised push-payment (APP) instructions before gross settlement, instead of reconstructing fraud after the credit. |
| Non-bank IMTO onboarding | Shorten supervisory onboarding of non-bank remitters from quarter-scale paper programmes toward days once local SI integration is in place. |
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.
Architecture plates for government forwarding
Civil servants forward static figures. These are illustrative architecture plates, not production screenshots and not a claim that a named central bank is live on Nexus.
pacs.008 inspection path (illustrative).Evaluation pack (under NDA)
Email team@injectgroup.com from an institutional domain. Do not attach customer PII. After NDA:
- One-page executive summary (PDF)
- High-level technical architecture specification (PDF)
- Vendor security and data-governance questionnaire pack
Files are issued by Inject Group Ltd over Google Workspace (Gmail). There is no public file dump and no third-party marketing CRM.
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.
Who is the named local implementation partner?
Named system integrators are appointed per jurisdiction under contract. Inject Group Ltd does not publish an uncontracted partner list. Ask for the SI in the RFP response.
How do we obtain a vendor security pack?
Email team@injectgroup.com with your institution, corridor, and NDA contact. Architecture specifications and one-pagers are released under NDA. See how to request a Nexus vendor pack.