Systems | Development | Analytics | API | Testing

But a recurring question came from banks, hospitals, defense and public-sector teams: what if nothing is allowed to leave our network, not even the prompt? This article answers that question with a full walkthrough.. We will stand up a 100% on-premise, air-gapped stack, and it only takes two things to install: OctoPerf Enterprise in Docker, and a local Qwen3 large language model running in LM Studio, which doubles as the Model Context Protocol client.

This is the third post in our "Features Sitting Idle" series, where we shine a light on OctoPerf features that are already in your account but rarely used to their full potential. This is a blind spot many teams discover too late. Tests pass, metrics look fine, yet real users report slowness or errors after a release. The root cause is almost always the same: the load test was built against the HTTP protocol layer, but the user pain happens in the browser, above that layer.

In the first two articles of this series we showed what the OctoPerf MCP Server does. This one is for the builders: how we designed it, and specifically how we kept its token cost under control. Because here is the thing nobody tells you when you start writing a Model Context Protocol server: the hard part is not exposing your API to an LLM. The hard part is not exposing too much of it.

Modern performance testing is evolving beyond the traditional choice between enterprise platforms and open-source tools. Teams increasingly need the flexibility of JMeter, k6, Gatling, or Locust combined with enterprise-grade reporting, scalability, security, and support. A new generation of platforms helps reduce operational complexity, lower total cost of ownership, and accelerate adoption through AI-assisted workflows and simplified onboarding.

This post is the second in our "Features Sitting Idle" series, where we explore key OctoPerf features that are either misused, misunderstood, or simply unknown to most users. The question comes up every iteration, and yet teams usually handle it the same way: export two reports, open a spreadsheet, and compare numbers manually. It works, but it doesn't scale. After three or four sprints, no one wants to open another spreadsheet.

We are launching with this post a new series of blog articles and LinkedIn posts titled "Features Sitting Idle". In this series, we explore key features of OctoPerf that are either misused, misunderstood, or simply unknown to our users. It's time to shine a light on these hidden gems, features that are already there, ready to become a central part of how you test. This is probably the most common situation after a load test.

Performance testing tools continue to evolve rapidly as modern applications become more distributed, scalable, and performance-critical. In this article, we review some of the most widely used performance and load testing tools in 2026, including JMeter, k6, Gatling, and cloud-based platforms, based on their scalability, ease of use, and integration with modern DevOps workflows.

In today's security-conscious world, relying on a password alone is no longer enough. With 2FA enabled, even if your password is compromised, the attacker would still need access to a second verification method (your authenticator app) to get in. At OctoPerf we're committed to helping you safeguard your valuable test configurations, results, and reports - 2FA is an essential step in that mission.

In 2022, OctoPerf went through a major UI makeover. The goal was not only to move to a more modern tech stack, but above all to offer a smoother, more flexible experience to our users. Since then, this new UI has been warmly welcomed by the thousands of people using OctoPerf every day. Over time, we’ve kept listening to you: your positive feedback, your suggestions, your ideas for improvement.

If you recall part one of this blog post, we were going to use ChatGPT in parallel with how we would work to cover these aspects of performance testing. We left the first part of this blog post at the point at which we had compared Requirements Gathering and Risk Assessment, we will pick this post up by looking at Script Creation before concluding with Results Analysis. Our performance testing tool of choice will be JMeter.