For journalists, analysts and anyone writing about RiskRouter
Press: what RiskRouter is, in facts you can check
Everything on this page can be checked without asking us. The figures are computed from the repository when the site is built, the same way the rest of the site states them, and each links to where you can verify it yourself.
Describing us
In one line, and in one paragraph
One line. RiskRouter is a log nobody can edit, in which a firm seals the fingerprint of a record it may one day have to defend, and anyone can later prove the record was never changed.
One paragraph. Regulated firms are asked, sometimes years later, what they advised or decided and whether the record of it has been touched since: an insurance advice note, an investment suitability statement, a credit assessment, an AI system’s decision log, a security log before a breach. RiskRouter seals a salted fingerprint of each record in an append-only log whose heads are signed, time-stamped and anchored in Bitcoin; the record itself never leaves the firm. Anyone holding the record and its receipt can check it offline with open-source verifiers, without trusting RiskRouter. It is built for the software vendors that serve regulated finance, and for AI platforms. It is a validation build, run from Brussels.
Either may be quoted as written. The name is one word with two capitals: RiskRouter.
Figures
Facts, from the repository
- First head anchored
- 13 September 2026, in Bitcoin block 967 830. How to check
- Time stamps
- Two signed heads carry RFC 3161 time stamps from DigiCert timestamp service and Sectigo timestamp service. None is a qualified time stamp under eIDAS.
- What to record, by law
- Twelve regime packs for eleven EU laws, each field mapped to the article that asks for it. Regime packs
- Industries covered
- Seventeen pages, one per kind of record people are later asked to prove. Industries
- Independent checks
- Two verifiers written separately (JavaScript and Python, standard libraries only), published test vectors and a conformance suite. Specification
- Independent witnesses
- None yet. The log is served in the format the public witness network cosigns.
- Results published by others
- None yet.
How much is recorded, and by whom, is counted live at /usage; whether the service answers, measured every ten minutes from outside, is at /status. Every claim the site makes, and where to check it: /evidence.
Not
What RiskRouter is not
- Not an insurer or an insurance intermediary, and it sells no cover. The pricing engine on the site is a worked example for developers. Regulatory position
- Not certified by anyone, and its time stamps are not qualified under eIDAS. Why
- Not a company yet: it is run by one person, Anil Jangra, with no legal entity registered, and no commercial terms are in force. What that means if you depend on it
- Not a holder of anyone’s records: it receives salted fingerprints, never the records. Data protection
RiskRouter names no customer, partner or user, because it has none it could name; please do not describe any organisation as one.
Brand
Name and logo
The mark is three linked squares, the last one filled: a chain of records whose newest entry is sealed.
Colours: ink #18191b on paper #fbfaf7, with one accent, #b3361b, for the
filled square. The type is Source Serif 4 for headings and IBM Plex for text, both open fonts.
Write
Contact
Write to anil@riskrouter.eu. You will be writing to Anil Jangra, who builds and runs RiskRouter, and the answer comes from the same person. Other ways to reach us