Understand the software you own
1ADK vs Structurizr
1ADK helps owners understand an existing architecture before the team has written a model: explore components, check supporting evidence, and keep track of questions.
Explore the components and connections found during analysis.Check the source reference behind a finding about a component.See new components and connections when comparing analyses.
Don’t wait for a model to understand your project.
Before you can describe an architecture, you need to establish how the system works. 1ADK gives owners access to those investigation results: a map, an interface inventory, supporting evidence, and history. You can discuss the project with a technical expert without learning a diagramming language.
01
What you gain with 1ADK
Start without an architecture repository
Your coding agent examines the existing project. 1ADK organizes the result even if nobody has maintained a separate architecture model.
Join the discussion without writing the model
Explore components and connections, then ask questions about the findings. You don’t need to edit a DSL—a text language for describing architecture.
Separate changes from discoveries
Analysis comparisons help distinguish new system changes from information established for the first time. That matters when documentation is being rebuilt alongside development.
02
Turn the map into a useful conversation
Example
You’ve bought the product. The architecture still needs to be documented.
Suppose the new team receives code and an incomplete diagram. They need a model that meets their standards, while the owner needs to understand the project now.
What 1ADK shows
The analysis finds components, external services, and an export job. Supporting references are available for review; an unidentified export recipient remains an open question.
The owner can discuss the system and missing information before the architecture documentation is finished. The team gets material to build the model.
03
What changes in your workflow
| Task | 1ADK | Structurizr |
|---|---|---|
| Source of the model | Findings from your coding agent’s investigation of the implementation. | Architecture defined in a text model, such as Structurizr DSL. |
| The owner’s workflow | Explore the map, check references, and discuss open questions. | Read diagrams generated from a model maintained by the team. |
| Unresolved information | Kept alongside findings as open questions. | Can be documented by the team in the model and supporting documents. |
| History | Differences between system analysis results. | Versions of the text model and its views. |
04
Using 1ADK and Structurizr together
1ADK helps investigate the implementation and keep its supporting evidence. Structurizr lets a team describe the agreed architecture as a text model and generate different views. Use 1ADK findings to prepare and check the model; writing it remains a separate task.
Questions about using 1ADK
No. You explore a map and its explanations. C4 is a way to show architecture at different levels of detail, while a DSL describes it in text. You don’t need to learn the language to use 1ADK.
Git shows file changes, including changes to architecture model files. 1ADK compares discovered components, connections, and system information, making the results easier to discuss at the project level.
Yes. First review the findings and resolve questions in 1ADK. An architect can then use that information to write a model in Structurizr DSL.
Product names and trademarks belong to their owners. 1ADK is not affiliated with these companies.
Find out what’s in your project.
The first analysis and one update are free. Your coding agent examines the project; 1ADK receives a structured description, not source files. Explore the map, check the evidence, and compare results.
No repository access. No source-code upload. No card.