Your project data never leaves your machine
Element names, file names, level identifiers, and discipline tags stay on your machine. The AI engine that generates the title runs as a separate process on your computer — no part of your clash data is sent to ClashWise or any third party.
No quotas. No throttling. No rate limits.
Update thousands of clashes in a single batch, re-run a project, iterate on naming standards, or run nightly automation. There is no cap on the number of titles you can generate, because nothing is metering you.
Works once the AI is downloaded
After the one-time AI download, no internet is required for clash titling. Run on a site with restricted internet, in a regional BIM hub with patchy WAN, or anywhere a corporate firewall blocks AI services.
Ten curated open-source AI engines
The catalog spans Google, Alibaba, Meta, Microsoft, Mistral AI, and OpenAI, with sizes small enough for a laptop up to workstation-class options — so you can match the AI to your hardware, and switch any time.
Frequently asked questions
Is local AI as good as cloud AI?
For the vast majority of AEC clash titles, yes. Cloud uses a larger frontier AI so it has a slight quality edge on unusually ambiguous clashes. Local is consistently strong on the typical case, especially with naming standards.
Does any data leave my machine?
With local mode and no cloud fallback enabled, no clash data leaves your machine. Only usage analytics such as the count of titles generated flow back to ClashWise — never element names, file paths, or clash content.
Will this slow down Navisworks?
No. The AI runs as a separate process. If it ever crashes, your Navisworks session and work-in-progress are unaffected — the plug-in relaunches the AI automatically.