All use cases
Platform engineering
Know what breaks before you deprecate it
An interactive dependency canvas built from your repositories, not from memory.
Before Fenwave2 weeks waiting
“We are retiring the v1 auth API in two weeks — can everyone check whether they use it and reply in this thread?”
What the wait costs
A deprecation that depends on everyone reading a Slack message, and one team that did not.
A dependency graph maintained by hand is out of date the day after it is drawn. Fenwave builds the catalog from your repositories, so the Architecture Explorer canvas shows components, APIs, systems and resources as they are now. Select the API you are retiring and its consumers are listed — including the one whose team is on holiday.
How it works
- 01Open Architecture Explorer and locate the component or API.
- 02The canvas draws its consumers, providers and owning system.
- 03Open the entity dossier for ownership, docs and API reference.
- 04Filter the canvas by system or type to reduce it to what matters.