Why I built ArchDocs

I'm Aylon, the founder of ArchDocs. A service name changes, but the diagrams that mention it still show the old name. I want that update to happen once.

I built ArchDocs around reusable objects. Define a service, database or API, then reference it in your diagrams. Change the object and every document that references it shows the change. You can open the object to see what depends on it.

That still takes work. Someone has to record a change to the system in ArchDocs. Reusing an object keeps its references consistent; it doesn't discover an unrecorded change in production.