Targeting
Rules on email, country, plan or any attribute, reusable segments and individual targets.
Ship to a few, then to everyone
Turn features on for some people first, ramp them up, and switch them off at once if something breaks.
Each domain is one project with one live configuration: there are no environments, and segments and rollouts take the place of Dev and Staging. Flags have a key, a type (boolean, string, number or JSON) with 2 to 20 variations, a kill switch (new flags start off), an off variation, a default rule, tags, an owner and a temporary or permanent mark. Targeting has individual targets and ordered rules on key, email, email domain, country, plan, name or custom attributes, with list, text, number, date and semver operators (each also negated) and reusable segments. Percentage rollouts place people by a stable hash of the flag key and context key, so a ramp from 10% to 50% keeps the first 10% in. Scheduled changes turn a flag on or off at a time or ramp it in steps, applied by a cron every 5 minutes. POST /api/v1/evaluate (secret key) answers servers with the value, variation and reason; GET /api/v1/flags and the /sdk.js browser SDK serve client-side flags only, from a cache that every change refreshes. Daily evaluation counts per variation, a history with field diffs, stale-flag digests and webhooks.
What Feature Flags does for you.
Rules on email, country, plan or any attribute, reusable segments and individual targets.
Stable percentage rollouts and scheduled ramps, with no environments to keep in sync.
A server API that gives its reasons, and a small browser SDK that serves client-side flags only.
A suggested path for Feature Flags. What you can do depends on your access in the app.
Choose its type and variations; new flags start off.
Add rules, segments and a percentage.
See evaluations per variation and remove stale flags.
Live host, inventory, governance, health checks, verification, dependencies and history.
Each domain is one project with one live configuration: there are no environments, and segments and rollouts take the place of Dev and Staging. Flags have a key, a type (boolean, string, number or JSON) with 2 to 20 variations, a kill switch (new flags start off), an off variation, a default rule, tags, an owner and a temporary or permanent mark. Targeting has individual targets and ordered rules on key, email, email domain, country, plan, name or custom attributes, with list, text, number, date and semver operators (each also negated) and reusable segments. Percentage rollouts place people by a stable hash of the flag key and context key, so a ramp from 10% to 50% keeps the first 10% in. Scheduled changes turn a flag on or off at a time or ramp it in steps, applied by a cron every 5 minutes. POST /api/v1/evaluate (secret key) answers servers with the value, variation and reason; GET /api/v1/flags and the /sdk.js browser SDK serve client-side flags only, from a cache that every change refreshes. Daily evaluation counts per variation, a history with field diffs, stale-flag digests and webhooks.
A/B tests of pages belong to Landing Pages and Campaigns; there are no environments (one live host).
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
flags.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.