The same tool, on your own machine
Silentfrog as an installable app — no terminal, no Node, no Git. It runs completely locally: the crawler moves inside the app, so the sites you point it at are fetched by your machine and never by ours.
macOS, version 0.2.0 · free for 50 pages, no key needed to start · all releases
What only the app can do
it crawls completely locally
The fetching that a browser is not allowed to do moves into the app itself. No url you enter, no page of either site and no result passes through our server — there is nothing for us to see and nothing to keep.
it reaches what your machine reaches
Staging behind an ip allowlist, a site on the company intranet, a build on localhost. The hosted version crawls from Frankfurt and simply cannot see those; the app is already inside.
no page cap from us
Nothing counts batches on a server, so the size of the crawl is a question for your machine, not for a plan. A ten thousand page site works like a fifty page one.
it works offline once activated
Once activated it never contacts a server again. No expiry, no re-check, nothing that stops working if this project ever goes away.
249 € once, and that is the last of it
There is no account and no subscription here either. Polar is the record of who paid; the app only checks it once.
free to download, free for 50 pages
Exactly like the browser version. You can map a small relaunch end to end before deciding anything.
one purchase, every relaunch
The web keys are bound to one project each, because a relaunch is a one-off. The Lifetime key is not: it covers every project you will ever open in the app.
three devices at a time
Your laptop, the studio machine, the one at home. Release a device and the slot is free again.
one server call, ever
Pasting the key asks our endpoint once whether it is real. What comes back is a signed activation record the app keeps in its own data directory — after that it is yours, offline.
Everything the browser version does
Same crawler, same matching, same directory and wildcard rules, same two csv exports. Nothing was left out to make an app of it — only the server half moved inside. See the full list or try it in the browser first.
Building the new site in Webflow?
A Webflow app is on the way. Inside the Designer the new site does not get crawled at all — its pages and cms collections come straight from the Webflow api, so the target list is exact from the first second and only the old site is crawled. Until then, the webflow-ready csv exported here imports under Site settings → Publishing → 301 redirects.
The first launch
These builds are not notarised yet, so macOS asks before opening one: right-click the app and choose Open, or go to System Settings → Privacy & Security → Open Anyway. A signature is on the list, and this note disappears with it.