Skip to app details
Back to app library
APPNEURAL APP FAMILYAutomation & Integrations

Feature Flags

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.

01 / OVERVIEW

See where it fits in your day.

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 LOOK INSIDEExample layout · sample content
Flags and what they serve
FlagServingStatus
new-checkoutfeature flagsEXAMPLE
dark-modefeature togglesEXAMPLE
hindi-interfacerolloutEXAMPLE
beta-dashboardkill switchEXAMPLE
02 / CAPABILITIES

Built around the work you do.

What Feature Flags does for you.

01

Targeting

Rules on email, country, plan or any attribute, reusable segments and individual targets.

02

Rollouts

Stable percentage rollouts and scheduled ramps, with no environments to keep in sync.

03

Evaluation

A server API that gives its reasons, and a small browser SDK that serves client-side flags only.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Feature Flags. What you can do depends on your access in the app.

01

Create a flag

Choose its type and variations; new flags start off.

02

Target and roll out

Add rules, segments and a percentage.

03

Watch and clean up

See evaluations per variation and remove stale flags.

YOUR NEXT MOVE

Make Feature Flags part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE— items
P2PARTIALLY VERIFIEDPUBLISHED
Overview

Purpose and boundaries

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.

Gradual rollout for a connected domain's apps: flags with variations, targeting rules and segments, percentage rollouts, a kill switch, scheduled changes and a browser SDK.

A/B tests of pages belong to Landing Pages and Campaigns; there are no environments (one live host).

Priority
P2
Portfolio
Automation & Integrations
Capability
Automation & Integrations
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-16T05:19:04.929Z
Semantic inventory

Every number says what it counts

—Count unavailabletrackedEntityCount · catalog-api:unavailable
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

flag schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

flags.appneural.com DEPLOYED

flags.appneural.com

Worker
flag-catalog
Health
HEALTHY
Last deployment
2026-11-10 19:33:57
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

APPNEURAL-Catalogs/flag-catalogLOCAL · NOT CONFIGURED

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

HEALTHYHTTP 200 · 449 ms · 2026-11-16T05:19:04.929Z
HEALTHYHTTP 200 · 552 ms · 2026-11-16T04:18:34.629Z
HEALTHYHTTP 200 · 709 ms · 2026-11-16T03:18:41.574Z
HEALTHYHTTP 200 · 624 ms · 2026-11-16T02:18:41.648Z
HEALTHYHTTP 200 · 1022 ms · 2026-11-16T01:18:36.371Z
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

GITHUBNOT_CONFIGURED · 2026-11-16T05:19:06.086Z
CLOUDFLARENOT_CONFIGURED · 2026-11-16T05:19:06.086Z
CATALOG APISUCCEEDED · 2026-11-16T05:19:06.765Z
DNSSUCCEEDED · 2026-11-16T05:19:05.612Z
CLOUDFLARENOT_CONFIGURED · 2026-11-16T04:18:35.800Z
GITHUBNOT_CONFIGURED · 2026-11-16T04:18:35.800Z
CATALOG APISUCCEEDED · 2026-11-16T04:18:36.482Z
DNSSUCCEEDED · 2026-11-16T04:18:35.320Z
GITHUBNOT_CONFIGURED · 2026-11-16T03:18:42.575Z
CLOUDFLARENOT_CONFIGURED · 2026-11-16T03:18:42.575Z
CATALOG APISUCCEEDED · 2026-11-16T03:18:43.202Z
DNSSUCCEEDED · 2026-11-16T03:18:42.159Z
GITHUBNOT_CONFIGURED · 2026-11-16T02:18:42.754Z
CLOUDFLARENOT_CONFIGURED · 2026-11-16T02:18:42.754Z
CATALOG APISUCCEEDED · 2026-11-16T02:18:43.470Z
DNSSUCCEEDED · 2026-11-16T02:18:42.293Z
GITHUBNOT_CONFIGURED · 2026-11-16T01:18:37.373Z
CLOUDFLARENOT_CONFIGURED · 2026-11-16T01:18:37.373Z
CATALOG APISUCCEEDED · 2026-11-16T01:18:38.027Z
DNSSUCCEEDED · 2026-11-16T01:18:36.969Z

Drift findings

RESOLVED · canonicalHostnameResolvesDNS · last seen 2026-11-16T05:19:05.371Z
Evidence & history

Trust record

DNS resolvesScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Canonical hostname matchesScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

HTTPS worksScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Production environment existsScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Repository existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Repository exists.

Business owner existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Business owner exists.

Product owner existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Product owner exists.

Technical owner existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Technical owner exists.

Maintaining team existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Maintaining team exists.

Documentation existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Documentation exists.

Architecture documentation existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Architecture documentation exists.

Security review is currentScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Security review is current.

Data classification existsScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Dependencies existScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Dependencies exist.

Consumers existScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Consumers exist.

Health endpoint existsScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

SLA or SLO existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: SLA or SLO exists.

On-call existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: On-call exists.

Release existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Release exists.

Catalog inventory synchronizesScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Infrastructure drift is clearScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Infrastructure drift is clear.

DNS resolvesScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Canonical hostname matchesScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

HTTPS worksScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Production environment existsScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Repository existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Repository exists.

Business owner existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Business owner exists.

Product owner existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Product owner exists.

Technical owner existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Technical owner exists.

Maintaining team existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Maintaining team exists.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app