What counts as a request?
One call from an SDK to feat's edge. A server SDK fetching the datafile counts once, including when it comes back 304 Not Modified, because that costs us the same as a full response. A browser or mobile SDK evaluating remotely counts once. Opening a stream counts once, at connect. What we never count is the frames we push down that stream when you change a flag: billing you for your own flag changes would be a meter that discourages changing flags, which is a strange thing to sell on a flag platform. Seats, flags, environments, and projects are not in the number at all.
Can I work out my number before I sign up?
Yes, and that is most of the point. A server SDK on a streaming connection spends one connect plus a safety-net poll every ten minutes, which lands near 4,400 requests a month per instance. The same SDK on a 30-second poll loop spends about 86,400, so streaming is roughly twenty times cheaper for you on the same transport. A browser or mobile session costs more than one request: an evaluation when it starts, a stream connect, and a slow background poll while the tab is open, so budget two or three per session and more for a long one. Multiply, add, done.
Do you count monthly active users?
No, and we no longer hold the data that would let us. Server SDKs evaluate inside your own process and never send us a context. Browser and mobile SDKs do send one to be evaluated, and we throw it away: nothing derived from it is stored. Your bill tracks how often your SDKs talk to us, not how many people use your product, so a good month for you is not an invoice event.
Is there really no per-seat tax?
Correct. Every plan includes unlimited seats, so adding teammates never changes your bill. The audit log is worth more when actions trace to real people instead of one shared login, and we would rather have that than the seat revenue.
Do you charge for server-side SDKs or connections?
No. There is no per-connection fee on any plan, which is the model that makes a large fleet expensive elsewhere. Your services each spend a connect and an occasional safety-net poll out of the same request allowance as everything else, and that path is deliberately the cheap one.
What happens when I go over the allowance?
On Pro and Growth, nothing visible happens: usage above the allowance bills at $6 per million, and falls again when your traffic falls. Production is not the place to enforce a billing limit, so the bill moves instead of your flags. The free plan has no card on file and no overage rate, so there is nothing to pay; if your usage settles above the allowance, a paid plan is how to get more headroom. Every plan gets usage alerts at 50, 80, 95, and 100%.
Can I switch plans mid-cycle?
You can change plan whenever you like, and the change takes effect at the start of your next cycle. We don't prorate, in either direction. Your billing period is anchored to the day you subscribed rather than the calendar month, so signing up on the 14th means you are billed 14th to 14th.
What if I need more than 25M requests?
Stay on Growth and let the usage rate do the work: $6 per million, no cap, no sales call, no new contract. Worth knowing that above roughly 22M a month Growth is the cheaper plan even before you count approvals, so if you are on Pro and sitting up there, move.
Why is feat priced this low?
We run on a global edge network, we don't pay per-connection service fees to anyone, and there is no sales organisation to fund. The price on this page is the price; there is no second number that appears after a call.