150 columns of crawl data is not an answer
In development. Crawls like the others, then does the thinking.
Not for sale yet. In development. This page exists so you know what is coming, and so you can tell me if it is the one you want first.
Screaming Frog is a genuinely good tool and I am not going to pretend otherwise. But it hands you a spreadsheet with 150 columns and assumes you know which ones are load-bearing. If you do, that is power. If you do not, it is a file you close again.
So the crawl is the easy half here and the prioritising is the product. Every issue arrives with why it matters, how to fix it, how urgent it is, and which pages are affected, which is the same four-part shape as the browser extension because that shape is the thing that works.
Why a desktop crawler at all
The browser extension can audit a few hundred pages before a tab starts struggling. Past that you need a real crawler with its own process, its own memory, and the ability to run for an hour without you leaving the window open.
A cloud crawler is the other option and it is the one that ends up metered, because someone is paying for those requests. Running it locally is what keeps it unlimited.
FAQ
Will it handle JavaScript-rendered sites?
That is the intention, and it is the hard part of building a crawler rather than a nice-to-have. A site that renders its content client-side is invisible to a crawler that only reads source HTML, and a lot of modern sites are exactly that.
How is the priority decided?
By impact and effort together, which is the only ordering that is any use. A missing title on your highest-traffic template outranks forty missing alt attributes on old blog posts, even though the second number is bigger.
Is there a free tier?
The browser extension is the free tier. That is not a token version either, for a small site it may be all you ever need. The desktop one is for when you have outgrown a browser tab.