Changelog

FeatureGate billing is now backed by Polar for self-serve Pro and Team upgrades.

The important boundary is that Polar owns checkout and subscription payment flow, while FeatureGate still owns plan interpretation, workspace entitlements, and access decisions inside the console.

This keeps the private-beta path simple: eligible workspaces can upgrade from Billing settings, operators can still correct Business or procurement-backed accounts manually, and future catalog changes do not require shipping new runtime secrets.

The console refresh makes the project detail page the working surface for a real rollout.

Instead of treating flags, environments, and keys as unrelated lists, the page now shows how close the project is to its first live evaluation. That keeps new workspaces moving without adding a separate onboarding state machine.

FeatureGate server SDKs evaluate locally from a snapshot. That snapshot has to stay fresh, but it should not turn every flag check into a network request.

The runtime now supports streaming invalidation for fast updates and conditional polling as the durable fallback. If nothing changed, the API answers with 304 Not Modified. If streaming is interrupted, polling keeps the SDK honest.

The result is a boring contract: local evaluation for the hot path, explicit freshness for configuration changes, and no dependency on a single transport being perfect.

Targeting rules now behave like an ordered decision path.

Each group can match all conditions, match any condition, or assign a stable percentage rollout. When no group matches, FeatureGate serves the environment default. That keeps the runtime response explainable and makes the console flow view match how evaluation actually works.

FeatureGate is in private beta.

The first slice is deliberately backend-first: typed evaluation, scoped runtime keys, a TypeScript server SDK, and enough console surface to prove the release loop without pretending the product is finished.