Load tests
Expected traffic simulated against staging.
Load, stress and spike tests with k6 that show how your APIs and sites behave under real traffic, before a launch or sale does it for you.
export const options = {
scenarios: {
sale: { executor: "ramping-arrival-rate", startRate: 50, timeUnit: "1s",
preAllocatedVUs: 500, stages: [{ target: 800, duration: "2m" }, { target: 800, duration: "5m" }] },
},
thresholds: { http_req_failed: ["rate<0.01"], http_req_duration: ["p(95)<400"] },
};
export default function () {
const res = http.post(BASE + "/api/cart", JSON.stringify({ sku: "SALE-01", qty: 1 }), HEADERS);
check(res, { "added to cart": (r) => r.status === 200 });
}
The kinds of k6 projects clients bring us most often.
Expected traffic simulated against staging.
Flash sales, launches and campaign bursts.
How many users your set-up can handle, and what next.
Response time thresholds enforced in CI.
Find the slow query, service or setting.
Plain-English results with recommended fixes.
We recommend the stack that suits the job, even when that means suggesting something else.
Not sure? Tell us about the project on a free call and we’ll give you a straight answer.
What we most often pair with k6. Each has its own page.
Three models, one team. Switch between them as the product grows.
A written scope, timeline and price, split into milestones you approve one by one.
Vetted people who join your team, your tools and your stand-ups, full or part time.
We build under your brand while you keep the client relationship.
You explain the goal. We ask about users, deadlines and what already exists.
Scope, k6 architecture, timeline and price in writing.
Working software on a staging link at the end of every sprint.
Go live together, then receive code, docs and a walkthrough.
Timings are typical and depend on scope. Your proposal states the exact plan. See how we work.
We test against a staging copy by default. If production testing is needed, we plan it for a quiet window with safeguards and a stop switch.
That is the point of testing. We pinpoint the bottleneck, recommend fixes, and re-run the test to confirm the improvement.
Usually within about five working days of agreeing the brief. You get a fixed quote within 48 hours of the first call, and work starts once the contract and NDA are signed.
Scoped projects get a fixed price split into milestones, each paid when you approve its demo. For ongoing work you can hire dedicated engineers monthly or by the hour. Current rates are on our pricing and hire-developers pages.
You do, once the work is paid for. Repositories and cloud accounts are set up in your name from day one, and you receive documentation and a recorded walkthrough at handover.
Yes. We begin with a short audit of the code, hosting and open issues, share what we find in plain English, then agree a plan before changing anything.