Changelog.

Plans are sized by one number: how often your SDKs call our edge. A server fetching the datafile, a browser or mobile SDK evaluating remotely, a stream connecting. Updates we push down an open stream when you change a flag are never counted. Six tiers become three (Free at 1M requests, Pro at $29 for 10M, Growth at $99 for 25M), and past the allowance it is a flat $6 per extra million rather than a cliff: your flags keep serving and the bill moves instead.

Monthly active users are gone from the bill, and with them the machinery that counted them. We no longer receive or store identifiers for metering, so nothing on our side is derived from who your users are. The pricing page has a calculator that takes a request volume and names the cheaper plan, and every org now has a usage dashboard with alerts at 50, 80, 95, and 100%.

We audited every claim on this site against what the product actually ships. Checkmarks that belonged to unshipped features (OAuth login, 2FA, multi-CDN failover) now carry Coming Q3 2026 labels, feature names match the product vocabulary (segments, context kinds), and streaming, which had quietly shipped weeks earlier, finally gets claimed. There’s also a new feat vs LaunchDarkly page with their listed prices, dated, and a section on where they’re ahead.

The delivery tier now measures server-SDK connection minutes, so your dashboard can show real usage against your plan’s allowance. The allowance stays a soft limit: going over never bills you and never cuts you off.

Flag changes stream to connected SDKs over SSE in under a second. Every SDK is streaming-first, with the 30-second background poll demoted to a safety net for dropped connections. A day later, streaming learned to send incremental patches instead of the full configuration on every change.

The documentation site launched at docs.feat.so: concepts, per-SDK guides for JavaScript, the browser, Go, Python, and Ruby, the full datafile wire format, and the exact evaluation order every SDK follows.

The full legal suite is live and versioned: customer agreement, DPA, subprocessor list, and a security overview. If your team needs documents before a trial, they’re all public; no NDA dance.