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 — PathIllustrative
CustomerBrowser · AI agent · Automation
Existing CDN / WAF / API GatewayUnchanged edge. Bruiser does not replace it.
BruiserCustomer-level execution control
Identity extraction
Customer policy
Execution lease
Concurrency control
Queue
Rate / in-flight control
Audit
Existing Waiting RoomOptional — scarcity between customers
Existing Ticketing / CommerceUnchanged. Not replaced.
InventoryScarce 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.
Direct origin access — the scarce operation is reachable without Bruiser.
Alternate allocation routes — a second path creates the same hold or booking.
Missing, stale, or tampered credentials — the presented proof is not current or intact.
Spoofed identity — the customer identity is not the merchant’s.
Origin-secret spoofing — a caller forges a secret that should stay at the origin.
Unprotected paths — a route performs allocation and is not covered.
Proxy and header bypasses — forwarded headers or an alternate hop skip the check.
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.