Installation · TrafficLab Pro Docs

Docs/Get Started/Installation

TrafficLab Pro ships as a packaged desktop app for Windows and macOS, with a Linux AppImage target. It bundles its own Chromium browser, so nothing else needs to be installed.

System requirements

Minimum setupThe app is lightweight, the bundled Chromium is the only real dependency

Windows 10 or 11 (64-bit), or macOS 12 or newer (Apple Silicon or Intel), or a Linux distro with AppImage support.
2 GB of free RAM per 10 concurrent workers, roughly. The dashboard itself uses very little.
About 400 MB of disk space for the bundled Chromium and app files.
An internet connection. Real traffic goes through real network requests.
No browser install needed. No Node.js needed for end users.

Install on Windows

Two files ship for Windows:

NSIS installer (TrafficLab Pro Setup 1.0.7.exe). Recommended. Lets you choose the install folder, and creates desktop and start menu shortcuts.
Portable exe (TrafficLab Pro 1.0.7.exe). No installation, runs from any folder, good for USB sticks.

Run the installer (or the portable exe).
In the installer, pick a folder, choose shortcuts, and finish.
Launch TrafficLab Pro from the desktop shortcut or start menu.
The window opens on the Live Dashboard with a default campaign ready.

Windows title bar

Windows builds use a native-style hidden title bar with overlay captions and snap layouts, so the app feels like a modern native program.

Install on macOS

Open TrafficLab Pro-1.0.7-arm64.dmg (Apple Silicon) or the matching Intel build.
Drag the TrafficLab Pro icon into the Applications folder.
Launch it from Applications.
If Gatekeeper shows an "unidentified developer" warning, right-click the app and choose Open, then confirm once. Only needed the first time.

macOS window

macOS builds use native traffic lights (close, minimize, zoom) with a hidden inset title bar, matching the platform conventions.

Install on Linux

Linux targets an AppImage. Make it executable and run it:

bash

chmod +x TrafficLab-Pro-1.0.7.AppImage
./TrafficLab-Pro-1.0.7.AppImage

Install from source (developers)

If you bought the CodeCanyon package or work with the repository:

bash

npm install
npx playwright install chromium   # downloads the Chromium used by the real engine
npm run electron                 # build + protect + launch the desktop app

Browser preview: npm run dev runs the same interface in a normal browser with the simulation engine.
Standalone bridge: npm run bridge starts the local captcha bridge server on its own.
Packaging: npm run dist:win and npm run dist:mac produce the release installers in release/.
QA: npm run test:smoke runs a headless smoke test of every page.

Verify the installation

TrafficLab Pro opens on the Live Dashboard.
The sidebar shows a Default Campaign and a green Start button at the bottom.
Open Settings and confirm the About section shows "Hydra Engine v4.1".
If you plan to use real browsers, captchas or AI: continue with the First Run checklist.

Fastest possible start

You do not need a captcha key, an AI key or proxies to run your first test. The engine works with direct IP, simulation mode and no extras. Add the optional services only when you need them.

Common problems

Windows SmartScreen warning. Click "More info" then "Run anyway". The installer is code-signed per the build pipeline; if your copy is unsigned, allow it once.
macOS says the app is damaged or unidentified. Right-click and Open, or check that the download finished completely.
The real browser engine alert appears. Real browsers only run inside the desktop app. The browser preview (npm run dev) uses the simulation engine.
Antivirus flags the portable exe. Some scanners dislike portable executables. Use the NSIS installer instead, or add an exclusion.

One instance at a time

TrafficLab Pro requests a single instance lock. Launching a second copy just focuses the running window, it never starts a second engine.

Next steps

Follow the First Run checklist to configure the AI Agent, Captcha Service and engine, then run your first session.