Documentation Index
Fetch the complete documentation index at: https://docs.nexus.westyx.cloud/llms.txt
Use this file to discover all available pages before exploring further.
What are feature flags?
Feature flags let you toggle behaviour in your application without a deployment. Nexus flags support:- Boolean on/off - the simplest use case
- Scheduling - automatically enable or disable at a specified time (
starts_at/ends_at) - A/B rollout - enable for a percentage of users with optional targeting rules
- Live push - changes propagate to connected SDK instances within milliseconds
Reading flags
All SDKs expose aGetFlag / getFlag / get_flag method that returns a boolean with a default fallback if the flag is not found.
A/B rollout
The AB Testing add-on (available ons tier and above) enables percentage-based rollout with optional targeting rules.
Use evaluateAB to evaluate multiple flags at once for a specific user:
evaluateAB returns { "checkout-v2": true, "new-sidebar": false } - stable for the same userID across calls (FNV-64 bucket).
A/B Testing requires the AB Testing add-on to be active on the project. A
403 response with ab_addon_not_active indicates the add-on is not enabled.Scheduling
Flags can be scheduled to turn on or off automatically:starts_at- enable the flag at this UTC timestampends_at- disable the flag at this UTC timestamp
Key names
Flag keys follow the same pattern as secrets and configs:^[a-zA-Z]([a-zA-Z0-9_.:-]*[a-zA-Z0-9])?$
Targeting rules
When the AB Testing add-on is active, you can configure JSONB targeting rules on a flag. Rules are evaluated by the server duringevaluateAB. Supported operators include eq, in, gt, lt, and contains.
