Arkhe
Arkhe scans your Unity project in the background and scores its architectural health, catching misplaced code and forbidden dependencies before they break your build.
by Tools Studio
Price History +
Arkhe
Unity projects accumulate structural drift over time. A script ends up in the wrong folder. An Editor-only class becomes reachable from runtime code without anyone noticing. A dependency crosses a boundary it was never supposed to cross. None of this produces a compile error at the moment it happens — it produces one later, often in a build, often once the original context is gone and nobody remembers why the code ended up that way.
Arkhe is a Unity Editor tool that scans your project, checks it against a defined set of architectural rules, and gives you one number — a Project Health Score — that reflects how much of that drift currently exists. You don't have to read every file to know whether your project's structure is holding up; you run a scan and look at the score.
How Arkhe Works
Arkhe opens as its own window from Tools > Arkhe, alongside your usual Editor layout. From the Dashboard or Scanner page, clicking Run Scan discovers the assets and script dependencies in your project and checks them against Arkhe's rule set. The scan runs in the background — you can keep working in the Editor while it completes.
Once a scan finishes, results appear in three places that build on each other: the Governance page lists every individual finding, the Rules page shows what was checked and why, and the Dashboard rolls all of it into a single Health Score. Nothing here requires interpreting a log or digging through console output — a finding on the Governance page always names the specific file involved and the specific rule it triggered.
Key Features
Wrong Location Detection checks whether a script's namespace, folder, and the assembly it actually compiles into agree with each other. This is what catches the case where Editor-only code is technically reachable from runtime code — a bug that costs nothing in the Editor and fails the moment someone builds a Player.
Forbidden Dependency Alerts checks dependencies between the parts of your project you've defined as Services against Arkhe's dependency rules — for example, that a runtime-facing service never depends on an Editor-only one. This catches an architectural boundary being crossed even when every individual file still compiles without complaint.
Governance is where every finding from both checks above is collected in one place, so you can see the current state of your project's architecture at a glance instead of hunting through separate reports.
Rules shows exactly what Arkhe is evaluating, in plain terms — each rule states its category, its severity, and the condition that triggers it. In this release, Arkhe's rules are predefined and run automatically on every scan.
Project Health Score turns the current scan's findings into a single number, weighted by how severe each finding is. It's not a live indicator — it reflects your most recent scan, so fixing something updates the score the next time you run one, not instantly.
Scanner is the engine underneath all of this: it's what actually walks your project, builds the dependency information the other features check against, and reports scan results (assets found, errors encountered) directly on the Scanner page.
Demo & Test Data
If you'd like to see what a real finding looks like before pointing Arkhe at your own project, the Settings page includes a Generate Demo Data action. It writes a small, fixed set of sample files into their own Assets/ArkheDemoData folder and registers two Services, so a scan has genuine violations to report immediately. Remove Demo Data deletes that folder and those Services in one step. This is the only thing in Arkhe that writes to your project at all, and only when you explicitly choose to run it — everything else Arkhe does is read-only.
Editor Scope & Compatibility
Arkhe is an Editor-only tool. It requires Unity 2022.3 LTS or newer, does not run in a built Player, and has no dependency on any render pipeline — it doesn't interact with rendering at all.
Support & Resources
- Documentation
- Arkhe on Discord
- Bug Reports
- Feature Requests
- Email Support: support.toolsstudio@gmail.com