All tools

RESEARCH / DATASCOUT

DataScout — competitor monitoring for Linux (early access)

Early access — not for sale. The 1.2.1 Linux build passed independent QA. Live provider use has not been independently certified; an external operator reported a DeepSeek-only live check on this build. There is no price, checkout or delivery date.

A guided Linux app that watches the competitor pages you choose, records changes on your machine, and writes a briefing with your own Anthropic or DeepSeek key. Early access — not for sale.

Who it is for

For a founder, product marketer or small team on Linux who wants a private, local way to watch a short list of competitors without another hosted account. It suits someone comfortable unpacking a package and running one install command in a terminal. It is not for Windows or macOS users, and it is not a managed service.

What this build does

  • Guided setup in your browser: competitor pages, provider, API key, delivery and briefing schedule.
  • A local dashboard for scans, briefings, service start/stop and Markdown export.
  • Competitor page snapshots and change detection stored on your machine.
  • Plain-language provider errors; a failed delivery keeps the saved briefing.
  • One desktop launch opens the local app after the one-time install.

Platform and requirements

Linux x86_64 (Ubuntu 24.04-class). The package bundles Node.js 22.23.5, so you do not install Node.js. You need a writable folder, a desktop browser, and your own Anthropic or DeepSeek API key. The bundled runtime needs glibc 2.28 or newer. Windows and macOS are not supported.

Current limits

How setup works

  1. Unpack the tarball into a folder you can write to.
  2. Run ./install.sh once in a terminal. It checks Linux x86_64 and the bundled runtime, then creates the local data folders. If the platform is unsupported, it stops.
  3. Launch DataScout.desktop (or run ./launch-ui.sh). Your default browser opens the app on 127.0.0.1. The URL contains a per-launch access token; keep it private.
  4. In the setup wizard, add competitor name/URL pairs, choose Anthropic or DeepSeek, enter your own API key, and set the delivery channel and briefing schedule.
  5. Before saving, the wizard tests the provider connection and probes each competitor URL. If the provider test fails, it does not write the key or configuration. On success, the key is written to app/.env with owner-only permissions (mode 600).
  6. Use the dashboard to run a scan or briefing, start or stop the background service, and export an open briefing as Markdown.

To change settings, reopen the wizard. The API key must be re-entered because the interface never reads it back. ./uninstall.sh stops the app; ./uninstall.sh --purge removes configuration, key, data and logs.

Your data

Competitor pages are fetched from your machine. When a briefing runs, the collected competitor content and alert summaries are sent to the model provider you selected. The local interface binds 127.0.0.1 only and requires a per-launch token. Your key is stored in app/.env with owner-only permissions (mode 600). AIDevShop does not receive telemetry, keys, competitor data or briefings. Anyone who can read your user account’s files can read the local token.