With loadforge-cli, your Locust scripts and test configs can live in Git, and your automations (syncing tests, starting runs, waiting for results) live in GitHub Actions. It’s the fastest way to make load testing part of your development workflow.
Writing the same Python helpers across multiple Locust tests is brittle and slow. The Library lets you create shared Python modules—small, reusable functions you can import across all your tests—to keep your performance suite DRY and consistent.
TLDR: We have launched the much-requested Organizations feature, allowing users to create separate workspaces for different projects or clients, with separate billing for each; Enterprise users can consolidate billing across multiple organizations by contacting our team.
•1 min read
We are proud to finally release a much requested feature - Organizations. You can now create entirely different workspaces (called Organizations) with their own packages, users, tests, and hosts.
This lets you fully separate different companies and divisions, or easily work on multiple clients accounts from a single user.
Each Organization is billed separately and kept entirely isolated from any other Organization. You can then add any users who should have access to multiple.
For Enterprise users, we do have the ability for you to have multiple organizations under a single billing entity, just speak to our team.