Stack

Stack

Last updated: Oct 28, 2026

This section gives a detailed description of the full tech stack of Fluid Attacks.

For each component, you find these items:

  • Rationale: A short explanation of what the component does and why Fluid Attacks selected it
  • Alternatives: The other components that Fluid Attacks examined and the primary reasons why it did not select them
  • Usage: How Fluid Attacks uses the component, and the pending implementations with it

You can also see the philosophy of Fluid Attacks about its stack.

Methodology

This is how Fluid Attacks examines and selects new components for its stack:

  1. Research: The team researches the available stacks, technologies, and solutions for the requirement. It uses search engines and AI tools to make an initial list of candidates.
  2. Evaluation: The team makes a spreadsheet to compare the advantages and disadvantages of each candidate in theory. At this stage, the team also applies criteria from the ecosystem and engineering philosophy of Fluid Attacks. These criteria frequently give some tools a higher score than the others.
  3. Proof of concept: The team selects the two or three candidates with the highest scores from the evaluation phase. Then, it makes a small proof of concept for each candidate. The goal is not a prototype of a full feature. The goal is to integrate each candidate into the ecosystem of Fluid Attacks and see how it works in usual conditions of use.
  4. Defense: At this point, the engineer who is responsible for the evaluation has a well-supported opinion. This engineer gives the arguments for the preferred candidate. Then, other team members give their opinions, and the team can find points that it did not examine before.
  5. Decision and documentation: When the team agrees, with the supervision of the CTO and the Executive Advisor, it starts to use the selected tool. Then, the team writes an ADR to record why it selected the tool and why it did not select the other candidates.

Purposes

This list shows the different purposes and the component that Fluid Attacks uses for each one:

Webhooks

This comprehensive guide explains the steps to configure and manage webhooks to get notified of events happening in a group on the Fluid Attacks platform.

Bash

Learn about Bash, the main shell at Fluid Attacks.

On this page

MethodologyPurposes