Short answer: they are different layers, and some teams will use both. myCOI is a mature, dedicated platform for tracking certificates of insurance. Kernos exists for the moment compliance has to change behavior — when a payment either releases or holds. Here is the full comparison, including where myCOI wins.
| Dimension | myCOI | Kernos |
|---|---|---|
| Core question | "How do we collect, track, and stay on top of certificates of insurance?" | "How do we enforce compliance decisions at the moment of payment?" |
| Focus | Certificate lifecycle tracking as the product center | Compliance enforced on the payment action itself |
| Decisions | Compliance status and follow-up workflows around certificates | Staged proposals with a seven-state approval flow — the initiator cannot self-approve, enforced server-side |
| Rules | Certificate requirements tracked per subcontractor | A rules engine evaluates each certificate against requirements extracted from the contract |
| Audit | Records of certificate status over time | Append-only audit chain — every decision replayable with full context |
| Scope | Insurance certificates (certificate lifecycle + AI-assisted review via illumend) | Business objects, rules, and governed actions across payment-side workflows |
| Deployment | SaaS | Self-hosted or private cloud — your data stays in your perimeter |
Comparison reflects publicly documented capabilities as of September 2026. Both products evolve; verify against current documentation. Last updated: .
Pretending otherwise would waste your time. myCOI is an established, focused product in certificate tracking — collecting, organizing, and tracking certificates of insurance is the center of the product, and it has matured there for years. If your problem is that certificates are scattered across inboxes, expirations are missed, and no one owns the paperwork, a dedicated tracker is a rational, proven choice. myCOI has also rebranded its platform as illumend, an AI-native compliance product powered by the Lumie AI engine — the tracking DNA is the same.
The divergence is the moment of enforcement. Tracking produces status; status does not stop a payment. In a tracking-first world, an expired certificate or a missing endorsement is information that still depends on a person noticing it at exactly the right moment — the moment the payment run executes. Kernos moves the decision itself into a governed path: requirements come from the contract as objects, the rules engine compares each certificate, gaps become exceptions with owners and deadlines, and the payment stays staged until a qualified approver clears it — in a flow where the initiator cannot approve their own proposal. The difference is not what you know about the certificate. It is what your system does about it, and whether it can prove that later.
Fairness cuts both ways. Kernos is the newer product, and its certificate-tracking surface — the day-to-day ergonomics of managing thousands of certificates — is not its center of gravity; enforcement and audit are. Teams whose pain is purely logistical tracking should evaluate myCOI on its own merits. Kernos's construction compliance line is in early access, and we would rather say that plainly than oversell it.
Comparison axis: myCOI is built around certificate tracking; Kernos is built around payment-time enforcement with governed actions.
Also compare: Kernos vs TrustLayer → and Kernos vs Dify →