Resilience · For operations, procurement and risk
Register the suppliers, sites and shipping lanes you actually depend on. An hourly event ledger runs against that list and names which entries a live disruption touches, and through what. No supplier survey, no ERP integration, no procurement cycle.
Building the register is free. Reading live events against it is Pro.
Who this is for
If you run operations, procurement or continuity, you can name the counterparties and the sites you cannot lose. That list is the hard part and you already have it. What you do not have is anything that checks it against the world every hour.
You read the news, and you hope the item that matters surfaces near the top. The failure is not a bad call. The failure is a call made on Thursday that could have been made on Monday.
The same feeds arrive whether or not you log in. What changes is that they arrive already intersected with your list, ordered by the criticality you set, with the reason each one surfaced written next to it.
This is the same engine behind Mimir, which points it at a portfolio of holdings. Same ledger, same graph, a different book. If you are here for the investor version, that page is the one you want.
One input, and you already own it
A row is a name, a role, and how badly you would feel it. Everything else is optional and improves the match if you have it.
A form on the page: role and name, then whichever of the optional fields you have. A ticker you type is normalised to one symbol space, so BRK.B and BRK-B are the same counterparty.
Five columns, role first, parsed in the browser and imported row by row. The import reports how many of the parsed rows landed.
If you do hold equities, one click reads their filed supplier disclosures into the register as deletable, visibly inferred rows. Running it twice creates nothing new.
The register is yours and typing it is not the price of admission: creating, editing and deleting rows needs an account and nothing more. It is reading the live event ledger against them, and the one-click seed, that sit behind Pro.
Three channels, each with a stated blind spot
A match with no stated reason is a guess with good posture. Each of the three channels below is a different question, and the product prints which one fired next to every row it surfaces.
A counterparty you registered that is a listed company. The event ledger already propagates events to tickers through named mechanisms, so this is the same join a portfolio gets, pointed at your book instead.
Containment, at the granularity the event ledger actually buckets on: five regions, americas, europe, middle-east, east-asia and global. A country on the row maps onto one of them.
One of ten watched maritime passages, matched by id against the hourly AIS stress rollup: Suez, Hormuz, Bab-el-Mandeb, Malacca, Taiwan, Panama, Lombok, the Turkish straits, the Danish straits and the Cape.
Order is set on the server and never re-sorted in the browser: your criticality first, then a calibrated severity ahead of an uncalibrated one, then how many independent receipts the cluster has. A critical supplier under a mild event outranks a spectacular event nowhere near you, which is the correct answer and not the interesting one.
Read this before the demo, not after
Written down here because you will find every one of them in the first week, and a tool for continuity work that oversells in month one is worse than no tool at all.
Where this sits
The established platforms in this category do something Convexity does not: validated, part-level, multi-tier mapping. The difference that matters to a mid-market operator is not depth. It is what has to happen before anything works at all.
| Resilinc | Interos | Everstream | Convexity | |
|---|---|---|---|---|
| How your chain gets in | Supplier declarations, ERP, AI outreach | Not stated on its mapping page | Mapped against its own network data | You type or paste it |
| Depth of the map | Part to site, across tiers | Tier 2 and tier 3 companies | Sub-tier discovery, scorecards | Your rows, plus filed disclosures |
| Published price | None | None | None | $29 / mo (Pro) |
| Before it answers anything | Supplier participation or an integration | No self-serve path published | No self-serve path published | A list |
Competitor rows report what each vendor's own site says, retrieved 2026-08-28. Resilinc states visibility "down to the part-site level" on "15+ years of validated data", collected through supplier declarations, ERP integrations and AI agents that automate supplier outreach (resilinc.ai/products/multi-tier-mapping). Interos states identification of tier 2 and tier 3 companies; its mapping page states no ingestion method and carries no figures (interos.ai/solutions/supply-chain-mapping). Everstream markets sub-tier discovery and supplier scorecards (everstream.ai). Nothing here asserts what a product does beyond its own published material, and none of the three publishes a price.
If you run a supplier programme with declarations and a validated bill of materials, buy one of those. This is for the operator whose current instrument is a spreadsheet and the news, and for the long tail of sites and counterparties that never made it into the programme you do run.
One tier, published
There is no operations edition and no enterprise quote. The lens sits inside Pro, which is the tier that carries the rest of the terminal, at $29 / mo or $290 / yr.
Pricing is read from the same file the pricing page renders, so these two cannot disagree.
Twenty rows is a real register. It takes about ten minutes, and the join runs against it from the first row. Inside the terminal the lens is called Resilience, under Real economy.