Design, debug and run performance tests on your own machine. Desktop distributions include Node.js, k6 and a shared browser runtime.
Current beta: 0.1.0-beta.3 · released Nov 10, 2026
Windows 10 (64-bit) or Windows 11 on x64. Installs for your user with a Start Menu shortcut.
Download for Windows (beta)Extract the complete directory into a permitted location and launch Spikeproof.exe. Saved data stays in your user profile.
Download portable ZIP (beta)macOS 12 or later on Apple Silicon (M1 or newer). Open the DMG and drag Spikeproof into Applications.
Download for macOS (beta)Release notes · SHA-256 checksums · Install guide · Unsigned beta
Once per version. This allows Spikeproof only; Gatekeeper stays on for everything else.
Installs for your user only; no administrator rights needed.
Follow your company's software policy. If it blocks unsigned apps, don't work around it: ask IT, or wait for a signed release.
Betas don't update themselves. Download the newest one here and install it over the old one. Your services, journeys and results are kept.
Run the approved installer, select a user-writable installation directory, and launch from the Start Menu. No global Node.js, npm, k6 or browser setup is required.
Extract every file before launching. Keep the application and its resources together. Upgrades use a new approved ZIP; your existing services and results stay in AppData.
Drag Spikeproof from the DMG into Applications, eject the disk image, and launch the installed copy. Intel Macs are not supported by this build.
Finish active tests before updating. Signed releases offer stable-channel updates that you can defer. Journeys, services, environments and results remain in your operating system’s application data directory.
If your organization blocks an installer or executable, ask IT to approve the publisher, version and checksum. A portable ZIP is an installation option only where execution is permitted; it does not bypass company policy. IT can disable application-managed updates.
Authorized developers can use the private source workflow documented with the project. Repository access is not required for approved desktop distributions.
Compare its SHA-256 hash with the published checksum file. Betas are unsigned, so the checksum is how you confirm the file is exactly what was published. Never turn off Defender, SmartScreen, Gatekeeper or application allowlisting to launch a build.
On Windows, use Get-FileHash -Algorithm SHA256. On macOS, use shasum -a 256. No signing certificates, credentials or private workspaces are included in releases.