RESOURCES
Stress testing resources
Evergreen guides and visuals for authorized capacity testing — Layer 4, Layer 7, metrics, and safe workflow.
Start here
Use these pages when you need a clear answer before opening the Hub: which layer to test, which metric matters, and how authorized testing differs from abuse tooling.
- Authorized Load Testing hub (start here)
- Product features
- Use cases hub
- vs k6 / JMeter / Loader.io / Gatling
- Load testing tools matrix
- Concurrent connections vs RPS
- Useful network tools (Check-Host, Censys, FOFA, Shodan)
- Switch — 15% migration discount
- vs typical stressers
- Layer 4 stress testing
- Layer 7 stress testing
- Load testing glossary
- Alternatives & comparisons
- Developer docs
- Authorized IP stresser vs booter
- Live status
From the blog
Deep playbooks live on the blog. Priority reads: Best IP stresser 2026, Is IP stresser legal?, legal checklist, API before launch.
Compare capacity on pricing or start free on verified targets only.
How to use this hub without getting lost
Treat resources as a map, not a reading list to finish in one sitting. Start with policy and vocabulary, then pick one method guide, then one use-case page that matches your next change window. Jumping straight into calculators without abort criteria usually produces vanity numbers that nobody trusts in a postmortem.
A reliable order: authorized load testing → glossary → Layer guide (L4 or L7) → matching use case → pricing / register.
Pair pages with the metrics you will report
- Need RPS vs workers clarity? Open concurrent vs RPS and the related glossary entries.
- Need tool choice? Use vs load-testing tools and the load testing tools matrix.
- Need trust framing? Read vs typical stressers before procurement.
- Need pre-flight host checks? See useful network tools.
Long-form playbooks stay on the blog; API and automation details live in docs.
A weekly learning loop for new operators
New Hub users waste capacity when they open every article at once. Pick one metric entry (for example abort criteria or RPS), one method page, and one use-case page per week. After each Hub smoke test, write three lines: hypothesis, abort rule, cliff observed. That loop beats binge-reading and keeps authorized practice tied to real systems you own.
When you outgrow Trial ceilings, compare published concurrents on pricing before the next campaign window — not during it.
What not to do with resource links
Do not treat marketing Gbps headlines as a substitute for a written hypothesis. Do not schedule a production rehearsal from a bookmark without verification, on-call notice, and abort rules. These pages explain authorized capacity testing on infrastructure you control — they are not instructions for disrupting third parties.
Hub tip: keep a short internal runbook that links three URLs only — the Layer guide you use, the use-case page, and pricing — so operators do not invent process mid-ramp. Status before large windows: check the live status page after you size capacity.
Related
Resources hub · Glossary · Tools matrix · RPS calculator · Useful network tools · Blog · Pricing · Start free