All customers
T
TidewaterMarketplace · two-sided · High-traffic, spiky load

A marketplace kept permission checks fast under spiky load

A two-sided marketplace gated every action through Qeet ID's RBAC hot-path and kept evaluation snappy even during traffic spikes.

RBACPerformanceExplainability

At a glance

permission checks
Single-call
decisions
Edge-cached
grant-path traces
Explainable

The challenge

Every action across both sides of the marketplace is gated by a permission check, against a model that had grown organically into a tangle of special cases. Debugging a denial meant reverse-engineering which rule fired.

The solution

Qeet ID's RBAC engine let the team express hierarchical roles with inheritance and evaluate them on the hot path with a single /check call. Edge-cached decisions kept evaluation responsive during spikes, and explainable authorization returned the exact grant-path for every decision.

The results

The team stopped firefighting authorization edge cases and shifted focus back to product surface area. When a denial is questioned, the trace answers it directly.

The RBAC layer is the cleanest we've used, and when something is denied we get the exact grant-path back instead of guessing.
MH
Marcus HalePrincipal Engineer · Tidewater
Get started

Start building today.Free for developers.

25,000 monthly active users on the house. Production-grade auth, no credit card, no time limit.

  • No credit card
  • 25,000 MAU free
  • SOC 2 · GDPR ready