gatling-jdbc-plugin
Simple Gatling plugin for JDBC-based scenarios.
Designed for teams that need realistic database-backed load tests without extra integration friction.
⚡ Developer tooling for performance teams
Galaxio Team
We build practical tooling that makes load testing easier to adopt, automate, and maintain. Plugins, integrations, and workflows for Gatling, k6, and adjacent performance-testing ecosystems.
One ecosystem, many moving parts.
The idea is simple: keep the toolchain connected, useful, and easy to grow.
Core repositories Contributors Priority work
Need something urgent?
Critical features can be prioritized as a paid engagement when shipping speed matters.
What we build
Products that remove friction from performance testing.
We focus on the parts of load testing that usually cost the most time: setup, integrations, repeatability, and maintenance.
gatling-amqp-plugin
Performance testing with AMQP in Gatling.
Useful for teams validating messaging flows and event-driven architectures.
gatling-kafka-plugin
Gatling protocol plugin for Kafka workloads.
Helps model high-throughput messaging scenarios in a practical way.
gatling-picatinny
Utility extensions for the Gatling DSL.
Reduces boilerplate and keeps test suites easier to maintain over time.
People
A small team with clear roles.
We prefer visible ownership over vague “team” language. Each role has a clear lane, even when the group is intentionally small.
EN
Core team Engineering Builds plugins, integrations, and the technical paths around them.
PR
Core team Product Keeps the roadmap focused on useful tooling and real outcomes.
CO
Core team Community Works with contributors, users, maintainers, and ecosystem feedback.
DL
Priority work Delivery Handles urgent paid engagements and fast-track feature requests.
Community
Built with contributors, maintainers, and users.
We welcome issues, ideas, documentation improvements, and integrations that help the ecosystem grow.
See the repositories, understand how they fit together, and follow the evolution.
Small documentation fixes are often the fastest way to make a product easier to adopt.
If you use Gatling, k6, or adjacent tools in a new way, that context helps us shape the roadmap.