How evaluation works
Every Kerf SDK holds a copy of your flag and experiment rules in memory. It evaluates each decision locally with a deterministic hash of the user id and the flag key. A user gets the same answer on every server, with no round trip.
Rules update by streaming. A change you make in the dashboard reaches connected SDKs in about a second.
Server SDKs
from kerf import Kerf
kerf = Kerf(sdk_key="srv_...")
variant = kerf.flag("new-checkout", user, default="control")Client SDKs
Browser and mobile SDKs never receive your full rule set. They request an evaluated payload for one user from a Kerf edge node, which keeps targeting rules private.
import { KerfClient } from "@kerf/js/client";
const kerf = new KerfClient({ clientKey: "cli_...", user });
await kerf.ready();Shared options
- defaultValue returned when the SDK cannot evaluate a flag.
- bootstrap lets you pass pre-evaluated values for first paint.
- offline mode reads rules from a local file for tests.
- exposureLogging turns exposure events off for a flag when needed.
Failure behavior
If Kerf is unreachable, the SDK serves its last known rules. If it has none, it returns the default value you supplied. A network failure never throws in the request path.
Testing
kerf.override("new-checkout", "treatment");
// reset after the test
kerf.clearOverrides();