The trusted front door

Know exactly who you're dealing with, on day 0, and every day after.

KNECT is RUBIQ's onboarding engine: it verifies the customers, suppliers and employees entering your business, scores their risk in one defensible record, and keeps watching long after the contract is signed, without you becoming the place their identity data gets stolen from.

  • VerifyIdentity, sanctions, documents and more, weighed on many signals, not one.
  • DecideEvery finding aggregated into one viability report, ready for sign-off.
  • MonitorA director resigns, a VAT lapses, and you're the first to know.
KNECT customer screening dashboard: a portfolio of onboarded entities with their screening status, enhanced-due-diligence breakdown and which counterparties are due for a refresh.
KNECT screening dashboard · sample data
Built for
  • KYC / KYB
  • AML & sanctions
  • POPIA
  • GDPR
ISO 27001:2022 Certification Ready · POPIA & GDPR aligned

Onboarding today is a maze of email, PDFs and spreadsheets.

The before

Three teams, three inboxes, no single record anyone can stand behind. The cost isn't only the wasted weeks. It's the liability you keep and the answer you can't give.

  1. Operations

    The same documents, chased for weeks.

    Registration, VAT, director and FICA documents get re-collected by email across siloed teams. Weeks pass per counterparty before anyone can safely transact.

  2. The CFO

    A pile of ID copies you're now liable for.

    Every identity document you store makes you a bigger honeypot. Centralised PII is breach exposure you never chose, and it never stops being your problem.

  3. Compliance

    A decision you can't defend later.

    Gut-feel calls, an inconsistent audit trail, and point-in-time checks that are stale the day after. When the regulator asks how you knew, there's no single record to show.

How KNECT works

Hold the key, not the data.
Then never stop watching.

Most onboarding tools keep a copy of your customer's identity, and quietly hand you the liability. KNECT works the other way around: the data stays with the people it belongs to, and it doesn't go stale the day the contract is signed.

The principle · sovereign custody
The subject keeps custody
Customers and suppliers load their data into their own secure vault. Their PII is never stored in the KNECT app layer, so it isn't yours to lose.
You get a verified answer, not the data
Consent is granted through a token that is authorized, traceable and revocable. You get the verification result; the raw documents stay where they belong.

Fewer copies of sensitive data. Less to lose.

The custody model
The subject's vaultTheir PII loads here, and stays here
PII held by them
A consent tokenAuthorized · traceable · revocable
Access, not custody
KNECT gets a verified answerNo copy of their data kept in the app
Verified
Data minimization by design · POPIA Condition 7 · GDPR Article 25
Over the whole relationship 4 stages

Onboarding isn't a one-time check that's stale the next morning. KNECT runs the whole relationship: who you let in, how sure you are, and whether that's still true a year later.

  1. Invite & intake

    Onboarding that starts with an invitation, not a form.

    Invite-based onboarding stops duplicate accounts before they happen. White-label portals carry your brand, and registration, VAT, director and FICA documents land in one structured record instead of five inboxes.

    In view: the intake checklist, completeness tracked as each document arrives.

  2. Verify

    Trust scored on many signals, not one.

    Identity, entity verification, sanctions, adverse media, document integrity and your own internal rules resolve into a single risk score. A credit check sees one thing. KNECT sees the whole counterparty, and routes the doubtful item to a person.

    In view: several screening signals composited into one risk score.

  3. Decide

    One defensible record, ready for sign-off.

    Every finding aggregates into the viability report, KNECT's flagship output: one document an executive can approve and an auditor can archive. The decision stays yours; the evidence is already assembled and timestamped.

    In view: a viability report cleared for onboarding, sample data.

  4. Monitor

    Trust that doesn't expire.

    Day 0 is the start, not the end. A director resigns or a VAT status lapses, and KNECT flags it and triggers a re-screen. Renewals fire on schedule. Every action is timestamped and evidence-linked, so the record stays current and defensible.

    In view: live alerts and an audit trail, kept since onboarding.

