# Use Cases

## No Infrastructure

Running a broker means dedicated servers that need to be managed, patched and paid for.

To have a proper **highly available** setup you would need:

* **Multiple brokers** behind a load balancer.
* **Multiple nodes** behind a load balancer.
* A **monitoring system**.
* **DDoS protection** when publicly available.

**BaaS** takes care of all of this for you.

## No Broker Maintenance

On top of keeping the servers running, the broker software itself needs updating whenever a new version is released, which costs time and can cause downtime.

**BaaS** follows releases closely and updates everything for you without downtime.

## Commission Protection

On the native broker endpoint, the broker fee is part of the payload the client sends, so a user can change it. Calling it from a browser is therefore not safe.

**BaaS** adds a layer above the native broker that sets your broker fee automatically, which makes it safe to integrate in your web application. The same layer provides DDoS protection and a simpler integration for frontend developers.

[What Is a Chainflip Broker?](https://docs.chainflip-broker.io/reference/chainflip-brokers/) explains the broker's role and the difference between running your own and using a hosted one.
