ClickProbe — Closed-Beta Onboarding Guide

This guide is in English. If you prefer German, write us at beta@clickprobe.ai — we're equally happy in DE or EN.


What is ClickProbe?


Before you start — beta pricing

As a closed-beta participant you receive €10 in free exploration credits, pre-loaded to your account. This covers roughly 200 short exploration sessions — more than enough to evaluate ClickProbe seriously.

There is no credit card required to use these pre-loaded credits. If you wish to top up, you can do so at any time from the dashboard (Cards via Stripe).


Step 1 — Create your account

  1. Open clickprobe.ai/signup in your browser.
  2. Enter your business email address.
  3. Choose your sign-in method:
    • Magic link (recommended) — we email you a one-click link; no password needed.
    • Google OAuth — click "Continue with Google" if your work email is a Google Workspace account.
  4. Click the link in your email (magic link only). You land on the ClickProbe dashboard.

Beta note: Your account will show €0 balance initially. Ingo will grant your €10 credit within one business day of you confirming your account via email to beta@clickprobe.ai. If you need it sooner, just say so.


Step 2 — Install the ClickProbe Proxy

The proxy is a single static binary (~15 MB). It runs on your machine, controls a local Chromium browser, and connects to our cloud over a single outbound WebSocket (port 443). No inbound firewall changes needed.

Download

Get the download link from Ingo after account confirmation — Ingo will send you the direct binary link for your OS. (Public release distribution is being set up; for the first beta cohort, Ingo provides the download link directly.)

OSFile
macOS (Apple Silicon)clickprobe-proxy-darwin-arm64
macOS (Intel)clickprobe-proxy-darwin-amd64
Linux (x86-64)clickprobe-proxy-linux-amd64
Linux (ARM64)clickprobe-proxy-linux-arm64
Windows (x86-64)clickprobe-proxy-windows-amd64.exe

Each binary ships with a SHA256 checksum — verify before running:

# macOS / Linux
sha256sum --check SHA256SUMS
# or: shasum -a 256 clickprobe-proxy-darwin-arm64

Install (macOS / Linux)

mv clickprobe-proxy-linux-amd64 /usr/local/bin/clickprobe-proxy
chmod +x /usr/local/bin/clickprobe-proxy
clickprobe-proxy

The proxy opens a browser tab for authentication. Sign in with the same account you created in Step 1.

Install (Windows)

Move-Item clickprobe-proxy-windows-amd64.exe C:\Users\you\bin\clickprobe-proxy.exe
& "C:\Users\you\bin\clickprobe-proxy.exe"

Verify it's online

After authentication, your terminal shows:

ClickProbe Proxy vX.Y.Z — connected
Account: your@email.com
Proxy ID: prx_xxxxxxxxxxxxxxxx

The dashboard at app.clickprobe.ai → Machines shows the proxy as Online (green dot).


Step 3 — Run your first exploration session

  1. Go to app.clickprobe.aiProjectsNew Project.
  2. Enter:
    • Name: anything descriptive (e.g., "My App — Staging")
    • Target URL: the full URL of the web app you want to test
    • App description (optional but recommended): 1–3 sentences about what the app does. The more context, the more targeted the bug reports.
  3. Click Save, then Start Exploration.
  4. Choose your proxy machine and set a budget limit (start with 5–10 minutes).
  5. Click Launch — the AI begins exploring.

Bugs stream into the Bug Inbox (left nav) as they're found.


Watching a session locally

Each ClickProbe proxy ships with a local WebUI for watching sessions in real time, without needing to log in to the cloud dashboard. It binds to http://127.0.0.1:9100 (loopback only — never externally reachable) and is protected by a per-startup random token.

Open the WebUI

clickprobe-proxy webui

This prints the URL + token and opens your default browser.

What you'll see

ClickProbe WebUI Dashboard showing auth, tunnel, Chromium, and local listen info.
Dashboard — auth state, tunnel state, Chromium version, port + token.
Sessions history list with the last 50 local sessions.
Sessions — last 50 local sessions; deep-linkable to the cloud dashboard.
Live session view with step counter and latest screenshot.
Live session — step-by-step view of the currently-running exploration.
Settings editor for port, enabled, log level, and headless mode.
Settings — edit <data-dir>/config.yaml.

Sharing a diagnostics bundle

If the proxy misbehaves, email beta@clickprobe.ai with the clickprobe-diag.zip from the Diagnostics page. It contains redacted logs, a redacted copy of your config (the WebUI token is stripped), current state, and version info.


Step 4 — Sign the AVV (Data Processing Agreement)

Under GDPR, because ClickProbe processes data from your users' web sessions on your behalf, kenaro GmbH acts as a data processor. We need a signed Auftragsverarbeitungsvertrag (AVV / DPA) before you handle any personal data in your sessions.

  1. Download the AVV template: AVV template (DRAFT PDF)
  2. Fill in your company details on the signature page.
  3. Sign the document (Adobe Reader, DocuSign, or handwritten scan — any method works).
  4. Email the signed PDF to legal@clickprobe.ai — Subject: AVV — [Your Company Name]
  5. Ingo counter-signs and returns within 1 business day (Mon–Fri).

DRAFT notice: The current AVV template is pending final review by a DACH tech lawyer. Your signature is not void, but the reviewed version will be sent for re-signing within 30 days of lawyer sign-off.


Beta support


Legal links


Quick-reference checklist