Both sides of the business

Different doors, one standard of trust.

The counterparty you sell to and the one you buy from ask different questions of you. KNECT gives each its own portal, then runs both through one engine, so your standard never bends to the door someone came through.

Revenue side · sales

Customer Portal

Are they who they say, and will they pay?

Directors and the entity verified against the registries, then sanctions, adverse media and documents weighed together.

Approved to transact

One engine underneath Whichever door they came through, every counterparty runs through the same multi-factor model and resolves to one risk score and one defensible record.

Supply side · procurement

Supplier Portal

Can you depend on them, and are they clean?

They consent, their compliance documents land in one record, then viability and dependency risk are scored.

Cleared to contract

KNECT is the front door of the Golden Thread: every entity KAIRO later governs and CORA later transacts with is validated here first, then carried forward on one continuous record. KNECT stays operational; the board-level view is ARI's job inside KAIRO.

Proof you can
stand behind.

Proof & trust

A real screening record, a privacy posture designed around the law, and the certifications we've actually earned. A named customer story when it's signed off, not a quote we can't stand behind.

Customer story · in progress

A named onboarding outcome is coming, with permission to publish.

We would rather connect you with a team running KNECT today than write a testimonial we can't back. Ask for a live reference when you book a demo.

Ask for a live reference
A KNECT screening record for a sample entity: its risk signals, a completed screening checklist and director-verification status, assembled into one defensible record.
KNECT screening record · sample data

Privacy posture · by design

POPIA · Condition 7 Security Safeguards

The subject's vault secures PII against loss and unauthorized access, by design.

GDPR · Article 25 By design & default

Data minimization and consent are built into the architecture, not bolted on.

  • ISO 27001:2022Certification Ready
  • POPIAaligned
  • GDPRaligned

ISO 27001:2022 Certification Ready · POPIA & GDPR aligned

How we secure and govern data

Questions, answered

The short version.

Where is my customer's data actually stored?

In the customer's own sovereign identity vault, not in the KNECT application layer. The subject loads their PII into their vault and grants KNECT access through a consent token that is authorized, traceable and revocable. KNECT gets a verified answer; you don't end up holding a copy of their identity documents.

What does KNECT screen against?

Many signals, not one: identity verification, entity verification, sanctions and PEP lists, adverse media, document integrity, and your own internal rules. They composite into a single risk score, and anything doubtful is routed to a person rather than auto-decided.

How is this different from a credit check?

A credit check is a single point-in-time signal. KNECT is multi-factor and continuous: it weighs identity, sanctions, adverse media and documents together, produces a defensible record rather than a number, and keeps watching after onboarding instead of going stale the next day.

What happens after someone is onboarded?

Monitoring continues from day 0. If a director resigns or a VAT status lapses, KNECT flags it and can trigger a re-screen; renewals fire on schedule; and every action is timestamped and evidence-linked. The record stays current, so trust doesn't expire the moment the contract is signed.

Can KNECT screen our own employees too?

Yes. Employees are a third counterparty the same engine screens: pre-employment checks run through the same multi-factor model as customers and suppliers, and new hires onboard into their own sovereign vault rather than a copy held on your servers. It is the same lifecycle, not a separate system, and it is the trust foundation under RUBIQ's talent management solution.

Is KNECT POPIA and GDPR compliant?

KNECT is designed around POPIA Condition 7 (Security Safeguards) and GDPR Article 25 (data protection by design and by default): the sovereign vault, data minimization and consent are built into the architecture. RUBIQ itself is ISO 27001:2022 Certification Ready and POPIA and GDPR aligned.

Ready when you are

Start the thread.
Verify your first
counterparty.

A 30-minute discovery call about the way you actually onboard, customer side and supplier side. We scope the intake, the screening engine, the viability report and the monitoring that keeps it true, then arrange a demo on your own flow.

No public pricing yet. Prefer a figure first? Request a quote.