I started Archinsight because I believe software architecture is becoming too complex for the way we usually describe and maintain it.
Large systems accumulate years of decisions and dependencies. Their architecture stretches across teams, services, infrastructure and environments, and eventually no single person can keep the whole picture in their head. At that scale, architectural knowledge has to become something we can preserve, connect and reason about with confidence.
This matters even more as the way we build software changes.
More development work is being delegated to AI, and that changes what we need from architecture tooling. Human-readable documentation can tolerate context, convention and interpretation because people are remarkably good at filling in the gaps. Agents are much more useful when the environment gives them precise meaning and clear boundaries.
I believe architecture models will increasingly serve both people and software. For that to work, they need strong semantics. The relationships across a system need to remain connected. The vocabulary needs to have defined meaning. Changes need deterministic validation. The more the model can establish as fact, the less an agent has to infer, and the easier it becomes to trust the result of its work.
This is the direction behind Insight and Archinsight. Type safety and a fully linked model are foundations for building architectural knowledge that remains dependable as systems grow and as more of the work around them becomes automated.
C4 is a useful starting point, especially for communicating the shape of a system. My interest goes further: complex software platforms, large infrastructure, and architectural models detailed enough to support real reasoning about how everything fits together.
We are moving away from a world where software is developed entirely by people, using tools designed exclusively for people. I expect architecture modeling to evolve with that shift.
Archinsight is my attempt to take a step in that direction.
Archinsight is open source and licensed under the Apache License 2.0, so it can be freely used, modified, and distributed. The project is developed in the open, and contributions, extensions, and new ideas are welcome.