Skip to content

Managing technology & end-of-life

The Technology page (/technology, Estate → Technology) catalogues what your applications run on and surfaces lifecycle risk. It has its own Risk and Radar tabs alongside the catalogue. (The broader application/data catalogue lives on the unified Assets surface at /assets.)

Steps

  1. Get technologies in — via CSV import, ArchiMate, or cloud/CMDB sync. At minimum you want name, vendor, version, and category.
  2. Link technologies to applications — the "runs on / hosts" relationship. This is what makes lifecycle risk meaningful (blast radius).
  3. Set lifecycle status and key dates — at least for the technologies under your critical applications. Edit inline on the technology page (version, vendor, lifecycle, category, and deployment model & cloud provider). Resources brought in via AWS/Azure sync are auto-tagged as cloud-hosted on the right provider, so you typically only set deployment by hand for the on-prem and SaaS estate. Cloud-hosted assets carry a small provider-tinted cloud badge on diagram nodes.

End-of-life intelligence

ArcaMira enriches technologies with end-of-life data (via endoflife.date). On a technology page you'll see:

  • A lifecycle banner warning when the component is end-of-life.
  • Blast radius first — the applications (and transitively, capabilities) that depend on it.
  • EOL & Risk detail: end-of-life/support proximity and procurement window.

Across the estate, the technology page's Risk tab (/technology#risk) and the Intelligence hub roll this up into:

  • Sunset debt score — accumulated lifecycle risk.
  • Vendor concentration — single-vendor exposure.
  • Procurement windows — lead time before you must act.
  • Risk Matrix — a 4×4 grid plotting each technology on impact (criticality tier) × likelihood (EOL/obsolescence band); both axes come from objective data, and clicking a cell drills to the assets in it.

How to prioritize

Don't remediate alphabetically. Sort by blast radius weighted by criticality: an end-of-life component under a T1 application is urgent; the same component under a sandbox tool is not. The technology page shows you that context directly.