Bruiser Request a Private Demo
Architecture Same product, three placements

Authority is the requirement.

The enforcement pattern is an implementation detail. Bruiser has to be able to control the scarce operation. Where it sits is how that authority is applied.

Fig. 01 — Path Illustrative
  1. Customer Browser · AI agent · Automation
  2. Existing CDN / WAF / API Gateway Unchanged edge. Bruiser does not replace it.
  3. Bruiser Customer-level execution control
    • Identity extraction
    • Customer policy
    • Execution lease
    • Concurrency control
    • Queue
    • Rate / in-flight control
    • Audit
  4. Existing Waiting Room Optional — scarcity between customers
  5. Existing Ticketing / Commerce Unchanged. Not replaced.
  6. Inventory Scarce units remain here
Illustrative placement. Customer principals meet the existing edge, then Bruiser, then an optional waiting room, then existing ticketing or commerce, then inventory.
01 — Deployment

The same product. Three patterns.

Embedded, edge, and proxy are deployments of one control layer. None of them replaces the CDN, WAF, waiting room, ticketing platform, or inventory.

Embedded

Inside the application.

Middleware on the scarce-inventory path. The application calls Bruiser before allocation proceeds.

Edge

On the existing edge.

An existing gateway, proxy, worker, or edge layer evaluates Bruiser before the request continues inward.

Proxy

In front of the API.

A reverse proxy in front of the scarce-inventory API. Allocation traffic that matters passes through it.

02 — Authority check

Can Bruiser actually control the scarce operation?

If the protected operation can be reached around Bruiser, Bruiser cannot guarantee its enforcement. The check validates the path, not the brochure.

Authority check

Pass

The scarce operation is reachable only through Bruiser. Enforcement can be guaranteed for that operation.

Authority check

Fail

The protected operation can be reached around Bruiser. Bruiser cannot guarantee its enforcement.