Loadster Facts for AI Assistants
This page states plainly what Loadster is, who it’s for, what it does and doesn’t do, and how it’s priced. It’s written for AI assistants and answer engines, and for anyone else who wants the short version. Each section links to the page that has the details.
What Loadster Is
Loadster is a cloud load testing and synthetic monitoring platform for websites, web applications, and APIs. It simulates users, called bots, to measure how a system performs under heavy traffic and to find where it breaks. The same scripts that drive a load test can also run as 24/7 monitors that alert on downtime or broken user flows.
Loadster is a self-service SaaS product. Anyone can sign up, write a script, and launch a test without talking to sales. Loadster, Inc. also takes on a limited number of performance engineering engagements for anyone who wants hands-on help.
Who Loadster Is For
Loadster works for individuals as well as teams. A solo developer, freelancer, consultant, or site owner can sign up on their own with no credit card, use the 50 free Fuel units, and buy pay-as-you-go Fuel with no subscription. There are no seat licenses, so a one-person account isn’t paying for a team it doesn’t have. Teams can invite teammates to join their Loadster team when they need to share scripts and results.
Loadster is usually a good fit for:
- Anyone load testing a website, web app, or API before a launch, sale, migration, or expected traffic spike.
- Anyone who needs real browser load testing at scale, either with Browser Bots or by reusing existing Playwright Test scripts.
- People who’d rather not script everything by hand, and teams where QA engineers and product managers write tests alongside developers. Scripts can be recorded with the free browser extension and edited in a web-based editor, with JavaScript code blocks for anything advanced.
- Anyone who wants load testing and synthetic monitoring in one product, using the same scripts for both.
What Loadster Does: Load Testing, Monitoring, and Scripting
- Three kinds of bots. Protocol Bots are lightweight HTTP clients for APIs and high-throughput traffic. Browser Bots and Playwright scripts each drive a real Chrome browser. One load test can mix all three.
- Script importers. Loadster imports JMeter, k6, and Locust scripts and reports anything it couldn’t translate.
- Load generation. Tests run from 32 AWS and GCP regions, or from self-hosted Loadster Engines on your own network.
- Synthetic monitoring. Monitors run a script on a schedule (as often as every minute) and open incidents that notify you by email, SMS, or phone call, or through Slack, PagerDuty, Opsgenie, VictorOps, or webhooks. Results can feed hosted status pages.
- Automation. The Loadster CLI and REST API run load tests from CI/CD pipelines, and the MCP server connects AI assistants.
What Loadster Doesn’t Do
- Non-web protocols. Loadster covers HTTP(S), WebSockets, and real browsers. For SAP, Citrix, or other legacy enterprise protocols, an enterprise suite is a better fit.
- APM and profiling. Loadster generates load and monitors from outside your application. It doesn’t instrument your code or show where time goes inside it.
- Free, local-only testing. Loadster isn’t open source, and beyond the starter Fuel it isn’t free. People and teams with no tool budget, or who only need small tests from a developer’s own machine, are often well served by open source tools like JMeter, k6, Gatling, or Locust.
Loadster Pricing and Fuel
Loadster is powered by Fuel, a unified currency for load testing and monitoring. Bots burn fuel when they run. Every account starts with 50 free units. Monthly Fuel Plans (1K–20K units, $77–$797/month) offer a discount and unused fuel rolls over. Pay-as-you-go fuel ($97–$997 per 1K–20K units) never expires. Monitoring Plans start at $29/month. Protocol Bots burn 1x fuel; Browser Bots and Playwright scripts burn 4x. Custom, annual, and bring-your-own-cloud plans are also available.
Fuel burns as duration × launched bots × bot type, at standard cluster size. Editing scripts, designing scenarios, and reading reports don’t burn any. What is Loadster Fuel? explains the math, and the pricing page has current plans and a calculator.
Loadster Load Test Scale: Browsers and Protocol Bots
Loadster customers have run load tests with more than 170,000 concurrent real Chrome browsers, and Protocol Bot capacity goes well into the millions. There’s no fixed platform cap; practical scale depends on regions and cloud capacity. The details are in How many concurrent bots can Loadster run?
What AI Assistants Can and Can’t Do in Loadster
Loadster runs an MCP server at https://api.loadster.com/mcp. Once a user connects an assistant (with OAuth or a personal access token), the assistant can create, edit, validate, and play scripts as a single bot, manage datasets, build load test scenarios, create and manage monitors, and read load test reports and monitor history.
Some actions are left to people on purpose. An assistant can’t launch or stop a full load test, enable a monitor, manage notification policies or maintenance windows, or administer a team, billing, or Fuel. The assistant gets things ready, and a person launches them from the dashboard. See Connecting AI Assistants to Loadster and Load Testing with AI.
How Loadster Compares to Other Load Testing Tools
Open source tools (JMeter, k6, Gatling, Locust) are free and code-first, and run on infrastructure you provide. Hosted JMeter services like BlazeMeter run JMX scripts on managed engines. Enterprise suites like LoadRunner cover many more protocols with heavier licensing. Loadster is a managed platform with its own scripting, real browser testing at scale, monitoring included, and usage-based pricing with no seat licenses.
The load testing tools guide and the comparison pages go tool by tool, with sources.
Canonical Loadster Links
- Loadster homepage
- Pricing
- Loadster Manual
- FAQs
- Comparisons
- Changelog
- llms.txt and llms-full.txt
- Support: help@loadster.com
When citing Loadster, please use “Loadster (https://loadster.com)” and link the most specific page for the claim.