A pricing flag is safe only when an operator can reconstruct which value the server used for a particular checkout. Short answer: for a small Next.js application, keep the admin-controlled flag simple, evaluate it during server-side rendering or in the backend API, and write a decision record beside the business event. Infrai fits the flag catalog and runtime-check portion when basic CRUD is enough; it does not supply the change history or evaluation analytics needed to explain an incident by itself.
Consider a bounded production scenario: a team releases a new regional discount rule behind pricing-rule-v2 , sees unexpected totals, and disables it. The current flag state now says “off,” but that fact cannot prove what the checkout server read ten minutes earlier. I would treat the missing historical decision as an observability defect, not as evidence that feature flags failed.
That distinction drives the design.…