Feature flags

Flags that cost zero requests to read.

AyBee evaluates every flag at the edge, before your application sees the request, and writes the result into the X-AYBEE header. Your app reads a boolean from memory — no SDK call, no flag service to time out on.

Get early access See A/B experiments →

The problem

A flag check shouldn't be
a network call.

Traditional flag SDKs ask a remote service — on startup, on a polling loop, or worse, per evaluation. You inherit its latency, its outages, and the fallback code you write for when it's unreachable.

AyBee inverts that. The edge already holds the config snapshot, so it decides every flag while the request is in flight and hands your app the answer. The flag service is never in your hot path because there is no flag service in your hot path.

In your app

One header in.
A boolean out.

# the edge injects the decision
X-AYBEE: 1.4.chk.dGZl.Ag
// the SDK decodes the header — no network, no polling
const ab = AyBee.fromRequest(req)

if (ab.enabled("new-checkout")) {
  renderNewCheckout()
}

What you control

Per-environment state,
without redeploys.

state
On / off per environment
Each flag has independent state in dev, staging, and production. Flip it in the dashboard, not in a deploy.
rollout
Percentage rollout
Enable for a deterministic slice of traffic. The same visitor always lands on the same side — no flicker.
targeting
Segment targeting
Restrict a flag to segments — country, device, cookie, custom attributes — with full AND / OR / NOT logic.
priority
Deterministic priority
When rules overlap, higher-priority targeting wins. Evaluation order is explicit and reproducible.

Move your flags off the hot path.

AyBee is in development. Get early access and we'll reach out personally.

Get early access