What is the difference between limiting a customer and limiting a key?
A customer may have separate keys for different apps or people. A per-key limit gives each key its own counter. A per-customer limit groups those requests under one customer identity. Pick the rule that matches what you promised customers.
Which part of Unkey should you price?
Unkey documents standalone limits as well as key rules and policies in its hosted Deploy product. Verify which path will count your requests. Its Deploy pricing has separate meters, including active keys for its Key Auth policy, so avoid treating that figure as the price of every Unkey integration.
What should you keep if you change the service?
Keep a record of which customer owns each key, what it can do and which requests share a limit. Check the destination’s credential migration options or plan to issue new keys. Store this mapping separately from secret key values.
Do a customer’s two integrations share one allowance?
Give a fictional bike shop two labeled keys on paper, one for reports and one for stock updates. Use a shared allowance of three requests in one window.
- Count across both labelsMark two report calls and one stock call. A fourth request for either integration is over the shared allowance.
- Compare with two countersGive each key its own allowance and repeat the calculation. Choose the result that matches the customer’s plan.