The test nobody ordered
Most systems discover their limits in production, in front of their customers.
That's a load test too. The most expensive kind, because you pay for it in lost orders and support tickets.
Your customers find the limit
Monitoring tells you the system is slowing down. It doesn't tell you where the limit was or how far traffic went past it. You find that out from the customers who already left.
Diagnosis under pressure
An outage at peak traffic costs the team a whole night, then days of cleanup. When you hunt for the cause in the middle of an outage, you usually end up fixing only the symptom.
The system stops responding
Usually at the moment the company has worked toward the longest: a campaign, a launch, the first big contract. Moments like that rarely come around twice.
A load test flips that order. You find the limit before your customers do, under controlled conditions and with time to decide.
What a load test is
Every system has a limit. Better to know where.
A load test is a controlled attempt to break your system. We simulate real user traffic and raise it step by step until we find the point where the system starts to struggle and no longer responds within the target time.
The test runs in your test environment, not in production. We generate the traffic from our infrastructure, so there's nothing for you to install and your customers never notice a thing.
The guide covers the test step by step and what it needs from you. Read the guide
How it works
We write the test. You read it and approve it.
There's nothing for you to write or install. We get to know your system, write the scenario, and generate the traffic. Your part is to read and approve.
We learn your system
We collect what you already have: API documentation, a description of user journeys, or a traffic recording. We fill the gaps by talking to someone who knows the system.
We write the scenario
From what we've collected, we build a readable scenario: user steps, traffic mix, and load profile, matching what your real users do.
You read and approve
You get the scenario in plain language. Approving it takes one email. If something needs changing, we revise it and show you the new version.
We generate traffic
We send traffic from our machines to the environment you point us to. At the end you get a diagnosis that says what fails first and where to start.
What a scenario looks like
Before the test runs, you know exactly what we're testing and how.
Every scenario has the same three parts:
User steps. The exact path the test will take through your system.
Traffic mix. Which actions happen most often and how many users do them at the same time.
Load profile. How traffic builds over time and what peak it reaches.
You approve the scenario before we start. Without your approval, the test doesn't run.
Scenario
Login peak at 9:00 a.m.
- 01User logs in
- 02Opens the dashboard
- 03Searches and filters
- 04Saves changes
Traffic mix
- read70%
- search20%
- write10%
Load profile
ramp to peak
What you get
You get what to fix first and proof that the fixes worked.
First we find out how much the system can take today and how much traffic it needs to handle. Then we repeat the same test after every fix, until the system reaches the goal you set.
After the test
Prioritized diagnosis
You get a list of what fails first, starting with what hurts most. If we have access to your metrics, you also get the cause. Your team knows right away where to start.
bottlenecks, in priority order
After every fix
The same test, run again
Once your team ships a fix, we run the same test again. You see whether the fix worked and where the system's limit is now.
same test, before and after
On our end
Your system stays in your hands
The scenario, the test data, and the traffic are our job. You share what you know about the system and read the results. Your team makes the fixes.
traffic from our infrastructure
Price, scope, and timeline
What it costs.
The price depends on how complex your system is and how much traffic it has to take. You'll know the exact figure before anything starts.
Free
Intro call
We assess whether you're ready for load testing.
Free
Scenario
We write, you read, we revise, you approve.
Free
Scope, price, timeline
You have the full picture. The decision is yours.
Paid
Setup and first run
We start once you approve. At the end you get a prioritized diagnosis.
First test
from PLN 7,500
Includes getting to know your system, login handling, test data, scenarios, the first run, and a prioritized diagnosis. The price grows with the number of scenarios, integrations, and environments, and with traffic volume and test duration.
Payable once you approve the scenario
Repeat run
from PLN 1,000
The same scenario after your fixes. The price depends on test duration and traffic volume.
You know the price before every run
Help by the hour
PLN 500
When your team gets stuck on a bug, we step in and track down the root cause.
Billed for time actually spent
You'll know the exact price for your system once you approve the scenario.
Why LoadCraft
You're one call away from a finished scenario.
Scenario right away
The first draft often takes shape during the call itself. You have the finished scenario shortly after we get your documentation.
You talk to the engineers
At an agency, several people stand between you and whoever runs the test, and some of what you agreed on gets lost along the way. With us, you talk directly to the people running your test.
We see it through
Test, diagnosis, your fix, another run. We're done when the system reaches the goal you set, and you have the proof in the diagnosis.
All it takes is one call to find out whether this makes sense for you.
Facing a performance problem? Tell us what you're up against.
You'll know whether you're ready for a load test.
30 minutes · online · free