Spitfire 1.0.0 release notes
Released: 2026-11-03latest
- Spitfire 1.0: Load Testing & Observability. Spitfire has its own APM and works with the APM you already have. The new tagline is in the title, the sign-in screen, the new About Spitfire dialog and the docs.
- The first step of our own APM: with the Go and Rust guides OTel now covers 7 languages (Java, .NET, Python, Node.js, PHP, Go, Rust). The Add a service wizard on the Observability and Towers pages asks for the language, the environment (Docker, Kubernetes, VM, IIS) and the service name, gives the commands with the endpoint and token filled in and waits for the first span live. The receiver also accepts OTLP/gRPC on :4317.
- External engines: existing JMeter (.jmx), Gatling and Locust tests run unchanged. Their results arrive as Spitfire metrics and the license limits apply. Each engine is off by default; an admin turns it on in the External engines card on the Runners page. The -jmeter, -gatling and -locust runner images ship with every release.
- Spitfire Recorder (Chrome extension): record a flow in Chrome and import it as a test. Passwords, card numbers, national ID numbers and auth headers are masked in the browser; correlation candidates such as CSRF tokens, JWTs and created IDs are checked against the recorded response.
- Deep APM with Dynatrace and Instana: markers at the run's start, each stage and end (off by default), per-stage service p95 and error rate, host CPU and memory, each stage's slowest traces with links. A slowdown and a problem during a stage become findings in the report.
- The report opens with a Result sentence: the run page and the HTML/PDF report start with a one-sentence verdict and 3-5 short lines. The live progress line says what the load is doing now. The new Executive summary is a one-page PDF: risk, the weak point, three numbers, up to three pieces of advice and the comparison with the previous run; /summary on shared links.
- Try it without installing: install.sh --with-demo brings a demo store with a breaking point and a ready test. The First steps list on the overview shows the way from the demo test to your own system.
- Feedback: a new Feedback page in the user menu. The answers travel only when you press Send, in your own browser, to our site; as a thank-you 30 days are added to the license (a 30-day Growth license for free users).
- The Starter plan comes with 1,000 VUs and 5,000 requests per second; older Starter keys keep their own limits. GitLab CI/CD catalog components (load-test, deploy, maintenance) were added.
- Release verification: an SBOM (SPDX, CycloneDX), a vulnerability scan and a cosign signature for every release; the steps are on the Security and release verification page.
- Fix: runner count fields no longer go above the runners there are. In the Run, calibration and comparison dialogs a typed count is cut to the idle runners as it is typed, and By labels applies the same limit. Schedules allow at most the registered runners (not the one kept for synthetic monitors, plus Kubernetes on-demand runners); they used to allow up to 256 and then failed with "not enough runners" when the run was due.
Updating
Your installation tells you about a new release itself: admins see its notes and the update command for that installation at the top of the UI. The command backs up the database first and keeps the settings (Updating). You can also follow new releases with the RSS feed.