The latest articles on DEV Community by terrenz monyok (@terrenz_monyok_478ab195f6). https://dev.to/terrenz_monyok_478ab195f6 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4099160%2F20f75567-22ad-4ca1-b675-f5d1c180fe7c.png https://dev.to/terrenz_monyok_478ab195f6 en terrenz monyok Fri, 28 Aug 2026 14:57:14 +0000 https://dev.to/terrenz_monyok_478ab195f6/piemesh-an-open-source-distributed-load-testing-framework-for-websites-you-own-1j3j https://dev.to/terrenz_monyok_478ab195f6/piemesh-an-open-source-distributed-load-testing-framework-for-websites-you-own-1j3j <div class="ltag-github-readme-tag"> <div class="readme-overview"> <h2> <img src="https://assets.dev.to/assets/github-logo-5a155e1f9a670af7944dd5e12375bc76ed542ea80224905ecaf878b9157cdefc.svg" alt="GitHub logo"> <a href="https://github.com/spookybrosyt-star" rel="noopener noreferrer"> spookybrosyt-star </a> / <a href="https://github.com/spookybrosyt-star/PieMesh" rel="noopener noreferrer"> PieMesh </a> </h2> <h3> Self-hosted distributed load testing platform. Volunteer agents generate HTTP(S) traffic only against domains whose ownership was proven via DNS TXT challenge — consent-gated clients, hard-coded rate limits, full audit logging. For authorized security testing of systems you own. </h3> </div> <div class="ltag-github-body"> <div id="readme" class="md"><div class="markdown-heading"> <h1 class="heading-element">PieMesh</h1> </div> <p>Self-hosted, open-source distributed load testing framework.</p> <p>PieMesh lets machine owners contribute idle bandwidth to performance tests — but only against targets whose control has been demonstrated through a DNS TXT ownership challenge, the same mechanism used by ACME/Let's Encrypt. Nothing ships until the hub can prove who owns what's being tested.</p> <p><strong>Reciprocal by design — no spectators:</strong> everyone who runs PieMesh runs an agent. There is no download-and-watch tier: the tool IS the mesh, so having it means being part of it. Contribute capacity, earn test capability — and every test, yours included, still requires verified ownership of the target.</p> <div class="markdown-heading"> <h2 class="heading-element">Why it's different</h2> </div> <div class="table-wrapper-paragraph"><table> <thead> <tr> <th>Typical tooling</th> <th>PieMesh</th> </tr> </thead> <tbody> <tr> <td>Trust the operator's word</td> <td>Ownership proven via public DNS</td> </tr> <tr> <td>Limits configurable server-side</td> <td>Rate/duration caps compiled into the agent</td> </tr> <tr> <td>Silent enrollment</td> <td>Interactive consent gate, versioned, revocable anytime</td> </tr> <tr> <td>Black-box operation</td> <td>Every task logged locally + hub-side (<code>audit.log</code>)</td> </tr> </tbody> </table></div> <div class="markdown-heading"> <h2 class="heading-element">How authorization works</h2> </div> <div class="snippet-clipboard-content notranslate position-relative overflow-auto"> <pre class="notranslate"><code>1. Operator: target</code></pre>…</div></div> </div> <div class="gh-btn-container"><a class="gh-btn" href="https://github.com/spookybrosyt-star/PieMesh" rel="noopener noreferrer">View on GitHub</a></div> </div> <p>Self-hosted distributed load testing platform. Volunteer agents generate HTTP(S) traffic only against domains whose ownership was proven via DNS TXT challenge — consent-gated clients, hard-coded rate limits, full audit logging. For authorized security testing of systems you own.</p> testing github opensource startup