# Competitive Analysis

### Jito vs BAM vs Flowra

| Category                |       Jito (Legacy)       |      Jito BAM      |             Flowra             |
| ----------------------- | :-----------------------: | :----------------: | :----------------------------: |
| **Philosophy**          |        MEV capture        |   MEV suppression  |     Open Orderflow Auction     |
| **Mempool access**      |     Closed (Mar 2024)     |     TEE private    |     Open Orderflow Gateway     |
| **Validator role**      |       Block building      |  Execution only ↓  |     MEV revenue maximizer ↑    |
| **Searcher access**     | Restricted (high capital) |     Via plugin     |        API open (anyone)       |
| **Primary beneficiary** |          Searcher         |   Apps/protocols   |       Validators + users       |
| **User fee**            |   Information asymmetry   |      No change     | Real-time visibility + rebates |
| **MEV redistribution**  |            None           | Redirected to apps |  Returned to users (MEV-Share) |
| **Transparency**        |            Low            |         TEE        |        Fully transparent       |
| **Protocol fee**        |             6%            |         6%         |             **5%**             |

***

### Detailed Comparison from a Validator's Perspective

The questions validators actually care about most.

| Question                                       | BAM                      | Flowra                               |
| ---------------------------------------------- | ------------------------ | ------------------------------------ |
| Is my MEV revenue maximized?                   | ❌ Shared with apps       | ✅ Competitive bidding drives tips up |
| Can I break free from single-infra dependency? | ❌ Still Jito-dependent   | ✅ Validator Sovereignty guaranteed   |
| Do I retain my authority?                      | ❌ Delegated to BAM nodes | ✅ Bundle selection rights retained   |
| Do users benefit?                              | ❌ Unclear                | ✅ Fee transparency + MEV rebates     |
| Can it be transparently verified?              | ❌ TEE black box          | ✅ Fully on-chain                     |

***

### Why Flowra — The Core Differentiators

#### vs Jito Legacy

Jito tried to eliminate MEV by closing the mempool — but this only led to private mempools like DeezNode emerging and concentrating MEV opportunity further among the privileged few. Flowra goes in the opposite direction: open everything up and let competition run.

#### vs Jito BAM

BAM takes block building authority away from validators inside a TEE black box. MEV revenue gets redistributed to apps and protocols, and validators are reduced to mere executors. With Flowra, validators remain the primary agents of revenue maximization.

Flowra is the first Open Orderflow Auction Layer on Solana **designed for validators.** It maximizes validator revenue while simultaneously creating positive outcomes for users and the broader ecosystem.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://flowra.gitbook.io/flowra/comparison/competitive-analysis.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.