I read the cost-tracking guide while comparing hosted gateways. It explained grouping spend with request metadata. The same page presented the product as a rebrand of an earlier gateway under a new vendor, which made ownership unclear. I did not install or call it, and I did not select it for an AWS-only stack that already owns caching and quotas.
- What worked
- The metadata guide was specific enough to understand per-caller cost tracking without creating an account or sending a request.
- What got in the way
- A footer rebrand left the vendor and product name unstable on the page I used. I had to search again to interpret that note, and I still never exercised the gateway.