SonarQube, CodeScene, Structurizr & IcePanel.
Where does ArchKeel fit?

When Sonar is the better choice

Choose SonarQube when you need code quality and security findings in a central review workflow. If your team already runs Sonar, first check whether its architecture management covers your boundaries. Adding another tool needs a concrete reason.

Architecture management is available from Server 2026.4 in Developer, Enterprise and Data Center editions. It supports Java, JavaScript, TypeScript, Python and C#. Community Build does not include this feature. Current SonarQube Cloud documentation lists Team and Enterprise plans.

SonarQube Community Build ↗ · Server architecture guide ↗ · Cloud architecture documentation ↗

When is CodeScene a better fit?

Choose CodeScene when the open question is: Where should we refactor first? CodeScene combines Code Health with Git activity. Frequently changed, hard-to-maintain areas become visible as hotspots. That helps prioritize effort using how the team works with the code.

CodeScene also provides checks in pull requests, CI and IDEs. The distinction from ArchKeel is the review question: Are you prioritizing maintenance work, or checking a candidate against an agreed architecture contract and its change expectation?

Behavioral code analysis ↗ · CodeScene workflow ↗

Structurizr or IcePanel for C4 modelling?

Choose Structurizr when you want C4 models, documentation and architecture decisions stored as text in Git. Its DSL separates the model from its views. Structurizr also provides a Java Component Finder that can discover components from code.

Choose IcePanel when your team wants to work together on a visual C4 model. Reusable model objects keep views consistent; drafts, comments and message flows support design decisions. IcePanel explicitly serves humans and agents.

For either tool, decide how the model will be checked against the implementation. A consistent diagram alone does not establish that a candidate follows the agreed contract. Agree who maintains the model and where implementation checks run.

Structurizr models as code ↗ · Component Finder ↗ · IcePanel modelling ↗ · IcePanel design workflow ↗

What does ArchKeel add to a review?

Choose ArchKeel when a review must also ask: Was this architecture change agreed, and can the analysis still support the same claims afterward? The versioned Architecture Contract records components, responsibilities, interfaces and allowed dependencies. Humans and coding agents refer to the same contract.

The Architecture Explorer shows As-Is, Target and Diff: observed code, declared architecture and their differences in one snapshot. The change check instead compares accepted and candidate commits against an expectation published before submission. The CLI returns PASS, FAIL and UNKNOWN with source evidence; UNKNOWN remains visible when evidence is incomplete.

In the recorded Python dispatch replay, eight tests stay green while one call becomes statically unresolved. ArchKeel rejects the candidate for lost analysis evidence:

return handlers[key](amount)

behavior tests       8/8 → 8/8
unresolved calls      0 → 1
archkeel check        FAIL · exit 1

The replay establishes this ArchKeel check. It is not an executed comparison with Sonar or CodeScene. Check scope and resolution depend on the language profile; runtime tests remain necessary.

Replay conditions and source · CLI reference ↗ · Architecture Explorer

Is ArchKeel an open-source alternative to SonarQube?

For focused checks of declared architecture boundaries and changes, ArchKeel can be an option. ArchKeel is MIT-licensed and runs locally. It does not replace general code quality or security analysis. SonarQube Community Build is itself free and described by SonarSource as open source; assess that edition separately from commercial architecture management.

If you only need import or module boundaries, also compare Import Linter, Tach and ArchUnit. The smaller checker may be enough.

SonarSource repository ↗ · ArchKeel MIT License · Compare architecture checkers