iyedy docs, home
FR Lire en françaisOpen iyedy (opens in a new tab)

Use the technology radar

The technology radar is your workspace's list of technologies, each with a ring and its lifecycle dates. Once a technology is on it, the checks flag every element that runs a version past or near its end of life, or a technology you put on hold.

On this page
Guide · 6 minAll plansUpdated 29 Oct 2026

Before you start

  • Edit rights on the workspace. Only Editors and Owners change the radar; everyone else reads it. In your personal workspace, you are the owner.
  • The technologies your diagrams name. The radar matches the technology texts of your models, such as PostgreSQL 16 or Java 21, Spring Boot 3, and the operating systems of deployment nodes, by name or alias and version.

The four rings

Ring Meaning
Adopt The default choice for new work.
Trial Use it where the team can manage the risk.
Assess Worth exploring; not for production yet.
Hold Do not start new work with it.

Each technology also sits in a quadrant: Languages and frameworks, Platforms and infrastructure, Data and messaging or Tools and services.

Rate your first technologies

  1. Open the radar

    Choose Technology radar in the Governance menu. An empty radar says that no vendor list ships with iyedy.

  2. Add the version you adopt

    Select Add technology. Fill in Product name (PostgreSQL) and Version (16); leave the version empty to rate the product as a whole. Choose the Ring Adopt and the Quadrant Data and messaging. Under the lifecycle, enter the End of support and End of life dates. Select Save.

  3. Add the version you want to stop

    Add PostgreSQL 12 in Hold, with its end-of-life date, and PostgreSQL 16 in Replacement so the finding says what to move to. Under Also written as, add the aliases your diagrams use, such as postgres.

  4. See it in a diagram

    Open the Claims Platform and run the checks.

    The radar lists the technologies Used in the open diagram. An element on PostgreSQL 12 has an STD-01 or STD-02 finding in the review, naming PostgreSQL 16 as the replacement.

Import lifecycle dates

Typing dates by hand is optional. Import technology lifecycle…, in the Governance menu, reads files you have downloaded:

  • endoflife.date API files, one per product: every release cycle with its dates.
  • A CycloneDX SBOM in JSON: one technology per component and major version, the quadrant from the component type. New technologies arrive unrated.
  • A CSV file, columns in any order by header, dates as YYYY-MM-DD. Export CSV writes the same columns.

The import shows a preview first: new technologies, updates and unchanged ones. Only Editors and Owners apply it. Nothing is fetched from another site: iyedy reads only the files you choose.

The checks it drives

Rule Fires when Default severity
STD-01 A technology is past its end of life or support, or reaches end of life within 180 days High, medium or low
STD-02 A technology is on hold Low
STD-03 A technology the model names is not on the radar Info

A technology without lifecycle dates is skipped by the end-of-life check. To see every technology in trouble at once, choose Technologies past or near end of life in the Governance menu.

Variants and limits

  • Remove a technology with Remove in its form: its findings go away, and no diagram changes.
  • A technology you keep on purpose past its date gets an exception, not a dismissal. See Accept an exception.
  • The Assistant reads the radar in designs and reviews: the technologies to adopt and those on hold go with the request.

If it doesn't work

STD-03 flags a technology I rated

The model writes it another way (Postgres 16, pg). Add that spelling under Also written as, or write the technology in the model as the radar names it.

No end-of-life finding for an old version

The technology has no lifecycle dates (No lifecycle dates: the end-of-life check skips it.), or the version on the radar does not match the model's. Add the dates, or import them from endoflife.date.

“Only Editors and Owners change the catalogue.”

Your role on this workspace only reads the radar. Ask an owner of the workspace; the register says who keeps it.

More: Run checks and handle findings.

Was this page helpful?Your answer is anonymous and counts only if you accepted measurement.

What went wrong?

Don't write personal data.

Navigation

iyedy docs, home
Lire en françaisOpen iyedy

↑ ↓ moveEnter openCtrl Enter new tabSearching English docs ·