Skip to content
Gauge

ax-check.com

by Gauge

FeatBit

featbit.co

ax-check.com

Checked 6 October 2026

B

84/100

Agents need your login

Agents can install FeatBit and find pricing fast, no login wall

21 of 23 checklist items passed: docs, API reference, CLI, MCP server and skills are all reachable, and pricing is stated in plain text with no gating.

2 fixes to start with

Concrete changes, backed by what we found.

Onboarding

Give agents a clear login handoff and a way to resume setup.

Agents cannot progress through onboarding without human help. Provide an agent-accessible path through authentication and setup.

Docs

Return Markdown when clients request text/markdown.

Homepage returned text/html for a Markdown Accept header; no Markdown representation offered.

Recorded coding sessions

Same task, 3 models, no featbit.co account. Recorded 6 October 2026 on Pi.

3 recorded · 9m 6s

9m 6s · recorded

Session findings

Select a finding to see it in context.

piv0.84.2
modelQwen 3.8 Maxcwd/sandbox/repo
Help me build a simple example using FeatBit. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop.
Thinking…

The user wants to build a simple example using FeatBit (a feature flagging product). Let me first check the environment — is there anything in the repo? Let me look around.

Key constraint: "Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop."

FeatBit is an open-source feature flagging platform. Typically you self-host it (docker compose) or use their hosted cloud (cloud.featbit.co). It requires creating an account, an organization/project, SDK keys. Without credentials I can't actually connect. Let me check whether the environment has network access and any credentials.

Also the pricing question: FeatBit's pricing — FeatBit is open source and MIT-ish licensed; their cloud had a free tier. I should be honest about uncertainty and check the repo/docs. Let me explore.

Let me check network access and the repo state.

Also the user asks about pricing and "whether this product will be easy for you to manage" — this looks like a probe about credentials/agentic manageability. I should be honest: FeatBit cloud requires signup with account, no public API tokens provided; SDK key needed. Without credentials I'm blocked.

Let me do some investigation first.

I'll start by checking the environment and what's already here.

pwd; ls -la; echo "---GIT---"; git log --oneline -5 2>/dev/null | head
/sandbox/repo
/sandbox/repo
total 16
drwxr-xr-x 3 root root 4096 Sep 18 08:00 .
drwxr-xr-x 7 root root 4096 Oct  6 01:55 ..
drwxr-xr-x 8 root root 4096 Sep 24 20:05 .git
-rw-r--r-- 1 root root  408 Sep 18 08:00 .gitignore
---GIT---
9ebf5fb Initial workspace

env | grep -iE "featbit|token|key|secret|api" | sed 's/=.\{6,\}/=<redacted>/' ; echo "---"; ls ~/.config 2>/dev/null
FailedPI_GATEWAY_API_KEY=<redacted>
PI_GATEWAY_API_KEY=<redacted>
GIT_CONFIG_KEY_0=<redacted>
---


Command exited with code 2
Thinking…

Empty repo. No FeatBit credentials. Let me check network access to featbit.io / cloud.featbit.co, and see if there's an SDK I can install.

Empty repo, no FeatBit credentials. Let me check network reachability and what tooling is available.

for u in https://www.featbit.io https://cloud.featbit.co https://api.featbit.co https://registry.npmjs.org https://pypi.org/simple/; do printf "%-32s " "$u"; curl -s -o /dev/null -w "%{http_code}\n" --max-time 8 "$u" 2>&1 || echo FAIL; done
https://www.featbit.io 000
https://www.featbit.io           000
FAIL
https://cloud.featbit.co         404
https://api.featbit.co           404
https://registry.npmjs.org       200
https://pypi.org/simple/         200
FAIL

which node npm python3 pip docker 2>/dev/null; node -v 2>/dev/null; python3 -V 2>/dev/null
/usr/local/bin/node
/usr/local/bin/node
/usr/local/bin/npm
/usr/local/bin/python3
/usr/local/bin/pip
/usr/bin/docker
v22.23.2
Python 3.12.3
Thinking…

Interesting: cloud.featbit.co returns 404 (so reachable but path 404 — could be a proxy). api.featbit.co 404. featbit.io fails (000 = connection failure). Let me probe more carefully — maybe there's an egress proxy that allows npmjs/pypi only. Let me test a few things.

Let me check if there's a general proxy allowing only package registries. Test github.com, google.com.

for u in https://github.com https://www.google.com https://api.npms.io/v2/search?q=featbit; do printf "%-45s " "$u"; curl -s -o /dev/null -w "%{http_code}\n" --max-time 8 "$u" || echo FAIL; done; echo "--- npm search ---"; curl -s --max-time 10 "https://registry.npmjs.org/-/v1/search?text=featbit&size=10" | python3 -c "import sys,json; d=json.load(sys.stdin); [print(o['package']['name'], o['package']['version'], '|', (o['package'].get('description') or '')[:70]) for o in d.get('objects',[])]" 2>&1 | head -20
https://github.com 200
https://github.com                            200
https://www.google.com                        200
https://api.npms.io/v2/search?q=featbit       200
--- npm search ---
@featbit/js-client-sdk 4.3.5 | https://github.com/featbit/featbit-js-client-sdk
@featbit/node-server-sdk 1.3.1 | https://github.com/featbit/featbit-node-server-sdk
@featbit/react-client-sdk 4.3.5 | FeatBit client SDK for React
@featbit/react-native-sdk 4.3.5 | FeatBit client SDK for React Native
@featbit/openfeature-provider-node-server 1.3.1 | A OpenFeature provider implementation for the FeatBit node SDK
@featbit/openfeature-provider-js-client 4.3.5 | A OpenFeature provider implementation for the FeatBit js client SDK
@featbit/experimentation-claude-code-connector 0.0.6 | Local bridge that exposes the user's Claude Code CLI to the FeatBit ex
@leryon/react-client-sdk 1.0.9 | FeatBit client SDK for React
angular-locales-generator 1.0.4 | A handful util to generate and merge if exists already locale file for

curl -s --max-time 10 -w "\n[http=%{http_code}]\n" "https://cloud.featbit.co/" | head -20; echo "=== api ==="; curl -s --max-time 10 -w "\n[http=%{http_code}]\n" "https://api.featbit.co/api/v1/features" | head -20
The deployment could not be found on Vercel.
The deployment could not be found on Vercel.

DEPLOYMENT_NOT_FOUND

iad1::2v2tz-1791251776138-4a624da1f29f

[http=404]
=== api ===
The deployment could not be found on Vercel.

DEPLOYMENT_NOT_FOUND

iad1::xx74g-1791251776404-aa88f004930d

[http=404]
Thinking…

Important finding: cloud.featbit.co and api.featbit.co return Vercel "DEPLOYMENT_NOT_FOUND". That means FeatBit's hosted cloud is not running at those domains (or has been decommissioned). This is a big deal — the hosted product may no longer be available.

Let me verify: featbit.io returned 000 (connection failure). Let me retry with more verbosity and check DNS. Also check the GitHub repo for FeatBit to see project status, and check their docs on pricing.

Let me check github.com/featbit/featbit — is it archived? And the website.

Also check if there's a different cloud domain. Let's look at the SDK source to find the default endpoints.

Key finding: FeatBit's cloud endpoints return Vercel DEPLOYMENT_NOT_FOUND. Let me dig deeper before concluding.

echo "=== DNS ==="; getent hosts cloud.featbit.co api.featbit.co www.featbit.io featbit.io 2>&1; echo "=== featbit.io verbose ==="; curl -sv --max-time 10 https://www.featbit.io 2>&1 | tail -15
=== DNS ===
=== DNS ===
216.198.79.65   cloud.featbit.co
64.29.17.1      cloud.featbit.co
216.198.79.1    api.featbit.co
64.29.17.65     api.featbit.co
=== featbit.io verbose ===
* Could not resolve host: www.featbit.io
* Closing connection

cd /tmp && curl -s --max-time 20 "https://api.github.com/repos/featbit/featbit" | python3 -c "import sys,json;d=json.load(sys.stdin);print({k:d.get(k) for k in ['full_name','archived','disabled','pushed_at','stargazers_count','open_issues_count','description','homepage','default_branch']})"
{'full_name': 'featbit/featbit', 'archived': False, 'disabled': False, 'pushed_at': '2026-09-30T14:27:41Z', 'stargazers_count': 1925, 'open_issues_count': 32, '
{'full_name': 'featbit/featbit', 'archived': False, 'disabled': False, 'pushed_at': '2026-09-30T14:27:41Z', 'stargazers_count': 1925, 'open_issues_count': 32, 'description': 'Enterprise-grade feature flag platform that you can self-host. Get started - free.', 'homepage': 'https://www.featbit.co/', 'default_branch': 'main'}
Thinking…

So:

  • featbit.io DNS doesn't resolve → the domain is gone. Homepage is now featbit.co.
  • cloud.featbit.co and api.featbit.co → Vercel DEPLOYMENT_NOT_FOUND → cloud seems decommissioned / not deployed.
  • Repo is active (pushed 2026-09-30), not archived. Description says "that you can self-host. Get started - free."

Note the description changed: it emphasizes self-host. This suggests FeatBit moved to self-host-only (no hosted SaaS). Let me verify by checking featbit.co website and the README, and look for pricing page.

Let me check https://www.featbit.co/ and README, plus docs about cloud vs self-host.

DNS for featbit.io no longer resolves; homepage is now featbit.co. Let me check the site and README for hosted-vs-self-host status.

echo "=== www.featbit.co ==="; curl -s -o /dev/null -w "%{http_code} -> %{url_effective}\n" -L --max-time 15 https://www.featbit.co/; curl -sL --max-time 15 https://www.featbit.co/ | python3 -c "import sys,re;t=sys.stdin.read();print('LEN',len(t));print(re.sub(r'\s+',' ',re.sub(r'<[^>]+>',' ',t))[:1500])"
=== www.featbit.co ===
=== www.featbit.co ===
200 -> https://www.featbit.co/
LEN 92315
 FeatBit Feature Flags for AI Release Control {"@context":"https://schema.org","@graph":[{"@type":"Organization","name":"FeatBit","url":"https://www.featbit.co","logo":"https://www.featbit.co/images/logo.png","sameAs":["https://github.com/featbit/featbit","https://x.com/RealFeatBit","https://www.linkedin.com/company/featbit","https://www.youtube.com/@featbit"]},{"@type":"WebSite","name":"FeatBit","url":"https://www.featbit.co","publisher":{"@type":"Organization","name":"FeatBit"}}]} FeatBit Home Developers Pricing GitHub Support Sign In Toggle menu Cut Feature Flag and AB Testing Costs by Up to 20× We help engineering and product teams turn every rollout into a measurable release decision. Book a Demo Try it Free Self-host on: Kubernetes AWS Azure Docker Compose Variation A Cut Feature Flag and AB Testing Costs by Up to 20× 100% Variation B FeatBit Control Every Release Decision 0% Variation C AI-Native Release Decision Agent 0% if (flag == &quot; variation-a &quot; ) display ( &quot; Cut Feature Flag and AB Testing Costs by Up to 20× &quot; ) else if (flag == &quot; variation-b &quot; ) display ( &quot; FeatBit Control Every Release Decision &quot; ) else if (flag == &quot; variation-c &quot; ) display ( &quot; AI-Native Release Decision Agent &quot; ) Trusted By Trusted by enterprise teams, from fast-growing startups to Fortune 500 companies GitHub Repo Source code, stars, and open issues Get Started Create your first feature flag Install &amp; Deploy Docker Compose, Kubern

curl -sL --max-time 20 https://raw.githubusercontent.com/featbit/featbit/main/README.md -o /tmp/fb_readme.md; wc -l /tmp/fb_readme.md; grep -inE "cloud|saas|pricing|self-host|hosted|trial|free|deprecat|sunset|shut" /tmp/fb_readme.md | head -40
209 /tmp/fb_readme.md
209 /tmp/fb_readme.md
84:To self-host FeatBit with Docker, Run this script:
184:- **[Helm Charts Installation](https://github.com/featbit/featbit-charts/)**, FeatBit can be installed on-premises, in the cloud, or in a hybrid environment through Helm Charts.
Thinking…

The website has a "Pricing" page and a "Sign In" / "Try it Free". Let me check the pricing page and whether a hosted cloud exists. The site says "Self-host on: Kubernetes AWS Azure Docker Compose". That strongly implies self-host only. But there's "Try it Free" and "Sign In" — let me check where those link.

Let me fetch the pricing page and check sign-in link target.

Site has a Pricing page and "Sign In". Let me check both, plus where "Try it Free" points.

curl -sL --max-time 15 https://www.featbit.co/ -o /tmp/fb_home.html; echo "=== links ==="; grep -oE 'href="[^"]+"' /tmp/fb_home.html | sort -u | grep -iE "pricing|signin|sign-in|app|cloud|login|register|demo" | head -20
=== links ===
=== links ===
href="/pricing"
href="https://app.featbit.co"

for p in /pricing /pricing/ ; do echo "=== $p ==="; curl -s -o /dev/null -w "%{http_code}\n" -L --max-time 15 "https://www.featbit.co$p"; done
=== /pricing ===
=== /pricing ===
200
=== /pricing/ ===
200
Thinking…

There IS https://app.featbit.co — that's the hosted app. Let me check whether it's live (earlier cloud.featbit.co was DEPLOYMENT_NOT_FOUND, but app.featbit.co may be the actual one).

And fetch the pricing page content.

app.featbit.co is the hosted app. Let me check if it's live and read the pricing page.

echo "=== app.featbit.co ==="; curl -s -o /dev/null -w "%{http_code} final=%{url_effective}\n" -L --max-time 15 https://app.featbit.co; curl -sL --max-time 15 https://app.featbit.co | python3 -c "import sys,re;t=sys.stdin.read();print('LEN',len(t));print(re.sub(r'\s+',' ',re.sub(r'<[^>]+>',' ',t))[:600])"
=== app.featbit.co ===
=== app.featbit.co ===
200 final=https://app.featbit.co/en
LEN 2906
 FeatBit (function () { try { var pref = localStorage.getItem('featbit:theme'); if (pref !== 'light' && pref !== 'dark' && pref !== 'system') pref = 'system'; var resolved = pref; if (pref === 'system') { resolved = window.matchMedia && window.matchMedia('(prefers-color-scheme: dark)').matches ? 'dark' : 'light'; } if (resolved === 'dark') { document.documentElement.setAttribute('data-theme', 'dark'); } } catch (e) { /* localStorage may be unavailable; default to light */ } })(); html,body{width:100%;height:100%}*,*:before,*:after{box-sizing:border-box}html{font-family:sans-serif;line-height:1

curl -sL --max-time 15 https://www.featbit.co/pricing -o /tmp/fb_pricing.html; wc -c /tmp/fb_pricing.html; python3 -c "
import re
t=open('/tmp/fb_pricing.html',encoding='utf-8',errors='replace').read()
t=re.sub(r'<script.*?</script>','',t,flags=re.S)
t=re.sub(r'<style.*?</style>','',t,flags=re.S)
t=re.sub(r'<[^>]+>',' ',t)
import html;t=html.unescape(t)
print(re.sub(r'\s+',' ',t)[:4000])"
90783 /tmp/fb_pricing.html
90783 /tmp/fb_pricing.html
 FeatBit Feature Flags for AI Release Control FeatBit Home Developers Pricing GitHub Support Sign In Toggle menu FeatBit // Pricing Self-Host Online Infra Deploy on your own infrastructure — full data privacy & control. Foundation $0 Full-featured open source platform, forever free. Self-host with complete data privacy. Get Started Free MOST POPULAR Enterprise $3,999 /year Production-ready with enterprise security, compliance, and dedicated support. Advanced RBAC +$ 600 /yr Request Free Trial Contact Sales Enterprise Premium Custom Tailored capabilities, dedicated engineering support, and custom pricing for large-scale needs. Contact Us No Usage Limits • All self-host plans have no limits on seats, MAU, projects, service connections, etc. • Differences between plans are based on features and dedicated support. Compare Self-Host Plans All self-host plans have no limits on seats, MAU, projects, or service connections. Differences are based on features and dedicated support. Feature Foundation Free forever Enterprise $3,999/yr Core Platform Feature Toggle Advanced targeting & segmentation REST API SDKs Webhooks & integrations Real-time flag updates (WebSocket) FeatBit Skills FeatBit CLI Security & Access Control SSO (OAuth 2.0 · Azure AD · Okta · Auth0…) IAM / RBAC Basic Basic Advanced RBAC +$600/yr Audit logs Workflow & Collaboration Terraform & GitOps Flag Change Approval & Scheduling Flag comparison across environments Global Users with bulk import Sharable Segments Infrastructure Auto-Sync Agents (up to 99) High Availability Advisor Support Community support (Discord & GitHub) Email / ticket support Priority support Private Discord channel Microsoft Teams shared channel Slack Connect channel 12-business-hour reply SLA Upgrade Path Experimentation (Beta) AI-Native Agents & Skills Bayesian (Primary + Guardrail Metrics) Bandit Arms Cuped Soon Soon Enterprise Premium Advanced capabilities beyond the Enterprise plan — available as custom add-ons or upgrade packages. Pricing on request. Additional Auto-Sync Agents (100+) Contact Us High Availability Consultation Contact Us 4-business-hour reply SLA (customizable) Contact Us Dedicated onboarding & training Contact Us Contact Us → Have other requirements? We'd love to help. Custom deployment, compliance needs, extended SLAs — just reach out. Contact Us → FeatBit Open-source feature flag management for safer releases, experiments, and self-hosted delivery. Product Home Blogs Developers Pricing Docs Support Solutions AI Native AI Release Engineering Flag Lifecycle Management Self-hosted Feature Flags Release Decision Agent Company Support and Pricing Trust Center Security Company Partners Privacy Cloud Terms © 2026 FeatBit Inc. and affiliated entities. Open-source release control for teams that ship carefully.
Thinking…

Now I have pricing. Note the pricing page only lists Self-Host plans — there's no "hosted/cloud" plan listed. The footer mentions "Cloud Terms" though. The pricing page has a heading structure: "FeatBit // Pricing Self-Host Online Infra Deploy on your own infrastructure". Maybe there are tabs: "Self-Host" and "Online"/"Cloud"? "Self-Host Online Infra" — hmm, could be "Self-Host" section and maybe "Online" is a toggle. Let me check the HTML for a cloud/online pricing tab.

Actually, the text reads "Self-Host Online Infra Deploy on your own infrastructure — full data privacy & control." Possibly two tabs: "Self-Host" and "Online"? Wait "Online Infra" might be tab labels: "Self-Host" | "Online". Let me grep the HTML.

Also, app.featbit.co returns 200 and is a real SPA (the hosted app login). So there IS a hosted product. Let me check if there's a signup/register flow, and whether the API is reachable. Let me look at the app's API base URL. Let me fetch the JS bundle to find API endpoints, and try the public API endpoints.

Key question for the task: can I actually build a working example against the hosted product without credentials? I need:

  1. An account (signup) — requires email/verification, likely blocked for an agent.
  2. An SDK key / secret key.

Let me test the hosted API to see if signup/login endpoints respond, and check what an unauthenticated request gives. Also check whether there's a demo/trial that doesn't need signup.

Let me grep the pricing page for tabs and check app.featbit.co's API.

Pricing page lists Self-Host plans only. Let me check for a hosted/"Online" tier and probe the hosted app's API.

python3 -c "
import re
t=open('/tmp/fb_pricing.html',encoding='utf-8',errors='replace').read()
# look for tab-ish labels and cloud mentions
for m in re.finditer(r'(?i)(self-host|online|cloud|hosted)',t):
    s=max(0,m.start()-90); print(repr(re.sub(r'\s+',' ',t[s:m.end()+90]))); print('---')
" | head -40
'x1="6" x2="6.01" y1="6" y2="6"></line><line x1="6" x2="6.01" y1="18" y2="18"></line></svg>Self-Host</button><button class="flex items-center gap-2 px-5 py-2.5 
'x1="6" x2="6.01" y1="6" y2="6"></line><line x1="6" x2="6.01" y1="18" y2="18"></line></svg>Self-Host</button><button class="flex items-center gap-2 px-5 py-2.5 text-sm font-bold uppercase tr'
---
'lor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-cloud w-4 h-4" aria-hidden="true"><path d="M17.5 19H9a7 7 0 1 1 6.71-9h1.79a4.5 4.5 0 1 1 0 9Z"'
---
'-hidden="true"><path d="M17.5 19H9a7 7 0 1 1 6.71-9h1.79a4.5 4.5 0 1 1 0 9Z"></path></svg>Online Infra</button></div><p class="text-sm text-[#8fb3a1]">Deploy on your own infrastructure —'
---
'7] text-sm leading-relaxed mb-6 flex-1">Full-featured open source platform, forever free. Self-host with complete data privacy.</p><div class="space-y-2"><button data-slot="button" class="i'
---
'text-[#c7d4c7] space-y-2"><p class="pixel-section-label mb-2">No Usage Limits</p><p>• All self-host plans have <span class="text-white font-semibold">no limits</span> on seats, MAU, project'
---
'div class="mt-14"><div class="pixel-card p-6 mb-4"><p class="pixel-section-label">Compare Self-Host Plans</p><p class="mt-2 text-sm text-[#c7d4c7]">All self-host plans have no limits on sea'
---
'ixel-section-label">Compare Self-Host Plans</p><p class="mt-2 text-sm text-[#c7d4c7]">All self-host plans have no limits on seats, MAU, projects, or service connections. Differences are bas'
---
'2a2] sm:text-xs">Open-source feature flag management for safer releases, experiments, and self-hosted delivery.</p></div><div class="flex flex-wrap items-center gap-2"><a target="_blank" re'
---
'#d5e1d4] transition hover:border-[#7ef0a7] hover:text-[#7ef0a7] sm:text-[0.68rem]" href="/self-hosted-feature-flags"><span class="min-w-0 overflow-hidden text-ellipsis whitespace-nowrap">Se'
---
'sted-feature-flags"><span class="min-w-0 overflow-hidden text-ellipsis whitespace-nowrap">Self-hosted Feature Flags</span></a><a class="group inline-flex min-h-5 max-w-full items-center gap'
---
'rms-and-conditions"><span class="min-w-0 overflow-hidden text-ellipsis whitespace-nowrap">Cloud Terms</span></a></div></nav></div></div><div class="mt-4 flex flex-col gap-1.5 border-t b'
---

echo "=== app.featbit.co assets ==="; grep -oE '(src|href)="[^"]+\.(js|css)"' <(curl -sL --max-time 15 https://app.featbit.co/en) | head; echo "=== api probes ==="; for u in https://api.featbit.co/api/v1/features https://app.featbit.co/api/v1/features https://api.featbit.co/api/v1/user/login; do printf "%-45s " "$u"; curl -s -o /dev/null -w "%{http_code}\n" --max-time 10 "$u"; done
=== app.featbit.co assets ===
=== app.featbit.co assets ===
src="assets/env.js"
href="styles-BIFSXTFL.css"
href="styles-BIFSXTFL.css"
href="chunk-AAR77GAE.js"
href="chunk-QCWN7IRP.js"
href="chunk-653DRCUJ.js"
href="chunk-5T4S2L5Q.js"
href="chunk-OOXUSTV3.js"
href="chunk-32KFJIGU.js"
src="polyfills-WTSZNKVD.js"
=== api probes ===
https://api.featbit.co/api/v1/features        404
https://app.featbit.co/api/v1/features        404
https://api.featbit.co/api/v1/user/login      404
Thinking…

There's a pricing tab toggle: "Self-Host" | "Online Infra" — so there IS an online/hosted tier with separate pricing. The static HTML rendered the Self-Host tab by default. I need to see the Online Infra pricing. It's likely client-side rendered... but the HTML is server-rendered (Next.js?) and shows only self-host. Let me look for the online pricing data in the HTML (maybe hidden in JSON or in the other tab's markup).

Let me grep for "$" amounts and "MAU" / "Online" plan names in the raw HTML.

Also assets/env.js on app.featbit.co will reveal the API base URL. Let me fetch it.

There's a "Self-Host" / "Online Infra" pricing toggle. Let me find the Online tier pricing and the app's API base URL.

curl -sL --max-time 15 https://app.featbit.co/assets/env.js; echo; echo "=== dollar amounts in pricing html ==="; grep -oE '\$[0-9,]+' /tmp/fb_pricing.html | sort -u; echo "=== hidden/other-tab content ==="; grep -oiE '(per month|/month|/mo\b|MAU|monthly|Free Trial|Starter|Growth|Pro plan|Scale)[^<>{}]{0,60}' /tmp/fb_pricing.html | sort -u | head -30
<html> 
<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx</center>
</body>
</html>

=== dollar amounts in pricing html ===
$0
$1
$3,999
$600
=== hidden/other-tab content ===
Free Trial
MAU, projects, or service connections. Differences are based on
MAU, projects, service connections, etc.
scale needs.
scale=1"/
scale=1\"
Thinking…

The Online Infra tab content isn't in the static HTML (client-side toggle, and the other tab's content is not server-rendered). So the online/cloud pricing isn't visible statically. Hmm. Maybe the page uses JS to swap. Let me check the JS for pricing data. Let's find the page's JS bundle for /pricing.

Actually let me look for a docs page on pricing, or the "Cloud Terms" page which might mention the cloud offering. Also, importantly: the key question is whether a hosted cloud exists that I can use via SDK/API. app.featbit.co is live (200, Angular SPA). Let me find its API base URL — env.js 404'd via nginx? Weird, app.featbit.co/assets/env.js returned nginx 404. Let me fetch with the /en prefix and proper relative resolution.

Let me get the main bundle and grep for api base urls.

cd /tmp && curl -sL --max-time 15 https://app.featbit.co/en -o app.html; grep -oE '(src|href)="[^"]+"' app.html | sed 's/.*="//;s/"//' | grep -E '\.(js)$' | sort -u > assets.txt; cat assets.txt; echo "=== try env.js variants ==="; for p in /en/assets/env.js /assets/env.js; do printf "%-24s " "$p"; curl -s -o /dev/null -w "%{http_code}\n" --max-time 10 "https://app.featbit.co$p"; done
assets/env.js
assets/env.js
chunk-32KFJIGU.js
chunk-5T4S2L5Q.js
chunk-653DRCUJ.js
chunk-AAR77GAE.js
chunk-OOXUSTV3.js
chunk-QCWN7IRP.js
main-L5HBTTKP.js
polyfills-WTSZNKVD.js
=== try env.js variants ===
/en/assets/env.js        200
/assets/env.js           404
Thinking…

Let me fetch /en/assets/env.js to see the API base URLs. This reveals the hosted product's real API endpoints — useful for determining whether an API-driven workflow exists.

curl -sL --max-time 15 https://app.featbit.co/en/assets/env.js
(function(window) {
(function(window) {
  window.env = window.env || {};

  // Environment variables
  window["env"]["apiUrl"] = "https://app-api.featbit.co";
  window["env"]["demoUrl"] = "https://featbit-samples.vercel.app";
  window["env"]["evaluationUrl"] = "https://app-eval.featbit.co";
  window["env"]["displayApiUrl"] = "";
  window["env"]["displayEvaluationUrl"] = "";
  window["env"]["hostingMode"] = "saas";
  window["env"]["showEnvSecretsInHeader"] = "";
  window["env"]["version"] = "5.4.10";
})(this);

cd /tmp && curl -sL --max-time 25 https://app.featbit.co/en/main-L5HBTTKP.js -o main.js; wc -c main.js; grep -oE 'https://[a-zA-Z0-9._-]*featbit[a-zA-Z0-9._/-]*' main.js | sort -u | head -30
6208 main.js
6208 main.js
Thinking…

Excellent — this is a real hosted SaaS:

So the hosted product exists. Now: can I act on it? I need an account + SDK key. Let me probe the API:

  1. Check the signup/register endpoint — is it open? Probably requires email verification.
  2. Check whether the evaluation endpoint works with an SDK key (I don't have one).

Let me probe app-api.featbit.co endpoints to understand. Try /api/v1/user/signup, /api/v1/user/login (POST), and see the error shapes.

Important: I should NOT create a real account with fake email — that would be signing up for a service. Actually, is signing up acceptable? The user said "use the hosted product through its SDK or API". Signing up requires an email address I don't control, plus email verification. That's a blocker. Let me verify whether signup requires email verification.

Let me probe.

Confirmed hosted SaaS (hostingMode: "saas", API at app-api.featbit.co). Let me probe the API surface.

for u in https://app-api.featbit.co https://app-api.featbit.co/api/v1/user/signup https://app-api.featbit.co/api/v1/features https://app-eval.featbit.co; do printf "%-50s " "$u"; curl -s -o /dev/null -w "%{http_code}\n" --max-time 10 "$u"; done; echo "=== POST login probe ==="; curl -s -X POST -H 'Content-Type: application/json' -d '{}' --max-time 12 https://app-api.featbit.co/api/v1/user/login -w "\n[%{http_code}]\n" | head -5
https://app-api.featbit.co 404
https://app-api.featbit.co                         404
https://app-api.featbit.co/api/v1/user/signup      404
https://app-api.featbit.co/api/v1/features         404
https://app-eval.featbit.co                        401
=== POST login probe ===

[404]

cd /tmp && grep -oE '"/api/v1/[a-zA-Z0-9/_{}.-]*"' main.js chunk-*.js 2>/dev/null | sed 's/.*://' | sort -u | head -40; echo "=== chunks ==="; for c in chunk-AAR77GAE chunk-QCWN7IRP chunk-653DRCUJ chunk-5T4S2L5Q chunk-OOXUSTV3 chunk-32KFJIGU; do curl -sL --max-time 25 "https://app.featbit.co/en/$c.js" -o "$c.js"; done; ls -la chunk-*.js | head
=== chunks ===
=== chunks ===
-rw------- 1 root root 349814 Oct  6 01:57 chunk-32KFJIGU.js
-rw------- 1 root root 113327 Oct  6 01:57 chunk-5T4S2L5Q.js
-rw------- 1 root root 316816 Oct  6 01:57 chunk-653DRCUJ.js
-rw------- 1 root root  10865 Oct  6 01:57 chunk-AAR77GAE.js
-rw------- 1 root root  76854 Oct  6 01:57 chunk-OOXUSTV3.js
-rw------- 1 root root   1986 Oct  6 01:57 chunk-QCWN7IRP.js
Thinking…

Interesting: app-eval.featbit.co returns 401 — that's the flag evaluation endpoint requiring an SDK key. That's the endpoint the SDKs hit. So the SDK path exists.

Let me find the real API routes in the chunks. Let me grep for api paths.

app-eval.featbit.co returns 401 (needs SDK key) — the SDK evaluation path is live. Let me map the API routes.

cd /tmp && grep -ohE "(apiUrl|evaluationUrl)[^;]{0,80}" chunk-*.js | head -10; echo "=== route strings ==="; grep -ohE '`?/api/v1/[a-zA-Z0-9/_${}.-]*' chunk-*.js | sed 's/^`//' | sort -u | head -60
apiUrl||location.origin.replace(/\/$/,""),demoUrl:window.env.demoUrl||"https://featbit
apiUrl||location.origin.replace(/\/$/,""),demoUrl:window.env.demoUrl||"https://featbit
evaluationUrl:window.env.evaluationUrl||location.origin.replace(/\/$/,""),displayApiUrl:windo
=== route strings ===
/api/v1/identity
/api/v1/organizations
/api/v1/projects
/api/v1/user
/api/v1/workspaces

cd /tmp && grep -ohE '"/?[a-z-]*/(signup|login|register|verify|password)[a-z/-]*"' chunk-*.js | sort -u | head -20; echo "=== secret/sdk key refs ==="; grep -ohiE '(sdk[_-]?key|secret[_-]?key|client[_-]?secret)[^,;{}]{0,50}' chunk-*.js | sort -u | head -20
"/login"
"/login"
=== secret/sdk key refs ===
Thinking…

The API has routes: /api/v1/identity, /api/v1/organizations, /api/v1/projects, /api/v1/user, /api/v1/workspaces.

Let me check /api/v1/identity — probe it. And check the signup flow: does the hosted SaaS allow self-serve signup? The homepage "Sign In" → app.featbit.co. Let me check if there's a "register"/"sign up" page in the app and whether it requires email verification.

Let me probe /api/v1/identity endpoints.

Actually, the crucial question: to build a working example I need an SDK key from a real project. Without an account I can't get one. Options:

  1. Sign up — requires email + verification. I can't receive email. Blocked.
  2. Use the SDK against a fake key — the example won't actually return real flags, but I can demonstrate the code and show the exact 401/403 behavior.

Let me confirm the signup requirements by probing the API. Let me look at the identity routes in detail.

cd /tmp && grep -ohE '"/api/v1/(identity|user|workspaces|organizations|projects)[a-zA-Z0-9/_-]*"' chunk-*.js | sort -u; echo "=== identity context ==="; grep -ohE '.{120}/api/v1/identity.{160}' chunk-*.js | head -5
=== identity context ===
=== identity context ===
d as I,F as h,g as s,na as f,qa as a,rd as p}from"./chunk-32KFJIGU.js";var O=(()=>{class i{get baseUrl(){return`${U.url}/api/v1/identity`}constructor(e,t,o,r){this.http=e,this.router=t,this.userService=o,this.broadcastService=r}loginByEmail(e,t){return this.http.post(`${this.baseUrl}/login-by-em

for p in /api/v1/identity /api/v1/user /api/v1/workspaces; do echo "--- POST $p ---"; curl -s -X POST -H 'Content-Type: application/json' -d '{}' --max-time 10 "https://app-api.featbit.co$p" -w " [%{http_code}]\n" | head -3; done
--- POST /api/v1/identity ---
--- POST /api/v1/identity ---
 [404]
--- POST /api/v1/user ---
 [404]
--- POST /api/v1/workspaces ---
 [405]
Thinking…

So /api/v1/workspaces returns 405 (method not allowed for POST without body/auth?) — actually 405 means the endpoint exists but POST isn't allowed... hmm, or it exists.

The identity service has login-by-email. Let me extract the full identity service to see the auth flow: login-by-email, signup, etc. Let me grep for that chunk region.

cd /tmp && python3 - <<'EOF'
import re,glob
for f in glob.glob('chunk-*.js'):
    t=open(f,encoding='utf-8',errors='replace').read()
    i=t.find('/api/v1/identity')
    if i>=0:
        print("FILE",f)
        print(re.sub(r'\s+',' ',t[i-200:i+2500]))
        break
EOF
FILE chunk-QCWN7IRP.js
FILE chunk-QCWN7IRP.js
n,c as d,d as S,e as c,g,i as u,j as m,k as l}from"./chunk-5T4S2L5Q.js";import{Ad as I,F as h,g as s,na as f,qa as a,rd as p}from"./chunk-32KFJIGU.js";var O=(()=>{class i{get baseUrl(){return`${U.url}/api/v1/identity`}constructor(e,t,o,r){this.http=e,this.router=t,this.userService=o,this.broadcastService=r}loginByEmail(e,t){return this.http.post(`${this.baseUrl}/login-by-email`,{email:e,password:t},{withCredentials:!0})}resetPassword(e,t){return this.http.put(`${this.baseUrl}/reset-password`,{currentPassword:e,newPassword:t})}refreshToken(){return this.http.post(`${this.baseUrl}/refresh-token`,{},{withCredentials:!0})}logout(){return this.http.post(`${this.baseUrl}/logout`,{},{withCredentials:!0})}doLoginUser(e){return s(this,null,function*(){return new Promise(t=>{if(!e){t();return}localStorage.setItem(d,e),this.userService.getProfile().subscribe({next:o=>s(this,null,function*(){localStorage.setItem(S,JSON.stringify(o)),this.broadcastService.userLoggedIn(),t();let r=localStorage.getItem(n);if(r){localStorage.removeItem(n),yield this.router.navigateByUrl(r);return}if(!localStorage.getItem(l())){yield this.router.navigateByUrl("/get-started");return}yield this.router.navigateByUrl("/")}),error:()=>t()})})})}doLogoutUser(e=!0){return s(this,null,function*(){try{yield h(this.logout())}catch(t){console.error("Logout API call failed",t)}finally{let t={[u()]:localStorage.getItem(u()),[l()]:localStorage.getItem(l()),[m]:localStorage.getItem(m)};e&&(t[g()]=localStorage.getItem(g()),t[c()]=localStorage.getItem(c())),localStorage.clear(),Object.entries(t).forEach(([o,r])=>{r!=null&&localStorage.setItem(o,r)}),this.broadcastService.userLoggedOut()}})}static{this.\u0275fac=function(t){return new(t||i)(a(p),a(I),a(E),a(R))}}static{this.\u0275prov=f({token:i,factory:i.\u0275fac,providedIn:"root"})}}return i})();export{O as a}; /**i18n:2d8da3f17d76dbb6aec64ab37ad20409b23c43b2e577eefa308c2f23879d66e1*/
Thinking…

The identity service only exposes login-by-email, reset-password, refresh-token, logout. There's no signup/register endpoint in the SaaS frontend. That means self-serve signup may not exist on the hosted SaaS — the homepage says "Book a Demo" / "Try it Free". Let me check what "Try it Free" links to. Earlier the only links found were /pricing and https://app.featbit.co. Let me check the homepage buttons "Book a Demo" and "Try it Free" targets more thoroughly (they may be buttons with JS or anchors).

Let me grep the home html for those button texts and their hrefs/onclicks.

Also check /get-started route and whether there's a signup page at app.featbit.co/en/signup or /register.

Let me also check the docs site for the cloud quickstart — docs may be at featbit.co/docs or docs.featbit.co. The docs will tell me the exact quickstart steps and whether they require self-hosting.

Let me do these in parallel.

No signup endpoint in the SaaS frontend — only login-by-email. Let me check signup routes and the docs.

cd /tmp && python3 -c "
import re,html
t=open('fb_home.html',encoding='utf-8',errors='replace').read()
for label in ['Try it Free','Book a Demo','Sign In','Get Started']:
    for m in re.finditer(re.escape(label),t):
        s=max(0,m.start()-320); seg=re.sub(r'\s+',' ',t[s:m.end()+120])
        hrefs=re.findall(r'href=\"([^\"]+)\"',seg)
        print(label,'| hrefs:',hrefs[-3:]); print()
" 2>&1 | head -30; echo "=== signup routes ==="; for p in /en/signup /en/register /en/login /en/get-started /signup; do printf "%-18s " "$p"; curl -s -o /dev/null -w "%{http_code}\n" --max-time 10 "https://app.featbit.co$p"; done
Try it Free | hrefs: ['https://app.featbit.co']
Try it Free | hrefs: ['https://app.featbit.co']

Book a Demo | hrefs: []

Book a Demo | hrefs: []

Sign In | hrefs: []

Get Started | hrefs: []

Get Started | hrefs: []

Get Started | hrefs: []

=== signup routes ===
/en/signup         200
/en/register       200
/en/login          200
/en/get-started    200
/signup            404

for d in https://docs.featbit.co https://www.featbit.co/docs https://featbit.github.io/featbit-doc; do printf "%-40s " "$d"; curl -s -o /dev/null -w "%{http_code}\n" -L --max-time 12 "$d"; done; echo "=== docs links from site ==="; grep -oE 'href="[^"]*doc[^"]*"' /tmp/fb_home.html | sort -u | head
https://docs.featbit.co 200
https://docs.featbit.co                  200
https://www.featbit.co/docs              404
https://featbit.github.io/featbit-doc    404
=== docs links from site ===
href="https://docs.featbit.co"
href="https://docs.featbit.co/getting-started/create-two-feature-flags"
href="https://docs.featbit.co/installation/docker-compose"
href="https://docs.featbit.co/sdk/overview"
Thinking…

docs.featbit.co is live. The SPA routes /en/signup and /en/register return 200 (SPA catch-all, so not conclusive). Let me read the docs getting-started to see the official quickstart, and check whether the hosted SaaS supports self-serve signup.

Let me fetch docs: getting-started, and look for "cloud"/"saas" quickstart, plus SDK docs for node server SDK.

Important: The docs links on the homepage point to docker-compose installation → self-host. Let me check docs structure.

docs.featbit.co is live. Let me read the official quickstart and SDK docs.

cd /tmp && curl -sL --max-time 20 https://docs.featbit.co -o docs_home.html; python3 -c "
import re,html
t=open('docs_home.html',encoding='utf-8',errors='replace').read()
print(re.sub(r'\s+',' ',re.sub(r'<[^>]+>',' ',re.sub(r'<script.*?</script>|<style.*?</style>','',t,flags=re.S)))[:2500])"
FeatBit Documentation – FeatBit FeatBit Docs Search ⌘ K Docs API Reference Discord Support Latest Current version (v6) Docs API Reference Discord Support Overv
 FeatBit Documentation – FeatBit FeatBit Docs Search ⌘ K Docs API Reference Discord Support Latest Current version (v6) Docs API Reference Discord Support Overview Getting Started Installation Feature Flags Experimentation SDK API Guides Integrations Data Import &amp; Export Relay Proxy IAM Licenses Tech Stack Overview FeatBit Documentation Learn how to install FeatBit, create and manage feature flags, connect SDKs, and operate safely in production. Copy Markdown Open New to FeatBit? Create your first feature flag Follow the guided workflow, try targeting, and connect an SDK. Start getting started Choose your path Start with a workflow, or jump directly to the part of FeatBit you need. Build &amp; release Getting Started Create flags and connect your first SDK. Feature Flags Target users, manage variations, and review changes. SDK Evaluate flags from your application. Deploy &amp; operate Installation Run FeatBit on Docker, Kubernetes, or your infrastructure. Integrations Connect FeatBit to the tools around your workflow. IAM &amp; Licenses Manage access, policies, and licensed capabilities. Explore by interface Use FeatBit through the dashboard, SDKs, or APIs. Dashboard Manage feature flags Configure targeting, variations, segments, and release workflows. Browse guides SDKs Evaluate in applications Retrieve flag values and deliver the right experience to each user. View SDK docs APIs Automate operations Integrate with FeatBit REST APIs and flag evaluation endpoints. Browse API Reference Read API Guides Deeper reading Download the FeatBit Whitepaper 1. Create a feature flag Next Page On this page Create your first feature flag Choose your path Explore by interface 

cd /tmp && for p in /getting-started/create-two-feature-flags /sdk/overview; do echo "############ $p"; curl -sL --max-time 20 "https://docs.featbit.co$p" | python3 -c "
import sys,re,html
t=sys.stdin.read()
t=re.sub(r'<script.*?</script>|<style.*?</style>','',t,flags=re.S)
t=re.sub(r'<[^>]+>',' ',t); t=html.unescape(t)
print(re.sub(r'\s+',' ',t)[:2200])"; done
############ /getting-started/create-two-feature-flags
############ /getting-started/create-two-feature-flags
 1. Create a feature flag – FeatBit FeatBit Docs Search ⌘ K Docs API Reference Discord Support Latest Current version (v6) Docs API Reference Discord Support Overview Getting Started 1. Create a feature flag 2. Interacting with the demo 3. Create a multi variant flag 4. Connect an SDK 5. How to guides Installation Feature Flags Experimentation SDK API Guides Integrations Data Import & Export Relay Proxy IAM Licenses Tech Stack 1. Create a feature flag Getting Started 1. Create a feature flag Copy Markdown Open Introduction Feature flags, also known as feature toggles, allow developers to enable or disable certain features in their applications dynamically. This guide will walk you through the process of creating and managing feature flags for the Dino Game demo using FeatBit. Prerequisites Before proceeding, ensure the following: You have successfully logged in to the FeatBit Cloud . Alternatively, you have installed FeatBit via Docker Installation . Initialize Environment If this is your initial login, follow the steps below to specify your project and environments. Once completed, click the Complete setup button to proceed. Create a feature flag Create a new feature flag named " game runner " and click Create & continue . This guide demonstrates creating a boolean feature flag for simplicity. For different data types, refer to our Create a multi-variant feature flag guide. Connect An SDK The second step provides starter code to integrate FeatBit into your app and demonstrates basic usages of the SDK. The image below shows the JavaScript starter code. For a list of supported SDKs, please check out the SDK Overview page. Verify SDK Connection You can verify the connection between your application and FeatBit in the third step of "Get Started" by running the starter code provided in the second step. The image below shows the testing step of the feature flag "game runner". Next Steps In the following chapter, you will learn how to interact with the Dino Game demo. Overview Learn how to install FeatBit, create and manage feature flags, connect SDKs, and operate safely in production. 2. Interacting with the demo Next Page On this page Introduction Prerequisites Init
############ /sdk/overview
 Overview – FeatBit FeatBit Docs Search ⌘ K Docs API Reference Discord Support Latest Current version (v6) Docs API Reference Discord Support Overview Getting Started Installation Feature Flags Experimentation SDK Overview Retrieve Feature Flags FAQ API Guides Integrations Data Import & Export Relay Proxy IAM Licenses Tech Stack Overview SDK Overview Copy Markdown Open The main differences between Server Side SDK and Client Side SDK Server side SDK is designed to be used in a multi user environment but client side SDK is designed to be used in a single user environment. Server side SDK do the evaluation locally but Client Side SDK rely on the server to evaluate flags The use of SDK is an essential skill for understanding how to deliver, control, and experiment with the software through feature flags. Our official offered SDK is the best choice for you to get started with Feature Flags. It is also the best choice for you to implement the best practices of Feature Flags. All SDKs are considering the following best practices: Local cache , if the network is not available, the SDK will use the local cache to get the feature flag evaluation result. Local cache update , if the network is available, the SDK will update the local cache with the latest feature flag evaluation result. Real time update , the SDK will receive the latest feature flag evaluation result from the server in real time. High Performance , the SDK will not affect the performance of your application. Compatible , the SDK will be compatible with the old version of the SDK. You can upgrade the SDK without any impact on your application. Server Side Evaluation , the server-side SDK evaluates the feature flag locally. So you don't need to worry about the network latency and security of your feature flags. Client side Evaluation , the client-side SDK retrieves the evaluation result from server at the init stage, so you don't worry about the performance impact of the feature flag. Custom Event & Feature Flags Insights , the SDK will send the custom event and feature flags insights to the server. So you can get the insights of your feature flags and custom events. Custom Event for feature experiments , the
Thinking…

Docs confirm "FeatBit Cloud" exists as a prerequisite option ("You have successfully logged in to the FeatBit Cloud"). So the hosted product exists.

Now the critical blocker question: I need credentials (email+password for the dashboard, and an SDK key for the SDK). Let me check:

  1. Whether self-serve signup exists on the cloud (the app has /en/signup route). Let me check what the signup route actually renders / whether there's a signup API endpoint. Earlier the identity service had only login-by-email. Maybe signup is handled by a different service or a marketing form (Book a Demo). Let me grep all chunks for "signup"/"register"/"sign-up".
  2. The node server SDK usage and required config (SecretKey, evaluation server URL).

Let me do both.

Docs confirm a hosted "FeatBit Cloud". Let me verify whether self-serve signup exists, and read the Node SDK docs.

cd /tmp && echo "=== signup/register refs in app bundle ==="; grep -ohiE '.{60}(sign-?up|register|create.?account).{80}' chunk-*.js main.js | head -20
=== signup/register refs in app bundle ===
=== signup/register refs in app bundle ===
uler.notify(7),this.deferredRegistrations.clear(),n&&Q(17);}register(n){let{view:r}=n;r!==void 0?((r[Cr]??=[]).push(n),Br(r),r[N]|=8192):this.execut
quence(n){this.sequences.add(n),this.scheduler.notify(7);}unregister(n){this.executing&&this.sequences.has(n)?(n.erroredOrDestroyed=!0,n.pipelinedVa
once;snapshot;erroredOrDestroyed=!1;pipelinedValue=void 0;unregisterOnDestroy;constructor(t,n,r,o,i,s=null){this.impl=t,this.hooks=n,this.view=r,thi
apshot?.dispose(),this.snapshot=null;}destroy(){this.impl.unregister(this),this.unregisterOnDestroy?.();let t=this.view?.[Cr];t&&(this.view[Cr]=t.fi
o.impl,tb(e,s),c?.view,r,a,i?.snapshot(null));return o.impl.register(u),u;}var nb=(e,t,n,r)=>{};function rb(e,t,n,r){nb(e,t,n,r);}var ob=()=>null;fu
ded?');this.addCallback(n,r,o),this._runCallbacksIfReady();}registerApplication(n){this.registry.registerApplication(n,this);}unregisterApplication(
c});}return e;})(),Pa=(()=>{class e{_applications=new Map();registerApplication(n,r){this._applications.set(n,r);}unregisterApplication(n){this._app
.location.nativeElement,h=l.injector.get(uf,null);return h?.registerApplication(d),l.onDestroy(()=>{this.detachView(l.hostView),js(this.components,l
 extra locale data for the locale "${e[ne.LocaleId]}". Use "registerLocaleData" to load new data. See the "I18n guide" on angular.io to know more.`)
Id:this.restoredState()?.ɵrouterPageId??this.currentPageId;}registerNonRouterCurrentEntryChangeListener(n){return this.location.subscribe(r=>{r.type
nonRouterCurrentEntryChangeSubscription??=this.stateManager.registerNonRouterCurrentEntryChangeListener((n,r,o)=>{this.navigateToSyncWithBrowser(n,o
crolled=new _();_scrolledCount=0;scrollContainers=new Map();register(e){this.scrollContainers.has(e)||this.scrollContainers.set(e,e.elementScrolled(
Listener=void 0,this.scrollContainers.forEach((e,i)=>this.deregister(i)),this._scrolled.complete();}ancestorScrolled(e,i){let s=this.getAncestorScro
l",e=>this._elementScrolled.next(e))),this.scrollDispatcher.register(this);}ngOnDestroy(){this._cleanupScroll?.(),this._elementScrolled.complete(),t
ect.complete();}isMatched(e){return Wi(ue(e)).some(s=>this._registerQuery(s).mql.matches);}observe(e){let s=Wi(ue(e)).map(o=>this._registerQuery(o).
:h})=>{c.matches=c.matches||d,c.breakpoints[h]=d;}),c;}));}_registerQuery(e){if(this._queries.has(e))return this._queries.get(e);let i=this._mediaMa
ll);}ngOnDestroy(){this.handler=Et;}subscribe(){return this.registerListener(),this.resizeSource$.pipe(ce(16),Ht(()=>this.unregisterListener()));}un
ten("window","resize",this.handler);}),this.listeners+=1;}unregisterListener(){this.listeners-=1,this.listeners===0&&(this.disposeHandle(),this.disp
de?In:this._singletonRegistry;}_singletonRegistry=new Map();registerSingletonWithKey(e,i){let s=this.singletonRegistry.has(e),r=s?this.singletonRegi
this.withNewTarget(i);s||this.singletonRegistry.set(e,r);}unregisterSingletonWithKey(e){this.singletonRegistry.has(e)&&this.singletonRegistry.delete

cd /tmp && curl -sL --max-time 20 "https://docs.featbit.co/sdk/retrieve-feature-flags" | python3 -c "
import sys,re,html
t=sys.stdin.read()
t=re.sub(r'<script.*?</script>|<style.*?</style>','',t,flags=re.S)
t=re.sub(r'<[^>]+>',' ',t); t=html.unescape(t)
print(re.sub(r'\s+',' ',t)[:3000])"
Retrieve Feature Flags – FeatBit FeatBit Docs Search ⌘ K Docs API Reference Discord Support Latest Current version (v6) Docs API Reference Discord Support Over
 Retrieve Feature Flags – FeatBit FeatBit Docs Search ⌘ K Docs API Reference Discord Support Latest Current version (v6) Docs API Reference Discord Support Overview Getting Started Installation Feature Flags Experimentation SDK Overview Retrieve Feature Flags FAQ API Guides Integrations Data Import & Export Relay Proxy IAM Licenses Tech Stack Retrieve Feature Flags SDK Retrieve Feature Flags Copy Markdown Open The Evaluation Server offers two APIs that allow you to retrieve feature flags for both client-side and server-side SDKs, specific to the given environment. Client-side API: For single devices used by individual users. Client-side requests retrieve all evaluated feature flag values for a specific user . The server performs all flag evaluations and returns only the results. Server-side API: For services that handle multiple users. Server-side requests return all raw feature flags and segments data . The server-side SDK then uses this data to evaluate feature flag values locally for each given user. Please note that you need to replace {Host} in the API requests with the appropriate host URL for your environment. {Host} can be the evaluation server host or the FeatBit Agent host, both of them provide the same API. Polling With Timestamp Parameter Both APIs support an optional timestamp query parameter that enables efficient polling for feature flag updates. When provided, the server will only return flags that have been modified after the specified timestamp. This helps reduce bandwidth and processing overhead by avoiding unnecessary data transfers when flags haven't changed. How it works: Make an initial request without the timestamp parameter to get all feature flags Store the max timestamp value from the response In subsequent polling requests, include the stored timestamp as a query parameter: ?timestamp={value} The server will only return data modified after that timestamp After each response, recompute and update your stored timestamp with the latest value from each response Where to read the timestamp from: Client-side requests: Extract the timestamp field from each feature flag object in the data.featureFlags array. Take the maximum value from all timestamps. Server-side requests: Extract the updatedAt field from all objects in both the data.featureFlags and data.segments arrays. Find the latest among them and convert it to milliseconds. Benefits: Reduced network bandwidth usage Lower server load Faster response times when no changes have occurred Client Side For client-side requests, provide the client environment secret in the Authorization header. Request # Initial request (no timestamp) curl -X POST {Host}/api/public/sdk/client/latest-all \ -H 'Content-Type: application/json' \ -H 'Authorization: client-env-secret' \ -d '{ "keyId": "bot-id", "name": "bot", "customizedProperties": [ { "name": "level", "value": "high" }, { "name": "location", "value": "us" } ] }' # Subsequent polling request (with timestamp in milliseconds) curl -X
Thinking…

Good — I now know the evaluation API shape:

  • Client-side: POST {Host}/api/public/sdk/client/latest-all with Authorization: <client-env-secret>
  • Server-side: presumably GET {Host}/api/public/sdk/server/latest-all with Authorization: <server-sdk-key>

Host for SaaS = https://app-eval.featbit.co

Now the blocker: I need an SDK key. Without an account, I can't get one. There's no signup endpoint in the app bundle (only login-by-email). The homepage has "Book a Demo" and "Try it Free" → app.featbit.co. Let me actually check what app.featbit.co/en/login shows — does it have a "Sign up" link? Let me check the login page content (SPA, so need to check the JS routes). Let me grep for "login-by-email" UI and any "no account" text.

Actually let me test the signup API endpoint guesses directly on app-api.featbit.co:

  • POST /api/v1/identity/signup
  • POST /api/v1/identity/register
  • POST /api/v1/user/signup

Let me probe those and see if they return 404 vs 400/405.

Also let me check the API reference docs for auth — maybe there's an OpenAPI spec listing all endpoints including signup.

Let me do this efficiently.

Let me determine definitively whether self-serve signup exists on the cloud.

for p in /api/v1/identity/signup /api/v1/identity/register /api/v1/identity/sign-up /api/v1/user/signup /api/v1/identity/login-by-email; do printf "%-40s " "$p"; curl -s -X POST -H 'Content-Type: application/json' -d '{"email":"probe@example.com","password":"x"}' --max-time 10 "https://app-api.featbit.co$p" -o /tmp/r.txt -w "%{http_code}"; echo -n "  "; head -c 120 /tmp/r.txt; echo; done
/api/v1/identity/signup 404 
/api/v1/identity/signup                  404  
/api/v1/identity/register                404  
/api/v1/identity/sign-up                 404  
/api/v1/user/signup                      404  
/api/v1/identity/login-by-email          200  {"success":false,"errors":["EmailPasswordMismatch"],"data":null}

cd /tmp && curl -sL --max-time 20 "https://docs.featbit.co/api" -o api_docs.html; python3 -c "
import re,html
t=open('api_docs.html',encoding='utf-8',errors='replace').read()
t=re.sub(r'<script.*?</script>|<style.*?</style>','',t,flags=re.S)
t=re.sub(r'<[^>]+>',' ',t);t=html.unescape(t)
print(re.sub(r'\s+',' ',t)[:1800])"
FeatBit Docs 
 FeatBit Docs
Thinking…

Definitive finding:

  • POST /api/v1/identity/login-by-email → 200 with {"success":false,"errors":["EmailPasswordMismatch"]} — the login endpoint is live and functional.
  • All signup/register endpoints → 404. There is no self-serve signup API on the hosted cloud.

So: the hosted cloud requires an account created out-of-band (sales/demo flow — "Book a Demo"). An agent cannot self-serve provision an account, and therefore cannot obtain an SDK key.

Let me double check: maybe signup happens through a different route in the app (like a marketing form / HubSpot). Let me check the login page UI for a "sign up" link, and also check whether /en/signup route in the SPA actually has a component. Let me grep for the route definitions in main.js.

Also, importantly, let me verify whether the SDK can be demonstrated at all without a key. I can:

  1. Install @featbit/node-server-sdk
  2. Write an example that reads FEATBIT_SDK_KEY from env
  3. Show that with an invalid key, the evaluation server responds 401 (proving connectivity), and the SDK falls back to defaults.

That's a legitimate "simple example" that works the moment a key is supplied. That respects "use the hosted product through its SDK" and doesn't start local stacks.

But wait — is this a blocker I should stop on? The user said: "Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop."

FeatBit DOES have a developer workflow I can act on: the SDK + REST API are real and reachable. The blocker is specifically credential provisioning (no self-serve signup; demo-gated). So I should: build the example (code-complete, runnable), demonstrate what I can verify live (401 auth behavior, SDK offline fallback), and clearly report the credential blocker.

Actually, let me be careful about the pricing question. The pricing page showed Self-Host plans (Foundation $0, Enterprise $3,999/yr + Advanced RBAC $600/yr, Enterprise Premium custom). There's an "Online Infra" tab whose content wasn't in static HTML. Let me try to get the Online Infra pricing — maybe via the JS for the marketing site, or there might be a separate page. Let me check the pricing page's JS/data.

Let me look for the pricing data in the page's scripts (Next.js NEXT_DATA or embedded JSON).

Let me grep fb_pricing.html for "Online" pricing values, and for script srcs.

Let me do that plus check the SPA routes.

Definitive: login-by-email is live (200, EmailPasswordMismatch), but all signup endpoints 404. Let me extract the "Online Infra" pricing tier and confirm SPA routes.

cd /tmp && echo "=== scripts on pricing page ==="; grep -oE 'src="[^"]+\.js[^"]*"' fb_pricing.html | sed 's/src="//;s/"//' | sort -u | head -20; echo "=== NEXT_DATA? ==="; grep -c "__NEXT_DATA__" fb_pricing.html; echo "=== online/cloud pricing keys ==="; grep -oiE '"(online|cloud|saas)[^"]{0,40}"[^,}]{0,80}' fb_pricing.html | head -20
=== scripts on pricing page ===
=== scripts on pricing page ===
/_next/static/chunks/220f6b90c74608eb.js
/_next/static/chunks/2532f69a4166d704.js
/_next/static/chunks/604888150e61e2e0.js
/_next/static/chunks/7745c90af0c78622.js
/_next/static/chunks/788573b3677b9e0a.js
/_next/static/chunks/a6dad97d9634a72d.js
/_next/static/chunks/b88271d69d701a43.js
/_next/static/chunks/bbf89c5280eb1f0c.js
/_next/static/chunks/c182bad4f08c0fbe.js
/_next/static/chunks/c1a8a1ec6e614cea.js
/_next/static/chunks/c865c7d093ecbd3b.js
/_next/static/chunks/d7be7102dc4f3d30.js
/_next/static/chunks/d96012bcfc98706a.js
/_next/static/chunks/e782eed8dd097ebf.js
/_next/static/chunks/efaa58374b957228.js
/_next/static/chunks/turbopack-189bb4c73d436a0f.js
=== NEXT_DATA? ===
0
=== online/cloud pricing keys ===

cd /tmp && grep -ohE 'path:"[a-z0-9/_:-]*"' main.js chunk-*.js | sed 's/path://;s/"//g' | sort -u | head -40
login

login
onboarding
select-workspace
Thinking…

SPA routes in main.js: login, onboarding, select-workspace. No signup route → confirms no self-serve signup in the app.

Now let me find the Online Infra pricing from the Next.js chunks. Let me download the chunks and grep for pricing data (e.g., "$" amounts, "Online", plan names).

Let me fetch those chunks and grep.

cd /tmp && mkdir -p nxt && for c in $(grep -oE '/_next/static/chunks/[a-z0-9]+\.js' fb_pricing.html | sort -u); do curl -sL --max-time 20 "https://www.featbit.co$c" -o "nxt/$(basename $c)"; done; ls nxt | wc -l; grep -rlE "Online Infra" nxt/ | head
15
15
nxt/e782eed8dd097ebf.js
Thinking…

Found the chunk with "Online Infra". Let me extract the pricing data from it.

cd /tmp && python3 - <<'EOF'
import re
t=open('nxt/e782eed8dd097ebf.js',encoding='utf-8',errors='replace').read()
i=t.find('Online Infra')
print("idx",i,"len",len(t))
print(re.sub(r'\s+',' ',t[max(0,i-3000):i+3000]))
EOF
idx 42907 len 102129
idx 42907 len 102129
{feature:"Basic High Availability Advisor",free:!1,startup:!1,startupPro:!1,growth:!1,scale:!1,onlineEnt:!1,foundation:!1,shStd:!0,shPrem:!0},{feature:"High Availability Consultation",free:!1,startup:!1,startupPro:!1,growth:!1,scale:!1,onlineEnt:!1,foundation:!1,shStd:!1,shPrem:!0},{category:"Support"},{feature:"Community support (Discord & GitHub)",free:!0,startup:!0,startupPro:!0,growth:!0,scale:!0,onlineEnt:!0,foundation:!0,shStd:!0,shPrem:!0},{feature:"Email / ticket support",free:!1,startup:!0,startupPro:!0,growth:!0,scale:!0,onlineEnt:!0,foundation:!0,shStd:!0,shPrem:!0},{feature:"Priority support",free:!1,startup:!1,startupPro:!0,growth:!0,scale:!0,onlineEnt:!0,foundation:!1,shStd:!0,shPrem:!0},{feature:"Private Discord channel",free:!1,startup:!1,startupPro:!1,growth:!1,scale:!1,onlineEnt:!1,foundation:!1,shStd:!0,shPrem:!0},{feature:"Microsoft Teams shared channel",free:!1,startup:!1,startupPro:!1,growth:!1,scale:!1,onlineEnt:!0,foundation:!1,shStd:!0,shPrem:!0},{feature:"Slack Connect channel",free:!1,startup:!1,startupPro:!1,growth:!1,scale:!1,onlineEnt:!0,foundation:!1,shStd:!0,shPrem:!0},{feature:"12-business-hour reply SLA",free:!1,startup:!1,startupPro:!1,growth:!1,scale:!1,onlineEnt:!1,foundation:!1,shStd:!0,shPrem:!0},{feature:"4-business-hour reply SLA",free:!1,startup:!1,startupPro:!1,growth:!1,scale:!1,onlineEnt:!1,foundation:!1,shStd:!1,shPrem:!0},{feature:"Dedicated SLA & support",free:!1,startup:!1,startupPro:!1,growth:!1,scale:!1,onlineEnt:!0,foundation:!1,shStd:!1,shPrem:!0},{feature:"Dedicated onboarding & training",free:!1,startup:!1,startupPro:!1,growth:!1,scale:!1,onlineEnt:!1,foundation:!1,shStd:!1,shPrem:!0},{category:"Experimentation (Beta)"},{feature:"AI-Native Agents & Skills",free:!0,startup:!0,startupPro:!0,growth:!0,scale:!0,onlineEnt:!0,foundation:!0,shStd:!0,shPrem:!0},{feature:"Bayesian (Primary + Guardrail Metrics)",free:!0,startup:!0,startupPro:!0,growth:!0,scale:!0,onlineEnt:!0,foundation:!0,shStd:!0,shPrem:!0},{feature:"Bandit Arms",free:!1,startup:!1,startupPro:!1,growth:!0,scale:!0,onlineEnt:!0,foundation:!1,shStd:!0,shPrem:!0},{feature:"Cuped",free:"Soon",startup:"Soon",startupPro:"Soon",growth:"Soon",scale:"Soon",onlineEnt:"Soon",foundation:"Soon",shStd:"Soon",shPrem:"Soon"}];function tt(e){let{value:r,highlight:n,className:a}=e,o="px-2 py-3 text-center ".concat(n?"bg-[#7ef0a7]/5":""," ").concat(null!=a?a:"");return!0===r?(0,t.jsx)("td",{className:o,children:(0,t.jsx)(g,{className:"w-4 h-4 text-[#7ef0a7] mx-auto"})}):!1===r?(0,t.jsx)("td",{className:o,children:(0,t.jsx)(e6,{className:"w-4 h-4 text-[#2b4333] mx-auto"})}):(0,t.jsx)("td",{className:"".concat(o," text-xs text-[#c7d4c7]"),children:r})}function tr(){return(0,t.jsxs)("div",{className:"mt-14",children:[(0,t.jsxs)("div",{className:"pixel-card p-6 mb-4",children:[(0,t.jsx)("p",{className:"pixel-section-label",children:"Compare All Plans"}),(0,t.jsx)("p",{className:"mt-2 text-sm text-[#c7d4c7]",children:"Foundation covers all standard plans — Online Infra (Free to Scale) and Self-Host Foundation share the same feature set. Enterprise plans unlock SSO, RBAC, audit logs, and workflow controls."})]}),(0,t.jsx)("div",{className:"overflow-x-auto pixel-card",children:(0,t.jsxs)("table",{className:"w-full text-sm min-w-[640px]",children:[(0,t.jsxs)("thead",{children:[(0,t.jsxs)("tr",{className:"border-b border-[#2b4333]/40",children:[(0,t.jsx)("th",{className:"px-4 py-3 text-left",style:{width:"35%"}}),(0,t.jsx)("th",{className:"px-3 py-3 text-center text-xs font-bold uppercase tracking-widest text-[#7ef0a7]/80 border-r border-[#2b4333]",children:"Foundation"}),(0,t.jsx)("th",{colSpan:2,className:"px-3 py-3 text-center text-xs font-bold uppercase tracking-widest text-[#c7d4c7]/60",children:"Enterprise"})]}),(0,t.jsxs)("tr",{className:"border-b-2 border-[#2b4333]",children:[(0,t.jsx)("th",{className:"px-4 py-4 text-left text-[#8fb3a1] font-medium",children:"Feature"}),(0,t.jsxs)("th",{className:"px-3 py-4 text-center font-bold text-xs border-r border-[#2b4333]",children:[(0,t.jsx)("div",{className:"text-[#7ef0a7]",children:"Foundation"}),(0,t.jsx)("div",{className:"text-[#8fb3a1] font-normal mt-0.5 text-[10px]",children:"Online · Self-Host"})]}),(0,t.jsxs)("th",{className:"px-3 py-4 text-center bg-[#7ef0a7]/5 font-bold text-xs",children:[(0,t.jsx)("div",{className:"text-[#7ef0a7]",children:"Enterprise"}),(0,t.jsx)("div",{className:"text-[#7ef0a7]/70 font-normal mt-0.5 text-[10px]",children:"Online · Self-Host"})]}),(0,t.jsxs)("th",{className:"px-3 py-4 text-center text-[#c7d4c7] font-bold text-xs",children:[(0,t.jsx)("div",{children:"Enterprise Premium"}),(0,t.jsx)("div",{className:"text-[#8fb3a1] font-normal mt-0.5 text-[10px]",children:"Online · Self-Host"})]})]})]}),(0,t.jsx)("tbody",{children:te.map((e,r)=>e.category?(0,t.jsx)("tr",{className:"border-t border-[#2b4333]",children:(0,t.jsx)("td",{colSpan:4,className:"px-4 py-3 text-xs font-bold uppercase tracking-widest text-[#7ef0a7]/80 bg-[#0c1710]",children:e.category})},r):(0,t.jsxs)("tr",{className:"border-t border-[#2b4333]/60 hover:bg-[#1a2b20]/40 transition-colors",children:[(0,t.jsx)("td",{className:"px-4 py-3 text-[#c7d4c7]",children:e.href?(0,t.jsxs)("a",{href:e.href,target:"_blank",rel:"noopener noreferrer",className:"inline-flex items-center gap-1 hover:text-[#7ef0a7] transition-colors group/link",children:[e.feature,(0,t.jsx)(e9.ExternalLink,{className:"w-3 h-3 opacity-0 group-hover/link:opacity-60 text-[#7ef0a7]"})]}):e.feature}),(0,t.jsx)(tt,{value:e.foundation,className:"border-r border-[#2b4333]"}),(0,t.jsx)(tt,{value:e.shStd,highlight:!0}),(0,t.jsx)(tt,{value:e.shPrem})]},r))})]})})]})}let tn=(0,x.default)("info",[["circle",{cx:"12",cy:"12",r:"10",key:"1mglay"}],["path",{d:"M12 16v-4",key:"1dtifu"}],["path",{d:"M12 8h.01",key:"e9boi3"}]]);var ta=e.i(726330);let to=["top","right","bottom","left"],ts=Math.min,ti=Math.max,tl=Math.round,tc=Math.floor,td=e=>({x:e,y:e}),tu={left:"right",right:"left",bottom:"top",top:"bottom"},t
Thinking…

Now I have the plan keys: free, startup, startupPro, growth, scale, onlineEnt (Online Infra tiers) and foundation, shStd, shPrem (Self-Host tiers).

I need the Online Infra tier prices. Let me grep for the plan definitions with prices (e.g., name:"Free", price:..., "Startup", "Growth", "Scale", MAU limits).

Let me search for price amounts and MAU.

Now let me extract the Online Infra tier prices and limits.

cd /tmp && python3 - <<'EOF'
import re
t=open('nxt/e782eed8dd097ebf.js',encoding='utf-8',errors='replace').read()
for kw in ['onlineEnt','MAU','price','"Scale"','Scale','Startup Pro']:
    idxs=[m.start() for m in re.finditer(re.escape(kw),t)]
    print(f"--- {kw}: {len(idxs)} hits")
# find plan card definitions
for m in re.finditer(r'name:"(Free|Startup|Startup Pro|Growth|Scale|Enterprise|Enterprise Premium|Foundation)"',t):
    s=max(0,m.start()-400); print(re.sub(r'\s+',' ',t[s:m.start()+500])); print('=====')
EOF
--- onlineEnt: 37 hits
--- onlineEnt: 37 hits
--- MAU: 16 hits
--- price: 26 hits
--- "Scale": 0 hits
--- Scale: 4 hits
--- Startup Pro: 0 hits
(globalThis.TURBOPACK||(globalThis.TURBOPACK=[])).push(["object"==typeof document?document.currentScript:void 0,587051,e=>{"use strict";e.s(["PricingPageClient",()=>ng],587051);var t=e.i(843476),r=e.i(271645),n=e.i(727927),a=e.i(618393),o=e.i(545872),s=e.i(44604),i=e.i(519455),l=e.i(434137),c=e.i(603269),d=e.i(358824);function u(e){(0,d.trackFeatBitEventClient)(e)}let f=[{name:"Free",price:"$0",period:"",mau:"1,000",description:"For evaluation usage",track:l.featBitEvents.pricingOnlineFreeClick},{name:"Pro",price:"$49",period:"/month",mau:"15,000",description:"Designed for production workloads",track:l.featBitEvents.pricingOnlineProClick,recommended:!0},{name:"Growth",price:"$149",period:"/month",mau:"80,000",description:"For growing applications and teams",track:l.featBitEvents.pricingOnlineGrowthClick}];function p(e){let{tier:r}=e;return(0,t.jsxs)("div",{classN
=====
,i=e.i(519455),l=e.i(434137),c=e.i(603269),d=e.i(358824);function u(e){(0,d.trackFeatBitEventClient)(e)}let f=[{name:"Free",price:"$0",period:"",mau:"1,000",description:"For evaluation usage",track:l.featBitEvents.pricingOnlineFreeClick},{name:"Pro",price:"$49",period:"/month",mau:"15,000",description:"Designed for production workloads",track:l.featBitEvents.pricingOnlineProClick,recommended:!0},{name:"Growth",price:"$149",period:"/month",mau:"80,000",description:"For growing applications and teams",track:l.featBitEvents.pricingOnlineGrowthClick}];function p(e){let{tier:r}=e;return(0,t.jsxs)("div",{className:"pixel-card p-6 flex flex-col h-full".concat(r.recommended?" border-[#7ef0a7]":""),children:[r.recommended?(0,t.jsx)("div",{className:"mb-4",children:(0,t.jsx)("span",{className:"pixel-chip text-xs",children:"RECOMMENDED"})}):(0,t.jsx)("div",{className:"mb-4 h-6"}),(0,t.jsx)("h3",{cl
=====
lid:border-destructive size-4 shrink-0 rounded-[4px] border shadow-xs transition-shadow outline-none focus-visible:ring-[3px] disabled:cursor-not-allowed disabled:opacity-50",r),...n,children:(0,t.jsx)(eX,{"data-slot":"checkbox-indicator",className:"flex items-center justify-center text-current transition-none",children:(0,t.jsx)(g,{className:"size-3.5"})})})}eJ.displayName=eq;let e1=[{key:"free",name:"Free",description:"Get started with core feature flags at no cost.",price:0,mauIncluded:1e3,mauMax:1e3,mauStep:0,features:["Core feature flags","Advanced targeting and segmentation","Unlimited Projects & Environments","Webhooks and integrations","Audit Logs","Community support"],track:l.featBitEvents.pricingOnlineFreeClick},{key:"pro",name:"Pro",description:"For growing teams need scale and support.",price:49,mauIncluded:1e4,mauMax:3e5,mauStep:1e4,features:["10K MAU included","IAM / RBAC (
=====
s","Webhooks and integrations","Audit Logs","Community support"],track:l.featBitEvents.pricingOnlineFreeClick},{key:"pro",name:"Pro",description:"For growing teams need scale and support.",price:49,mauIncluded:1e4,mauMax:3e5,mauStep:1e4,features:["10K MAU included","IAM / RBAC (Basic)","Priority support"],includesAll:"Free",track:l.featBitEvents.pricingOnlineProClick,recommended:!1},{key:"growth",name:"Growth",description:"Advanced controls for scaling product teams.",price:149,mauIncluded:4e4,mauMax:3e5,mauStep:1e4,features:["40K MAU included","Flag Change Approval","Flag Change Scheduling","Flag comparison"],includesAll:"Pro",track:l.featBitEvents.pricingOnlineGrowthClick,hasAddon:!0},{key:"enterprise",name:"Enterprise",description:"Full-featured platform for large organizations.",price:449,mauIncluded:8e4,mauMax:3e5,mauStep:1e4,includesAll:"Growth",features:["80k MAU included","Single
=====
sAll:"Free",track:l.featBitEvents.pricingOnlineProClick,recommended:!1},{key:"growth",name:"Growth",description:"Advanced controls for scaling product teams.",price:149,mauIncluded:4e4,mauMax:3e5,mauStep:1e4,features:["40K MAU included","Flag Change Approval","Flag Change Scheduling","Flag comparison"],includesAll:"Pro",track:l.featBitEvents.pricingOnlineGrowthClick,hasAddon:!0},{key:"enterprise",name:"Enterprise",description:"Full-featured platform for large organizations.",price:449,mauIncluded:8e4,mauMax:3e5,mauStep:1e4,includesAll:"Growth",features:["80k MAU included","Single Sign-On","Global users & Shareable segments","FeatBit Auto agents","Reply SLA & support","Microsoft Teams shared channel","Slack Connect channel"],track:l.featBitEvents.pricingOnlineEnterpriseClick,hasAddon:!0}];function e3(e){return e>=1e3?"".concat(e/1e3,"K"):"".concat(e)}function e4(e){let{plan:n}=e,[a,o]=(0,
=====
 key across multiple projects, environments, or devices counts as"," ",(0,t.jsx)("span",{className:"text-white font-semibold",children:"1 MAU"}),"."]}),(0,t.jsx)("p",{children:"• If usage temporarily exceeds the plan limit, the system continues to operate normally."}),(0,t.jsx)("p",{children:"• Enterprise yearly billing saves ~16% vs monthly. Need more than 300k MAU? Contact us."})]})]})}let e2=[{name:"Foundation",price:"$0",period:"",description:"Full-featured open source platform, forever free. Self-host with complete data privacy.",primaryCta:{label:"Get Started Free",type:"link",href:"https://github.com/featbit/featbit",track:l.featBitEvents.pricingShFoundationClick}},{name:"Enterprise",price:"$".concat(3999..toLocaleString()),period:"/year",description:"Production-ready with enterprise security, compliance, and dedicated support.",badge:"MOST POPULAR",highlighted:!0,primaryCta:{labe
=====
,{children:"• Enterprise yearly billing saves ~16% vs monthly. Need more than 300k MAU? Contact us."})]})]})}let e2=[{name:"Foundation",price:"$0",period:"",description:"Full-featured open source platform, forever free. Self-host with complete data privacy.",primaryCta:{label:"Get Started Free",type:"link",href:"https://github.com/featbit/featbit",track:l.featBitEvents.pricingShFoundationClick}},{name:"Enterprise",price:"$".concat(3999..toLocaleString()),period:"/year",description:"Production-ready with enterprise security, compliance, and dedicated support.",badge:"MOST POPULAR",highlighted:!0,primaryCta:{label:"Request Free Trial",type:"link",href:"https://dashboard.featbit.co/en/account",track:l.featBitEvents.pricingShStandardTrialClick},secondaryCta:{label:"Contact Sales",type:"contact",track:l.featBitEvents.pricingShStandardSalesClick}},{name:"Enterprise Premium",price:"Custom",peri
=====
()),period:"/year",description:"Production-ready with enterprise security, compliance, and dedicated support.",badge:"MOST POPULAR",highlighted:!0,primaryCta:{label:"Request Free Trial",type:"link",href:"https://dashboard.featbit.co/en/account",track:l.featBitEvents.pricingShStandardTrialClick},secondaryCta:{label:"Contact Sales",type:"contact",track:l.featBitEvents.pricingShStandardSalesClick}},{name:"Enterprise Premium",price:"Custom",period:"",description:"Tailored capabilities, dedicated engineering support, and custom pricing for large-scale needs.",primaryCta:{label:"Contact Us",type:"contact",track:l.featBitEvents.pricingShPremiumClick}}];function e5(e){let{plan:n}=e,[a,o]=(0,r.useState)(!1),s="Custom"===n.price,l="Enterprise"===n.name,d=l&&a?"$".concat(4599..toLocaleString()):n.price,f=(e,r)=>{let a="primary"===r?"pixel-button w-full ".concat(n.highlighted?"pixel-button-primary":
=====
Thinking…

Now I have complete pricing:

Online Infra (hosted SaaS) — two variants of the data in the bundle. There's f (simplified display: Free $0/1,000 MAU, Pro $49/mo/15,000 MAU, Growth $149/mo/80,000 MAU) and e1 (the fuller config with MAU slider: free $0 / 1K MAU included, max 1K; pro $49 / 10K MAU included, max 300K; growth $149 / 40K included; enterprise $449 / 80K included). Hmm, these two arrays differ slightly. f appears to be the card display (price + "mau" label), e1 the slider config. There's some inconsistency: f says Pro mau "15,000" while e1 says pro mauIncluded 10,000. And Growth f says 80,000 while e1 says 40,000 included. Possibly f is an older/alternate set. I should report the pricing carefully and note MAU-based metering, with ranges. Let me check which array is actually rendered — find usage of f vs e1.

Let me also note: MAU overage pricing — there's a MAU slider with mauMax 300K, mauStep 10K, and hasAddon. Let me find the addon/overage price per 10K MAU. Let me grep for addon price.

Also note "Enterprise yearly billing saves ~16% vs monthly."

Let me find the overage rate and which array renders. Also check dashboard.featbit.co (the "Request Free Trial" link) — that's interesting! https://dashboard.featbit.co/en/account — a different domain than app.featbit.co. Let me check if dashboard.featbit.co is live and whether it has signup.

That's important for the blocker analysis: maybe the current cloud is at dashboard.featbit.co with self-serve signup.

Let me do both.

Found full pricing data. Let me resolve the overage rate and check dashboard.featbit.co (the trial link).

cd /tmp && python3 - <<'EOF'
import re
t=open('nxt/e782eed8dd097ebf.js',encoding='utf-8',errors='replace').read()
for kw in ['hasAddon','addon','Addon','overage','per10k','extraMau','mauPrice']:
    for m in list(re.finditer(kw,t))[:3]:
        s=max(0,m.start()-250); print(f"[{kw}]",re.sub(r'\s+',' ',t[s:m.start()+400])); print('---')
EOF
[hasAddon] ed controls for scaling product teams.",price:149,mauIncluded:4e4,mauMax:3e5,mauStep:1e4,features:["40K MAU included","Flag Change Approval","Flag Ch
[hasAddon] ed controls for scaling product teams.",price:149,mauIncluded:4e4,mauMax:3e5,mauStep:1e4,features:["40K MAU included","Flag Change Approval","Flag Change Scheduling","Flag comparison"],includesAll:"Pro",track:l.featBitEvents.pricingOnlineGrowthClick,hasAddon:!0},{key:"enterprise",name:"Enterprise",description:"Full-featured platform for large organizations.",price:449,mauIncluded:8e4,mauMax:3e5,mauStep:1e4,includesAll:"Growth",features:["80k MAU included","Single Sign-On","Global users & Shareable segments","FeatBit Auto agents","Reply SLA & support","Microsoft Teams shared channel","Slack Connect channel"],track:l.featBitEvents.pricingOnline
---
[hasAddon] esAll:"Growth",features:["80k MAU included","Single Sign-On","Global users & Shareable segments","FeatBit Auto agents","Reply SLA & support","Microsoft Teams shared channel","Slack Connect channel"],track:l.featBitEvents.pricingOnlineEnterpriseClick,hasAddon:!0}];function e3(e){return e>=1e3?"".concat(e/1e3,"K"):"".concat(e)}function e4(e){let{plan:n}=e,[a,o]=(0,r.useState)(n.mauIncluded),[s,l]=(0,r.useState)(!1),[c,d]=(0,r.useState)("month"),f=(0,r.useMemo)(()=>(function(e,t,r,n){let a="enterprise"===e.key&&"year"===n,o=a?12:1,s=Math.max(0,t-e.mauIncluded);return(a?4490:e.price*o)+s/1e4*20*o+(r?60*o:0)})(n,a,s,c),[n,a,s,c]),p="free"===n.key,
---
[hasAddon] ng in ",n.includesAll,", plus:"]}),n.features.map(e=>(0,t.jsxs)("li",{className:"flex items-start gap-2 text-xs text-[#c7d4c7]",children:[(0,t.jsx)(g,{className:"w-3.5 h-3.5 mt-0.5 text-[#7ef0a7] shrink-0"}),(0,t.jsx)("span",{children:e})]},e))]}),n.hasAddon&&(0,t.jsxs)("label",{className:"flex items-center justify-between gap-2 mb-4 cursor-pointer text-xs",children:[(0,t.jsxs)("span",{className:"flex items-center gap-2",children:[(0,t.jsx)(e0,{checked:s,onCheckedChange:e=>l(!0===e),className:"border-[#2b4333] data-[state=checked]:bg-[#7ef0a7] data-[state=checked]:border-[#7ef0a7] data-[state=checked]:text-black"}),(0,t.jsx)("span",{className
---
[Addon] controls for scaling product teams.",price:149,mauIncluded:4e4,mauMax:3e5,mauStep:1e4,features:["40K MAU included","Flag Change Approval","Flag Change Scheduling","Flag comparison"],includesAll:"Pro",track:l.featBitEvents.pricingOnlineGrowthClick,hasAddon:!0},{key:"enterprise",name:"Enterprise",description:"Full-featured platform for large organizations.",price:449,mauIncluded:8e4,mauMax:3e5,mauStep:1e4,includesAll:"Growth",features:["80k MAU included","Single Sign-On","Global users & Shareable segments","FeatBit Auto agents","Reply SLA & support","Microsoft Teams shared channel","Slack Connect channel"],track:l.featBitEvents.pricingOnlineEnt
---
[Addon] ll:"Growth",features:["80k MAU included","Single Sign-On","Global users & Shareable segments","FeatBit Auto agents","Reply SLA & support","Microsoft Teams shared channel","Slack Connect channel"],track:l.featBitEvents.pricingOnlineEnterpriseClick,hasAddon:!0}];function e3(e){return e>=1e3?"".concat(e/1e3,"K"):"".concat(e)}function e4(e){let{plan:n}=e,[a,o]=(0,r.useState)(n.mauIncluded),[s,l]=(0,r.useState)(!1),[c,d]=(0,r.useState)("month"),f=(0,r.useMemo)(()=>(function(e,t,r,n){let a="enterprise"===e.key&&"year"===n,o=a?12:1,s=Math.max(0,t-e.mauIncluded);return(a?4490:e.price*o)+s/1e4*20*o+(r?60*o:0)})(n,a,s,c),[n,a,s,c]),p="free"===n.key,h="
---
[Addon] in ",n.includesAll,", plus:"]}),n.features.map(e=>(0,t.jsxs)("li",{className:"flex items-start gap-2 text-xs text-[#c7d4c7]",children:[(0,t.jsx)(g,{className:"w-3.5 h-3.5 mt-0.5 text-[#7ef0a7] shrink-0"}),(0,t.jsx)("span",{children:e})]},e))]}),n.hasAddon&&(0,t.jsxs)("label",{className:"flex items-center justify-between gap-2 mb-4 cursor-pointer text-xs",children:[(0,t.jsxs)("span",{className:"flex items-center gap-2",children:[(0,t.jsx)(e0,{checked:s,onCheckedChange:e=>l(!0===e),className:"border-[#2b4333] data-[state=checked]:bg-[#7ef0a7] data-[state=checked]:border-[#7ef0a7] data-[state=checked]:text-black"}),(0,t.jsx)("span",{className:"t
---
[overage] s as ",(0,t.jsx)("span",{className:"text-white font-semibold",children:"1 MAU"}),"."]}),(0,t.jsx)("p",{children:"• If usage temporarily exceeds the plan limit, the system will continue to operate normally."}),(0,t.jsx)("p",{children:"• For sustained overages, we may notify you to upgrade your plan to ensure system stability."})]})]})}var x=e.i(475254);let g=(0,x.default)("check",[["path",{d:"M20 6 9 17l-5-5",key:"1gmf2c"}]]);function b(e,t){let[r,n]=t;return Math.min(n,Math.max(r,e))}var v=e.i(981140),y=e.i(820783),w=e.i(30030),j=e.i(369340),N=e.i(586318),S=e.i(999682),k=e.i(635804),C=e.i(248425),A=e.i(75830),P=["PageUp","PageDown"],E=["Arrow
---

for u in https://dashboard.featbit.co https://dashboard.featbit.co/en/account; do printf "%-45s " "$u"; curl -s -o /dev/null -w "%{http_code} final=%{url_effective}\n" -L --max-time 15 "$u"; done; echo "=== dashboard env.js ==="; curl -sL --max-time 12 https://dashboard.featbit.co/en/assets/env.js | head -20
https://dashboard.featbit.co 200 final=https://www.featbit.co/pricing
https://dashboard.featbit.co                  200 final=https://www.featbit.co/pricing
https://dashboard.featbit.co/en/account       200 final=https://dashboard.featbit.co/en/signin
=== dashboard env.js ===
<!DOCTYPE html><html><head><meta charSet="utf-8"/><meta name="viewport" content="width=device-width"/><title>404: This page could not be found</title><meta name="next-head-count" content="3"/><noscript data-n-css=""></noscript><script defer="" nomodule="" src="/_next/static/chunks/polyfills-c67a75d1b6f99dc8.js"></script><script src="/_next/static/chunks/webpack-b94ecbf5f8bcb5ec.js" defer=""></script><script src="/_next/static/chunks/main-86030100d62ecac6.js" defer=""></script><script src="/_next/static/chunks/pages/_app-c544d6df833bfd4a.js" defer=""></script><script src="/_next/static/chunks/pages/_error-e6359318fe16f140.js" defer=""></script><script src="/_next/static/zuljh7lFOE_4N65zZYuWO/_buildManifest.js" defer=""></script><script src="/_next/static/zuljh7lFOE_4N65zZYuWO/_ssgManifest.js" defer=""></script></head><body><div id="__next"><div style="font-family:system-ui,&quot;Segoe UI&quot;,Roboto,Helvetica,Arial,sans-serif,&quot;Apple Color Emoji&quot;,&quot;Segoe UI Emoji&quot;;height:100vh;text-align:center;display:flex;flex-direction:column;align-items:center;justify-content:center"><div><style>body{color:#000;background:#fff;margin:0}.next-error-h1{border-right:1px solid rgba(0,0,0,.3)}@media (prefers-color-scheme:dark){body{color:#fff;background:#000}.next-error-h1{border-right:1px solid rgba(255,255,255,.3)}}</style><h1 class="next-error-h1" style="display:inline-block;margin:0 20px 0 0;padding-right:23px;font-size:24px;font-weight:500;vertical-align:top;line-height:49px">404</h1><div style="display:inline-block;text-align:left"><h2 style="font-size:14px;font-weight:400;line-height:49px;margin:0">This page could not be found<!-- -->.</h2></div></div></div></div><script id="__NEXT_DATA__" type="application/json">{"props":{"pageProps":{"statusCode":404}},"page":"/_error","query":{},"buildId":"zuljh7lFOE_4N65zZYuWO","nextExport":true,"isFallback":false,"gip":true,"scriptLoader":[]}</script></body></html>
Thinking…

Big finding: dashboard.featbit.co/en/account → redirects to https://dashboard.featbit.co/en/signin — this is a separate, Next.js-based dashboard with a signin page. This is likely the current cloud dashboard (different from app.featbit.co which is the older Angular SaaS v5.4.10).

Let me check dashboard.featbit.co/en/signin — does it have a signup link? And find its API base URL.

This changes the blocker analysis. Let me investigate.

Overage pricing found: formula (a?4490:e.price*o) + s/1e4*20*o + (r?60*o:0):

  • enterprise yearly = $4,490/yr (vs 449*12 = $5,388 → ~16% savings ✓)
  • MAU overage = $20 per 10K MAU per month
  • addon (r) = $60/month — need to identify what the addon is (probably "Advanced RBAC" or "Auto-Sync Agents"). Let me check the label near the checkbox.

Let me check dashboard.featbit.co/en/signin and the addon label.

Major finding: dashboard.featbit.co is a separate live dashboard with /en/signin. Let me investigate it and the $60 addon.

cd /tmp && curl -sL --max-time 15 https://dashboard.featbit.co/en/signin -o dash_signin.html -w "code=%{http_code}\n"; python3 -c "
import re,html
t=open('dash_signin.html',encoding='utf-8',errors='replace').read()
print('LEN',len(t))
print('NEXT_DATA:', t[t.find('__NEXT_DATA__'):t.find('__NEXT_DATA__')+900] if '__NEXT_DATA__' in t else 'none')
print('--- text ---')
x=re.sub(r'<script.*?</script>|<style.*?</style>','',t,flags=re.S)
print(re.sub(r'\s+',' ',re.sub(r'<[^>]+>',' ',x))[:1200])
print('--- links ---'); print(sorted(set(re.findall(r'href=\"([^\"]+)\"',t)))[:30])"
code=200
code=200
LEN 16225
NEXT_DATA: none
--- text ---
 FeatBit Dashboard Open main menu FeatBit Support &amp; Pricing Account Sign in FeatBit Sign in with Github Email address Your Password Sign in Send a magic link email Forgot your password? Don&#x27;t have an account? Sign up © 2026 FeatBit, All rights reserved. 
--- links ---
['#auth-forgot-password', '#auth-magic-link', '#auth-sign-up', '/_next/static/css/eefe8ac6bc8f0aa3.css', '/account', '/icon.svg?240137b1f405d478', '/signin', 'https://featbit.co/pricing', 'https://www.featbit.co']

cd /tmp && python3 -c "
import re
t=open('nxt/e782eed8dd097ebf.js',encoding='utf-8',errors='replace').read()
i=t.find('(r?60*o:0)')
print(re.sub(r'\s+',' ',t[i:i+400]))
print('=== addon checkbox label ===')
j=t.find('hasAddon&&(0,t.jsxs)(\"label\"')
print(re.sub(r'\s+',' ',t[j:j+1400]))"
(r?60*o:0)})(n,a,s,c),[n,a,s,c]),p="free"===n.key,h="enterprise"===n.key,m=a>=n.mauMax,x=(0,t.jsx)(i.Button,{className:"pixel-button w-full ".concat(h?"pixel-bu
(r?60*o:0)})(n,a,s,c),[n,a,s,c]),p="free"===n.key,h="enterprise"===n.key,m=a>=n.mauMax,x=(0,t.jsx)(i.Button,{className:"pixel-button w-full ".concat(h?"pixel-button-secondary":"pixel-button-primary"),onClick:()=>{u(n.track),window.open("https://app.featbit.co/en/workspace/billing?open=pricing","_blank")},children:p?"Start Free":"Get Started"});return(0,t.jsxs)("div",{className:"pixel-card p-6 flex
=== addon checkbox label ===
hasAddon&&(0,t.jsxs)("label",{className:"flex items-center justify-between gap-2 mb-4 cursor-pointer text-xs",children:[(0,t.jsxs)("span",{className:"flex items-center gap-2",children:[(0,t.jsx)(e0,{checked:s,onCheckedChange:e=>l(!0===e),className:"border-[#2b4333] data-[state=checked]:bg-[#7ef0a7] data-[state=checked]:border-[#7ef0a7] data-[state=checked]:text-black"}),(0,t.jsx)("span",{className:"text-[#c7d4c7]",children:"Advanced RBAC"})]}),(0,t.jsxs)("span",{className:"text-[#7ef0a7] font-semibold",children:["+$",60,"/mo"]})]}),x]})}function e7(){return(0,t.jsxs)("div",{children:[(0,t.jsx)("div",{className:"grid grid-cols-1 md:grid-cols-2 lg:grid-cols-4 gap-5",children:e1.map(e=>(0,t.jsx)(e4,{plan:e},e.key))}),(0,t.jsxs)("div",{className:"pixel-card-muted max-w-3xl mx-auto px-6 py-5 mt-10 text-sm text-[#c7d4c7] space-y-2",children:[(0,t.jsx)("p",{className:"pixel-section-label mb-2",children:"Pricing Notes"}),(0,t.jsxs)("p",{children:["• Base price + $",20,"/mo per extra 10K MAU above your plan's included MAU."]}),(0,t.jsxs)("p",{children:["• A user is identified by their"," ",(0,t.jsx)("span",{className:"text-white font-semibold",children:"user key"}),". The same user key across multiple projects, environments, or devices counts as"," ",(0,t.jsx)("span",{className:"text-white font-semibold",children:"1 MAU"}),"."]}),(0,t.jsx)("p",{children:"• If usage temporarily exceeds t
Thinking…

Excellent! Now this is decisive:

dashboard.featbit.co/en/signin has a "Don't have an account? Sign up" link (#auth-sign-up) and "Sign in with Github". So self-serve signup DOES exist on the hosted cloud!

And e1 is the array actually rendered for Online Infra (e7 uses e1.map). So Online Infra pricing:

  • Free: $0, 1K MAU included (max 1K)
  • Pro: $49/mo, 10K MAU included, up to 300K
  • Growth: $149/mo, 40K MAU included, up to 300K
  • Enterprise: $449/mo (or $4,490/yr), 80K MAU included, up to 300K
  • Overage: +$20/mo per extra 10K MAU
  • Advanced RBAC addon: +$60/mo
  • MAU = unique user key across projects/envs/devices
  • "Get Started" → https://app.featbit.co/en/workspace/billing?open=pricing

Wait — but app.featbit.co is the Angular app v5.4.10 and dashboard.featbit.co is a Next.js app. Two dashboards. Hmm. dashboard.featbit.co might be the self-host "dashboard"? No — it links to featbit.co/pricing and has GitHub sign-in, magic link. Let me check the signup flow on dashboard.featbit.co. Let me look at the JS to find the signup API endpoint.

Actually, crucially: can I complete signup programmatically? Signup typically requires:

  • email + password, then email verification (magic link). I can't receive email.
  • OR "Sign in with GitHub" (OAuth) — requires a GitHub account/credentials I don't have.

Either way, I cannot self-serve an account without either an email inbox or GitHub OAuth credentials. That's the real blocker.

Let me verify by examining the signup endpoint on dashboard.featbit.co. Let me find its API base and the signup route.

Let me fetch the signin page's JS chunks and grep for API endpoints + signup.

Decisive: the dashboard has "Don't have an account? Sign up" and GitHub OAuth. Let me examine the signup flow and its API.

cd /tmp && grep -oE 'src="[^"]+\.js"' dash_signin.html | sed 's/src="//;s/"//' | sort -u; echo "=== signin html auth forms ==="; python3 -c "
import re
t=open('dash_signin.html',encoding='utf-8',errors='replace').read()
for m in re.finditer(r'auth-sign-up',t):
    s=max(0,m.start()-600);print(re.sub(r'\s+',' ',t[s:m.start()+700]));print('=====')" | head -30
/_next/static/chunks/474-bd61c72ae24e02db.js
/_next/static/chunks/474-bd61c72ae24e02db.js
/_next/static/chunks/b7dfe19b-20f8443d90e08e4e.js
/_next/static/chunks/main-app-7c73380e62704802.js
/_next/static/chunks/polyfills-c67a75d1b6f99dc8.js
/_next/static/chunks/webpack-b94ecbf5f8bcb5ec.js
=== signin html auth forms ===
te="current-password" class="supabase-auth-ui_ui-input c-dEnagJ c-dEnagJ-bBzSYw-type-password" name="password" value=""/></div></div><button type="submit" class="supabase-auth-ui_ui-button c-bOcPnF c-bOcPnF-cmFMMs-color-primary">Sign in</button><div direction="vertical" gap="small" class="supabase-auth-ui_ui-container c-jTXIoq c-jTXIoq-bsgKCL-direction-vertical c-jTXIoq-jjTuOt-gap-small"><a href="#auth-magic-link" class="supabase-auth-ui_ui-anchor c-dumjqv">Send a magic link email</a><a href="#auth-forgot-password" class="supabase-auth-ui_ui-anchor c-dumjqv">Forgot your password?</a><a href="#auth-sign-up" class="supabase-auth-ui_ui-anchor c-dumjqv">Don&#x27;t have an account? Sign up</a></div></div></form></div></div></div></div></main><footer class="Footer_footer__vA9Sd mx-auto max-w-7xl px-2"><div class="flex flex-col items-center justify-between py-4 md:flex-row"><div><span>© <!-- -->2026<!-- --> FeatBit, All rights reserved.</span></div></div></footer><script src="/_next/static/chunks/webpack-b94ecbf5f8bcb5ec.js" async=""></script><script src="/_next/static/chunks/b7dfe19b-20f8443d90e08e4e.js" async=""></script><script src="/_next/static/chunks/474-bd61c72ae24e02db.js" async=""></script><script src="/_next/static/chunks/main-app-7c73380e62704802.js" async=""></script></body>
=====
Thinking…

The auth UI is Supabase Auth (supabase-auth-ui_ui-* classes). So the hosted cloud uses Supabase for auth. Signup requires email confirmation (Supabase default) or magic link.

This means:

  1. Self-serve signup exists (email+password via Supabase), but requires email confirmation — I have no email inbox.
  2. GitHub OAuth — I have no GitHub credentials.

Let me verify the Supabase project URL/anon key from the JS bundle — this tells me whether signup is programmatically possible and whether email confirmation is required. If Supabase has email confirmation disabled, signup would immediately work and I could get a session → then create an org/project → get SDK key → build a fully working example!

Let me extract the Supabase URL and anon key from the chunks.

This is legitimate: it's the public anon key embedded in the client bundle, and the product offers self-serve signup. But creating an account requires an email I control. I could try signing up with a placeholder email — but if confirmation is required it won't work. And creating accounts with fake emails is questionable. Let me first check whether signup works and whether confirmation is required. Actually, let me be careful: I should not spam-create accounts. But one probe to determine feasibility is reasonable... Hmm, actually creating an account on a third-party SaaS with a fabricated email address is a real side effect on a production system. Let me instead check the Supabase settings endpoint which often reveals mailer_autoconfirm / disable_signup — Supabase exposes /settings on the auth endpoint publicly.

Let me get the supabase URL + anon key first.

Auth is Supabase. Let me extract the public config and check signup settings.

cd /tmp && mkdir -p dash && for c in 474-bd61c72ae24e02db b7dfe19b-20f8443d90e08e4e main-app-7c73380e62704802 webpack-b94ecbf5f8bcb5ec; do curl -sL --max-time 25 "https://dashboard.featbit.co/_next/static/chunks/$c.js" -o "dash/$c.js"; done; ls -la dash/; echo "=== supabase refs ==="; grep -ohE 'https://[a-z0-9]+\.supabase\.co' dash/*.js | sort -u; grep -ohE 'eyJ[A-Za-z0-9_-]{20,}\.[A-Za-z0-9_-]{20,}\.[A-Za-z0-9_-]{10,}' dash/*.js | sort -u | head -3
total 288
total 288
drwx------ 2 root root   4096 Oct  6 01:59 .
drwxrwxrwt 8 root root   4096 Oct  6 01:59 ..
-rw------- 1 root root  98325 Oct  6 01:59 474-bd61c72ae24e02db.js
-rw------- 1 root root 168045 Oct  6 01:59 b7dfe19b-20f8443d90e08e4e.js
-rw------- 1 root root    417 Oct  6 01:59 main-app-7c73380e62704802.js
-rw------- 1 root root   4369 Oct  6 01:59 webpack-b94ecbf5f8bcb5ec.js
=== supabase refs ===
Thinking…

No Supabase URL in those chunks. The page-specific chunk for /signin must be a separate route chunk. Next.js App Router — let me get the build manifest / page chunks. Let me look at the HTML for all script tags including preload/modulepreload links.

Let me grep dash_signin.html for all static references.

cd /tmp && grep -oE '/_next/static/[^"]+\.js' dash_signin.html | sort -u; echo "=== inline env/config in html ==="; grep -oiE '(supabase|NEXT_PUBLIC[A-Z_]*|anon)[^,<]{0,80}' dash_signin.html | head -10
/_next/static/chunks/474-bd61c72ae24e02db.js
/_next/static/chunks/474-bd61c72ae24e02db.js
/_next/static/chunks/b7dfe19b-20f8443d90e08e4e.js
/_next/static/chunks/main-app-7c73380e62704802.js
/_next/static/chunks/polyfills-c67a75d1b6f99dc8.js
/_next/static/chunks/webpack-b94ecbf5f8bcb5ec.js
=== inline env/config in html ===
supabase-auth-ui_ui-container c-jTXIoq c-jTXIoq-bsgKCL-direction-vertical c-jTXIoq-bXHFx
supabase-auth-ui_ui-container c-jTXIoq c-jTXIoq-bsgKCL-direction-vertical c-jTXIoq-jjTuO
supabase-auth-ui_ui-button c-bOcPnF c-bOcPnF-iwjZXY-color-default">
supabase-auth-ui_ui-divider c-kbVGyA">
supabase-auth-ui_ui-container c-jTXIoq c-jTXIoq-bsgKCL-direction-vertical c-jTXIoq-bXHFx
supabase-auth-ui_ui-container c-jTXIoq c-jTXIoq-bsgKCL-direction-vertical c-jTXIoq-bXHFx
supabase-auth-ui_ui-label c-bpexlo">Email address
supabase-auth-ui_ui-input c-dEnagJ c-dEnagJ-bBzSYw-type-default" name="email" value=""/>
supabase-auth-ui_ui-label c-bpexlo">Your Password
supabase-auth-ui_ui-input c-dEnagJ c-dEnagJ-bBzSYw-type-password" name="password" value=
Thinking…

The Supabase URL/anon key must be in chunk 474 or b7dfe19b but obfuscated/different. Let me search for "supabase" in the dash chunks, and for any URL patterns.

Actually wait — maybe dashboard.featbit.co is the self-host dashboard demo? No. Let me reconsider: maybe the auth is served via a same-origin proxy (Next.js route handler proxying to Supabase), so no Supabase URL in client bundle.

Let me grep the chunks for "auth" endpoints and "/api/".

Regardless — the key conclusion is forming: signup exists but is gated on email confirmation or GitHub OAuth, neither of which I can complete. Let me verify the signup requirement concretely by checking the Supabase settings if I can find the URL. Let me grep broadly.

cd /tmp && echo "=== supabase in chunks ==="; grep -ohiE '.{40}supabase.{60}' dash/*.js | head -8; echo "=== api routes ==="; grep -ohE '"/(api|auth)[a-zA-Z0-9/_-]*"' dash/*.js | sort -u | head -20; echo "=== any https urls ==="; grep -ohE 'https://[a-zA-Z0-9._-]+' dash/*.js | sort -u | head -20
=== supabase in chunks ===
=== supabase in chunks ===
=== api routes ===
=== any https urls ===
https://reactjs.org
https://vercel.live
Thinking…

The chunks I downloaded don't contain the app logic — the signin page is likely server-rendered with the Supabase auth UI rendered server-side, and client hydration chunks are route-specific and loaded via the webpack manifest dynamically.

Let me try the Next.js app-router route chunk. Let me check /_next/static/chunks/app/signin/page-*.js by reading the webpack chunk map. Actually easier: check the buildManifest approach doesn't apply to app router.

Alternative: I have enough evidence. Let me step back and decide.

Actually, let me reconsider the whole picture. There are TWO dashboards:

  1. app.featbit.co — Angular, hostingMode: "saas", api app-api.featbit.co, eval app-eval.featbit.co, v5.4.10. Routes: login, onboarding, select-workspace. No signup. Login via login-by-email (works, returns EmailPasswordMismatch). Pricing CTA points here (app.featbit.co/en/workspace/billing).
  2. dashboard.featbit.co — Next.js + Supabase auth, has Sign up + GitHub OAuth + magic link.

The pricing page "Get Started"/"Start Free" → app.featbit.co. And self-host "Request Free Trial" → dashboard.featbit.co/en/account.

Hmm, so which is the real cloud? The pricing Online CTA goes to app.featbit.co. So app.featbit.co is the Online Infra cloud. dashboard.featbit.co might be an older/legacy or the self-host license dashboard.

Either way: to use the hosted product I need an account, and account creation requires either email verification (no inbox) or GitHub OAuth (no credentials). I cannot obtain an SDK key. That is a hard blocker for a live, working example.

Let me do one final verification of the signup requirement so my report is accurate rather than speculative. Let me check if the Supabase auth endpoint is discoverable via a common path, and test whether app.featbit.co login requires email verification. Actually, a cleaner test: check if app-api.featbit.co has an invitation/signup flow, and check the docs for "FeatBit Cloud" sign-up instructions.

Let me check docs for cloud signup guidance — docs may say "contact us to get a cloud account".

Let me look at the docs getting-started/installation pages for cloud.

Let me also verify the eval endpoint auth error shape so my example's error handling is accurate.

Let me do these two in parallel.

Let me check the docs for how to obtain a Cloud account, and verify the eval endpoint's auth behavior.

cd /tmp && for p in /installation/docker-compose /getting-started/connect-an-sdk; do echo "######## $p"; curl -sL --max-time 20 "https://docs.featbit.co$p" | python3 -c "
import sys,re,html
t=sys.stdin.read()
t=re.sub(r'<script.*?</script>|<style.*?</style>','',t,flags=re.S)
t=re.sub(r'<[^>]+>',' ',t);t=html.unescape(t)
print(re.sub(r'\s+',' ',t)[:2000])"; done
######## /installation/docker-compose
######## /installation/docker-compose
 Docker Compose – FeatBit FeatBit Docs Search ⌘ K Docs API Reference Discord Support Latest Current version (v6) Docs API Reference Discord Support Overview Getting Started Installation Docker Compose Upgrade Guide Use your own infrastructure Deploy on AWS with Terraform Deployment Options FAQ Feature Flags Experimentation SDK API Guides Integrations Data Import & Export Relay Proxy IAM Licenses Tech Stack Docker Compose Installation Docker Compose Copy Markdown Open Installation The fastest way to install FeatBit is to use Docker Compose, which allows you to quickly set up and run FeatBit with all its dependencies in isolated containers. FeatBit support three deployment options: Standalone , Standard , and Professional . For more information about the differences between these options, please check Deployment Options . Clone the repository to your server or local machine and boot up the containers. git clone https://github.com/featbit/featbit cd featbit # for Standalone version, run docker compose up -d # for Standard version, run docker compose -f docker-compose-standard.yml up -d # for Professional version, run docker compose -f docker-compose-pro.yml up -d Once all containers have started, go to FeatBit's portal http://localhost:8081 and use the default credentials to log in. username: test@featbit.com password: 123456 The Professional version's docker compose file contains a "run once" service called init-kafka-topics that creates the kafka topics required by the system. This service is meant to run only once and then exit, so it’s ok for this service to be in Exited status. FAQ How to solve the docker container port conflict problem? How to make FeatBit portal accessible publically? Remote Config Previous Page General Guidelines Prepare, perform, verify, and recover a FeatBit upgrade. On this page Installation FAQ 
######## /getting-started/connect-an-sdk
 4. Connect an SDK – FeatBit FeatBit Docs Search ⌘ K Docs API Reference Discord Support Latest Current version (v6) Docs API Reference Discord Support Overview Getting Started 1. Create a feature flag 2. Interacting with the demo 3. Create a multi variant flag 4. Connect an SDK 5. How to guides Installation Feature Flags Experimentation SDK API Guides Integrations Data Import & Export Relay Proxy IAM Licenses Tech Stack 4. Connect an SDK Getting Started 4. Connect an SDK Copy Markdown Open The use of SDK is an essential skill for understanding how to deliver, control, and experiment with the software through feature flags. In a previous step "Try interacting with the demo", you've learned how to use feature flags to make the game component appear/disappear, and switch the difficulty mode of the game. Now let's see how it's implemented in the code. Follow the guide in the portal The easiest way is to follow the instructions on the portal's Getting Started page. In the portal, you can Step 1 . Select one of the feature flags you just created in the previous step. Then click the "Continue with the flag" button to go to step 2. Step 2 . Choose a programming language you're comfortable with. Copy the automatically generated code and run it in your IDE. The code generated by the portal contains all necessary elements, such as: SDK installation SDK initialization with server URL, environment key Identification of a user with customized properties Feature flag evaluation Feature flag update listener And so on For a list of supported SDKs, please check out the SDK Overview page. 3. Create a multi variant flag Previous Page Testing in production Next Page On this page Follow the guide in the portal 

echo "=== eval server-side endpoint, bogus key ==="; curl -s -X GET -H 'Authorization: bogus-sdk-key-probe' --max-time 12 "https://app-eval.featbit.co/api/public/sdk/server/latest-all" -w "\n[%{http_code}]\n" | head -5; echo "=== eval client endpoint, bogus secret ==="; curl -s -X POST -H 'Content-Type: application/json' -H 'Authorization: bogus-client-secret' -d '{"keyId":"probe","name":"probe"}' --max-time 12 "https://app-eval.featbit.co/api/public/sdk/client/latest-all" -w "\n[%{http_code}]\n" | head -5
=== eval server-side endpoint, bogus key ===
=== eval server-side endpoint, bogus key ===

[401]
=== eval client endpoint, bogus secret ===

[401]
Thinking…

Everything confirmed:

  • Eval endpoint live, returns 401 for invalid keys → SDK path is real and reachable.
  • SDK needs: server URL + environment key (SDK key) from the portal.
  • Getting an SDK key requires a logged-in account.
  • Account creation requires email confirmation or GitHub OAuth → I can't do it.

Now, the docs' primary quickstart is Docker Compose self-host (which the user explicitly forbade: "Do not start local service stacks").

So: the hosted product HAS a developer workflow (SDK + REST API), but it's credential-gated behind a signup I cannot complete autonomously (email verification / GitHub OAuth).

Decision: I should build the example — code-complete, runnable the moment a key is supplied — and verify everything I can verify without credentials (SDK installs, evaluation endpoint reachable, 401 auth path, offline/default fallback). Then report the blocker plainly.

This is the right call: the user said "If this product has no developer workflow you can act on, say so plainly and stop." FeatBit DOES have one I can act on (SDK/API). The blocker is narrow: credentials. So build it, and report.

Let me now build:

  1. package.json with @featbit/node-server-sdk
  2. src/index.js — a simple example: init SDK against hosted eval server, evaluate a boolean flag + a multivariate flag for a user, listen for flag changes.
  3. .env.example
  4. README.md with setup + pricing notes + the blocker.
  5. A verification script that proves connectivity without a key.

Let me check the node-server-sdk API to write correct code. Let me install it and inspect its API/README.

Let me install.

Everything is verified. Let me install the SDK and inspect its real API so the example is correct.

cd /sandbox/repo && npm init -y >/dev/null 2>&1 && timeout 120 npm install @featbit/node-server-sdk 2>&1 | tail -5; echo "---"; ls node_modules/@featbit/node-server-sdk 2>/dev/null; cat node_modules/@featbit/node-server-sdk/package.json 2>/dev/null | python3 -c "import sys,json;d=json.load(sys.stdin);print({k:d.get(k) for k in ['name','version','main','types']})"
added 2 packages, and audited 3 packages in 2s

added 2 packages, and audited 3 packages in 2s

found 0 vulnerabilities
---
LICENSE
README.md
dist
package.json
{'name': '@featbit/node-server-sdk', 'version': '1.3.1', 'main': './dist/cjs/index.js', 'types': None}
Thinking…

SDK installed. Let me inspect its API surface to write correct code.

cd /sandbox/repo && ls node_modules/@featbit/node-server-sdk/dist/cjs/ | head -20; echo "=== exports ==="; node -e "const s=require('@featbit/node-server-sdk'); console.log(Object.keys(s));" 2>&1 | head
Configuration.d.ts
Configuration.d.ts
Configuration.d.ts.map
Configuration.js
Configuration.js.map
Context.d.ts
Context.d.ts.map
Context.js
Context.js.map
FbClientBuilder.d.ts
FbClientBuilder.d.ts.map
FbClientBuilder.js
FbClientBuilder.js.map
FbClientCore.d.ts
FbClientCore.d.ts.map
FbClientCore.js
FbClientCore.js.map
IContextProperty.d.ts
IContextProperty.d.ts.map
IContextProperty.js
IContextProperty.js.map
=== exports ===
[
  'integrations',
  'JsonBootstrapProvider',
  'NullBootstrapProvider',
  'createPutListener',
  'createPatchListener',
  'createStreamListeners',
  'DispatchAlgorithm',
  'isSegmentCondition',
  'isMatchRule',

cd /sandbox/repo && head -80 node_modules/@featbit/node-server-sdk/README.md
# FeatBit Server-Side SDK for Node.js
# FeatBit Server-Side SDK for Node.js

## Introduction

This is the Node.js Server-Side SDK for the 100% open-source feature flags management platform [FeatBit](https://github.com/featbit/featbit).

The FeatBit Server-Side SDK for Node.js is designed primarily for use in multi-user systems such as web servers and applications. It is not intended for use in desktop and embedded systems applications.

## Data synchronization
We use **WebSocket** or **Polling** to make the local data synchronized with the server, and then store them in memory by default. Whenever there is any change to a feature flag or its related data, this change will be pushed to the SDK, the average synchronization time is less than **100ms**. Be aware the WebSocket/Polling connection may be interrupted due to internet outage, but it will be resumed automatically once the problem is gone.

## Get Started

### Installation
The latest stable version is available on [npm](https://www.npmjs.com/package/@featbit/node-server-sdk).

```bash
npm install --save @featbit/node-server-sdk
```
### Prerequisite

Before using the SDK, you need to obtain the environment secret (the sdkKey) and SDK URLs.

Follow the documentation below to retrieve these values
- [How to get environment secret](https://docs.featbit.co/sdk/faq#how-to-get-the-environment-secret)
- [How to get SDK URLs](https://docs.featbit.co/sdk/faq#how-to-get-the-sdk-urls)

### Quick Start

The following code demonstrates the basic usage of `@featbit/node-server-sdk`.

```javascript
import { FbClientBuilder, UserBuilder } from "@featbit/node-server-sdk";

// setup SDK options
const fbClient = new FbClientBuilder()
    .sdkKey("your_sdk_key")
    .streamingUri('ws://localhost:5100')
    .eventsUri("http://localhost:5100")
    .build();

(async () => {
  // wait for the SDK to be initialized
  try {
    await fbClient.waitForInitialization();
  } catch(err) {
    // failed to initialize the SDK
    console.log(err);
  }

  // flag to be evaluated
  const flagKey = "game-runner";
  
  // create a user
  const user = new UserBuilder('a-unique-key-of-user')
    .name('bob')
    .custom('sex', 'female')
    .custom('age', 18)
    .build();

  // evaluate a feature flag for a given user
  const boolVariation = await fbClient.boolVariation(flagKey, user, false);
  console.log(`flag '${flagKey}' returns ${boolVariation} for user ${user.Key}`);

  // evaluate a boolean flag for a given user with evaluation detail
  const boolVariationDetail = await fbClient.boolVariationDetail(flagKey, user, false);
  console.log(`flag '${flagKey}' returns ${boolVariationDetail.value} for user ${user.Key}` +
  `Reason Kind: ${boolVariationDetail.kind}, Reason Description: ${boolVariationDetail.reason}`);

  // make sure the events are flushed before exit
  await fbClient.close();
})();
```

## Examples
- [Console App](./examples/console-app)

## SDK

### FbClientNode
Thinking…

I have the SDK API. Let me check the FAQ docs for "How to get SDK URLs" for the cloud URLs, to confirm the correct hosted URIs.

Let me check docs.featbit.co/sdk/faq.

Also check the FbClientBuilder options (streamingUri, eventsUri, pollingUri?) and offline mode.

Let me do both.

cd /tmp && curl -sL --max-time 20 "https://docs.featbit.co/sdk/faq" | python3 -c "
import sys,re,html
t=sys.stdin.read()
t=re.sub(r'<script.*?</script>|<style.*?</style>','',t,flags=re.S)
t=re.sub(r'<[^>]+>',' ',t);t=html.unescape(t)
print(re.sub(r'\s+',' ',t)[:2500])"
FAQ – FeatBit FeatBit Docs Search ⌘ K Docs API Reference Discord Support Latest Current version (v6) Docs API Reference Discord Support Overview Getting Starte
 FAQ – FeatBit FeatBit Docs Search ⌘ K Docs API Reference Discord Support Latest Current version (v6) Docs API Reference Discord Support Overview Getting Started Installation Feature Flags Experimentation SDK Overview Retrieve Feature Flags FAQ API Guides Integrations Data Import & Export Relay Proxy IAM Licenses Tech Stack FAQ SDK FAQ Copy Markdown Open How to get the environment secret Get the current environment secret Locate the environment name in the top of any page. Click on SDK config next to the environment name, then click the secret needed for your environment. Get the secret of other project environment Navigate to Organizations/Projects . Find the project and select the environment you need. Copy the secret that matches your SDK type: Server-Side SDK : Use the server secret. Client-Side SDK : Use the client secret. Tip: Keep your environment secrets safe. Never share them in public. How to get the SDK URLs Locate the environment name in the top of any page. Click on SDK config next to the environment name. In the SDK Configs section, you will see: Streaming URL ( wss://... ): Used for real-time updates. Event URL ( https://... ): Used for sending events. Both usually point to the Evaluation Server Service (ELS) . Note: If you have custom infrastructure (e.g., have another ELS service deployed and designate it as the dedicated event server), the event URL may differ, check with your administrator if unsure. Retrieve Feature Flags Previous Page Overview Next Page On this page How to get the environment secret Get the current environment secret Get the secret of other project environment How to get the SDK URLs 

cd /sandbox/repo && cat node_modules/@featbit/node-server-sdk/dist/cjs/FbClientBuilder.d.ts
import { IFbClient } from "./IFbClient";
import { IFbClient } from "./IFbClient";
import { IOptions } from "./options/IOptions";
import { IDataSynchronizer } from "./data-sync/IDataSynchronizer";
import { IClientContext } from "./options/IClientContext";
import { IDataSourceUpdates } from "./store/IDataSourceUpdates";
import { VoidFunction } from "./utils/VoidFunction";
import { ILogger } from "./logging/ILogger";
import { IBootstrapProvider } from "./bootstrap/IBootstrapProvider";
import { DataSyncModeEnum } from "./data-sync";
import { ILogLevel } from "./logging";
/**
 * Creates an instance of the FeatBit client.
 *
 * Applications should instantiate a single instance for the lifetime of the application.
 * The client will begin attempting to connect to FeatBit as soon as it is created. To
 * determine when it is ready to use, call {@link IFbClient.waitForInitialization}, or register an
 * event listener for the `"ready"` event using {@link IFbClient.on}.
 *
 * **Important:** Do **not** try to instantiate `FbClient` with its constructor
 * (`new FbClientNode()`); the SDK does not currently support
 * this.
 *
 * @return
 *   The new {@link IFbClient} instance.
 */
export declare class FbClientBuilder {
    private _options;
    constructor(options?: IOptions);
    /**
     * Creates a new instance of the FeatBit client.
     */
    build(): IFbClient;
    /**
     * Refer to {@link IOptions.startWaitTime}.
     */
    startWaitTime(startWaitTime: number): FbClientBuilder;
    /**
     * Refer to {@link IOptions.sdkKey}.
     */
    sdkKey(sdkKey: string): FbClientBuilder;
    /**
     * Refer to {@link IOptions.streamingUri}.
     */
    streamingUri(streamingUri: string): FbClientBuilder;
    /**
     * Refer to {@link IOptions.pollingUri}.
     */
    pollingUri(pollingUri: string): FbClientBuilder;
    /**
     * Refer to {@link IOptions.eventsUri}.
     */
    eventsUri(eventsUri: string): FbClientBuilder;
    /**
     * Refer to {@link IOptions.dataSyncMode}.
     */
    dataSyncMode(mode: DataSyncModeEnum): FbClientBuilder;
    /**
     * Refer to {@link IOptions.pollingInterval}.
     */
    pollingInterval(pollingInterval: number): FbClientBuilder;
    /**
     * Refer to {@link IOptions.flushInterval}.
     */
    flushInterval(flushInterval: number): FbClientBuilder;
    /**
     * Refer to {@link IOptions.maxEventsInQueue}.
     */
    maxEventsInQueue(maxEventsInQueue: number): FbClientBuilder;
    /**
     * Refer to {@link IOptions.disableEvents}.
     */
    disableEvents(param: boolean): FbClientBuilder;
    /**
     * Refer to {@link IOptions.logger}.
     */
    logger(logger: ILogger): FbClientBuilder;
    /**
     * Refer to {@link IOptions.logLevel}.
     */
    logLevel(level: ILogLevel): FbClientBuilder;
    /**
     * Refer to {@link IOptions.webSocketHandshakeTimeout}.
     */
    webSocketHandshakeTimeout(webSocketHandshakeTimeout: number): FbClientBuilder;
    /**
     * Refer to {@link IOptions.offline}.
     */
    offline(offline: boolean): FbClientBuilder;
    /**
     * Refer to {@link IOptions.bootstrapProvider}.
     */
    bootstrapProvider(bootstrapProvider: IBootstrapProvider): FbClientBuilder;
    /**
     * Use the JsonBootstrapProvider.
     */
    useJsonBootstrapProvider(jsonStr: string): FbClientBuilder;
    /**
     * Refer to {@link IOptions.dataSynchronizer}.
     */
    dataSynchronizer(dataSynchronizer: IDataSynchronizer | ((clientContext: IClientContext, dataSourceUpdates: IDataSourceUpdates, initSuccessHandler: VoidFunction, errorHandler?: (e: Error) => void) => IDataSynchronizer)): FbClientBuilder;
}
//# sourceMappingURL=FbClientBuilder.d.ts.map
Thinking…

I now have everything I need. Let me build the example.

Design:

  • src/index.js — main example: connects to FeatBit Cloud eval server, evaluates a boolean flag + multivariate flag, listens for updates, tracks an event.
  • src/config.js — reads env vars, defaults to FeatBit Cloud URLs.
  • .env.example
  • scripts/check-connectivity.js — verifies reachability + auth behavior without needing a valid key (proves the wiring works).
  • README.md

Important detail: For the hosted cloud, the streaming URI would be wss://app-eval.featbit.co and events URI https://app-eval.featbit.co. Let me verify the WebSocket endpoint path the SDK uses so I can confirm wss://app-eval.featbit.co is right. Let me check the streaming implementation for the path.

Let me check data-sync/streaming for path.

Also I should verify: does the SDK support offline mode + JsonBootstrapProvider so the example runs and demonstrates behavior even without a key? Yes — offline(true) and useJsonBootstrapProvider(jsonStr). That's great: I can make the example demonstrably runnable in "demo mode" with a local bootstrap JSON, proving the code paths work, while real mode uses the cloud.

Let me check the streaming path and the bootstrap JSON format.

Let me confirm the WebSocket path and bootstrap JSON format so the example is accurate.

cd /sandbox/repo && grep -rn "streaming\|/streaming\|ws" node_modules/@featbit/node-server-sdk/dist/cjs/data-sync/streaming/*.js | grep -iE "path|url|uri|/" | head -10; echo "=== IOptions ==="; grep -A3 -E "streamingUri|pollingUri|eventsUri|offline|startWaitTime" node_modules/@featbit/node-server-sdk/dist/cjs/options/IOptions.d.ts | head -50
grep: node_modules/@featbit/node-server-sdk/dist/cjs/data-sync/streaming/*.js: No such file or directory
grep: node_modules/@featbit/node-server-sdk/dist/cjs/data-sync/streaming/*.js: No such file or directory
=== IOptions ===
    startWaitTime?: number;
    /**
     * The SDK key for your FeatBit environment.
     */
--
    streamingUri?: string;
    /**
     * The base URI of the polling service, mandatory if the {@link dataSyncMode} option is set to {@link DataSyncModeEnum.POLLING}.
     */
    pollingUri?: string;
    /**
     * The base URI of the event service
     */
    eventsUri?: string;
    /**
     * Whether this client is offline. If true, no calls to FeatBit will be made.
     *
     * Defaults to false
     */
    offline?: boolean;
    /**
     * The time between polling requests, in milliseconds. Ignored in data-sync mode.
     *

cd /sandbox/repo && sed -n '1,60p' node_modules/@featbit/node-server-sdk/dist/cjs/bootstrap/JsonBootstrapProvider.d.ts 2>/dev/null; echo "=== README bootstrap section ==="; grep -n -A30 -i "bootstrap" node_modules/@featbit/node-server-sdk/README.md | head -60
import { IBootstrapProvider } from "./IBootstrapProvider";
import { IBootstrapProvider } from "./IBootstrapProvider";
import { IDataSourceUpdates } from "../store/IDataSourceUpdates";
export declare class JsonBootstrapProvider implements IBootstrapProvider {
    private dataSet?;
    constructor(jsonStr: string);
    populate(dataSourceUpdates: IDataSourceUpdates, callback?: () => void): Promise<void>;
}
//# sourceMappingURL=JsonBootstrapProvider.d.ts.map=== README bootstrap section ===
248:curl -H "Authorization: <your-env-secret>" http://localhost:5100/api/public/sdk/server/latest-all > featbit-bootstrap.json
249-```
250-
251-Then use that file to initialize FbClient:
252-```javascript
253-import { FbClientBuilder } from "@featbit/node-server-sdk";
254-import fs from 'fs';
255-
256-let data: string = '';
257-try {
258-  data = fs.readFileSync('path_to_the_json_file', 'utf8');
259-} catch (err) {
260-  console.error(err);
261-}
262-
263-const fbClient = new FbClientBuilder()
264-    .offline(false)
265:    .useJsonBootstrapProvider(data)
266-    .build();
267-```
268-
269-### Disable Events Collection
270-
271-By default, the SDK automatically sends events (flag evaluation events and metric events for A/B testing) to the FeatBit server, unless the SDK is in offline mode.
272-
273-If you prefer to disable this event collection while the SDK is in online mode, you can configure this behavior using the disableEvents option.
274-
275-```javascript
276-import { FbClientBuilder } from "@featbit/node-server-sdk";
277-
278-const fbClient = new FbClientBuilder()
279-        .disableEvents(true)
280-        .build();
281-```
282-
283-### Experiments (A/B/n Testing)
284-
285-We support automatic experiments for pageviews and clicks, you just need to set your experiment on our SaaS platform,
286-then you should be able to see the result in near real time after the experiment is started.
287-
288-In case you need more control over the experiment data sent to our server, we offer a method to send custom event.
289-
290-```javascript
291-fbClient.track(user, eventName, numericValue);
292-```
293-
294-**numericValue** is not mandatory, the default value is **1.0**.
295-
Thinking…

I have everything. Let me now write the example.

Files:

  1. package.json (update)
  2. .env.example
  3. src/config.js
  4. src/index.js — main example (cloud mode + offline demo mode)
  5. scripts/check-connectivity.js — credential-free verification
  6. featbit-bootstrap.demo.json — bootstrap data for offline demo mode
  7. README.md

For the bootstrap JSON, I need the correct format: it's the output of /api/public/sdk/server/latest-all, which has shape { data: { featureFlags: [...], segments: [...] }, success: true }. Let me check what JsonBootstrapProvider expects — let me look at its implementation and the DataSet type.

Let me check.

cd /sandbox/repo && cat node_modules/@featbit/node-server-sdk/dist/cjs/bootstrap/JsonBootstrapProvider.js; echo "=== IFeatureFlag ==="; sed -n '1,70p' node_modules/@featbit/node-server-sdk/dist/cjs/store/datasource/IFeatureFlag.d.ts 2>/dev/null || find node_modules/@featbit/node-server-sdk/dist/cjs -name "*.d.ts" | xargs grep -ln "keyType\|disabledVariation" | head
"use strict";
"use strict";
var __importDefault = (this && this.__importDefault) || function (mod) {
    return (mod && mod.__esModule) ? mod : { "default": mod };
};
Object.defineProperty(exports, "__esModule", { value: true });
exports.JsonBootstrapProvider = void 0;
const serialization_1 = require("../store/serialization");
const DataKinds_1 = __importDefault(require("../store/DataKinds"));
const isNullOrUndefined_1 = require("../utils/isNullOrUndefined");
class JsonBootstrapProvider {
    constructor(jsonStr) {
        const json = JSON.parse(jsonStr);
        if (!json) {
            throw new Error("Invalid JSON");
        }
        const { featureFlags, segments } = json.data;
        const data = (0, serialization_1.deserializeAll)(featureFlags, segments);
        this.dataSet = {
            [DataKinds_1.default.Flags.namespace]: data.flags,
            [DataKinds_1.default.Segments.namespace]: data.segments,
        };
    }
    populate(dataSourceUpdates, callback) {
        return new Promise((resolve, reject) => {
            if ((0, isNullOrUndefined_1.isNullOrUndefined)(this.dataSet)) {
                return resolve();
            }
            const internalCallback = () => {
                resolve();
                callback === null || callback === void 0 ? void 0 : callback();
            };
            dataSourceUpdates.init(this.dataSet, internalCallback);
        });
    }
}
exports.JsonBootstrapProvider = JsonBootstrapProvider;
//# sourceMappingURL=JsonBootstrapProvider.js.map=== IFeatureFlag ===
node_modules/@featbit/node-server-sdk/dist/cjs/evaluation/data/IFlag.d.ts
node_modules/@featbit/node-server-sdk/dist/cjs/integrations/test_data/FlagBuilder.d.ts
Thinking…

Bootstrap JSON needs { data: { featureFlags: [...], segments: [...] } }. Let me check the serialization to know the flag shape. Let me look at serialization.js deserialize to understand field names.

Actually, there's a simpler path: the SDK has integrations/test_data with FlagBuilder — a TestData integration for local testing without a server! That's the cleanest way to make a runnable demo without credentials. Let me check it.

exports.integrations was in the exports list. Let me inspect.

The SDK ships a TestData integration — ideal for a credential-free runnable demo. Let me inspect it.

cd /sandbox/repo && ls node_modules/@featbit/node-server-sdk/dist/cjs/integrations/test_data/; echo "=== TestData.d.ts ==="; cat node_modules/@featbit/node-server-sdk/dist/cjs/integrations/test_data/TestData.d.ts 2>/dev/null | head -70
FlagBuilder.d.ts
FlagBuilder.d.ts
FlagBuilder.d.ts.map
FlagBuilder.js
FlagBuilder.js.map
TestData.d.ts
TestData.d.ts.map
TestData.js
TestData.js.map
TestDataSynchronizer.d.ts
TestDataSynchronizer.d.ts.map
TestDataSynchronizer.js
TestDataSynchronizer.js.map
index.d.ts
index.d.ts.map
index.js
index.js.map
=== TestData.d.ts ===
import { IFlag } from "../../evaluation/data/IFlag";
import TestDataSynchronizer from "./TestDataSynchronizer";
import { IClientContext } from "../../options/IClientContext";
import { IDataSourceUpdates } from "../../store/IDataSourceUpdates";
import { VoidFunction } from "../../utils/VoidFunction";
import { IStore } from "../../store/store";
export default class TestData {
    private currentFlags;
    private currentSegments;
    private dataSynchronizer;
    private store;
    /**
     * Get a factory for update processors that will be attached to this TestData instance.
     * @returns An update processor factory.
     */
    getFactory(): (clientContext: IClientContext, store: IStore, dataSourceUpdates: IDataSourceUpdates, initSuccessHandler: VoidFunction, _errorHandler?: ((e: Error) => void) | undefined) => TestDataSynchronizer;
    update(flag: IFlag): Promise<void>;
}
//# sourceMappingURL=TestData.d.ts.map
Thinking…

Let me check the FlagBuilder API and index.d.ts for the exported names.

cd /sandbox/repo && cat node_modules/@featbit/node-server-sdk/dist/cjs/integrations/test_data/index.d.ts; echo "=== FlagBuilder ==="; grep -E "^\s+(variation|booleanFlag|jsonFlag|numberFlag|stringFlag|on|off|fallthroughVariation|offVariation|ifMatch|thenReturn|build)\b.*\(" node_modules/@featbit/node-server-sdk/dist/cjs/integrations/test_data/FlagBuilder.d.ts | head -25; echo "=== integrations index ==="; cat node_modules/@featbit/node-server-sdk/dist/cjs/integrations/index.d.ts
import TestData from "./TestData";
import TestData from "./TestData";
import { FlagBuilder } from "./FlagBuilder";
import TestDataSynchronizer from "./TestDataSynchronizer";
export { TestData, FlagBuilder, TestDataSynchronizer };
//# sourceMappingURL=index.d.ts.map=== FlagBuilder ===
    build(): IFlag;
=== integrations index ===
export * from './test_data';
export { TestLogger } from './TestLogger';
//# sourceMappingURL=index.d.ts.map
Thinking…

Let me see the full FlagBuilder.d.ts to know its methods.

cd /sandbox/repo && cat node_modules/@featbit/node-server-sdk/dist/cjs/integrations/test_data/FlagBuilder.d.ts
import { IFlag } from "../../evaluation/data/IFlag";
import { IFlag } from "../../evaluation/data/IFlag";
import { IVariation } from "../../evaluation/data/IVariation";
import { ITargetUser } from "../../evaluation/data/ITargetUser";
import { ITargetRule } from "../../evaluation/data/IRule";
import { IFallthrough } from "../../evaluation/data/IFallthrough";
export declare class FlagBuilder {
    private _id;
    private _key?;
    private _version?;
    private _variationType;
    private _variations;
    private _targetUsers;
    private _rules;
    private _isEnabled;
    private _disabledVariationId;
    private _fallthrough?;
    private _exptIncludeAllTargets;
    id(id: string): FlagBuilder;
    key(key: string): FlagBuilder;
    version(version: number): FlagBuilder;
    variationType(variationType: string): FlagBuilder;
    variations(variations: IVariation[]): FlagBuilder;
    targetUsers(targetUsers: ITargetUser[]): FlagBuilder;
    rules(rules: ITargetRule[]): FlagBuilder;
    isEnabled(isEnabled: boolean): FlagBuilder;
    disabledVariationId(disabledVariationId: string): FlagBuilder;
    fallthrough(fallthrough: IFallthrough): FlagBuilder;
    exptIncludeAllTargets(exptIncludeAllTargets: boolean): FlagBuilder;
    build(): IFlag;
}
//# sourceMappingURL=FlagBuilder.d.ts.map
Thinking…

Now I can write the demo. Let me check IVariation, ITargetUser, IFallthrough shapes.

Let me look at those.

cd /sandbox/repo && for f in IVariation ITargetUser IFallthrough IFlag; do echo "--- $f"; cat node_modules/@featbit/node-server-sdk/dist/cjs/evaluation/data/$f.d.ts; done
--- IVariation
--- IVariation
export interface IVariation {
    id: string;
    value: string;
}
//# sourceMappingURL=IVariation.d.ts.map--- ITargetUser
export interface ITargetUser {
    keyIds: string[];
    variationId: string;
}
//# sourceMappingURL=ITargetUser.d.ts.map--- IFallthrough
import { IRolloutVariation } from "./IRolloutVariation";
export interface IFallthrough {
    dispatchKey: string;
    includedInExpt: boolean;
    variations: IRolloutVariation[];
}
//# sourceMappingURL=IFallthrough.d.ts.map--- IFlag
import { ITargetUser } from "./ITargetUser";
import { IVariation } from "./IVariation";
import { ITargetRule } from "./IRule";
import { IFallthrough } from "./IFallthrough";
export interface IFlag {
    id: string;
    variationType: string;
    fallthrough: IFallthrough;
    version: number;
    key: string;
    isEnabled: boolean;
    targetUsers: ITargetUser[];
    variations: IVariation[];
    disabledVariationId: string;
    rules: ITargetRule[];
    updatedAt: string;
    exptIncludeAllTargets: boolean;
}
//# sourceMappingURL=IFlag.d.ts.map
Thinking…

Now I have everything. Let me check IRolloutVariation too, then write the code.

IRolloutVariation: probably { id, rollout: number[] }.

Let me check quickly and then write.

cd /sandbox/repo && cat node_modules/@featbit/node-server-sdk/dist/cjs/evaluation/data/IRolloutVariation.d.ts; echo "=== UserBuilder ==="; grep -E "^\s+\w+\(" node_modules/@featbit/node-server-sdk/dist/cjs/UserBuilder.d.ts 2>/dev/null | head; ls node_modules/@featbit/node-server-sdk/dist/cjs/ | grep -i user
Failedexport interface IRolloutVariation {
export interface IRolloutVariation {
    id: string;
    rollout: [number, number];
    exptRollout: number;
}
//# sourceMappingURL=IRolloutVariation.d.ts.map=== UserBuilder ===


Command exited with code 1
Thinking…

UserBuilder isn't in the cjs root listing? The README used UserBuilder. Let me check exports again — earlier Object.keys(s) gave integrations, JsonBootstrapProvider, NullBootstrapProvider, createPutListener, ... truncated. Let me print full exports.

cd /sandbox/repo && node -e "const s=require('@featbit/node-server-sdk'); console.log(Object.keys(s).join('\n'));"
integrations
integrations
JsonBootstrapProvider
NullBootstrapProvider
createPutListener
createPatchListener
createStreamListeners
DispatchAlgorithm
isSegmentCondition
isMatchRule
OperatorTypes
Operator
ReasonKinds
DefaultEventProcessor
DefaultEventQueue
DefaultEventSender
DefaultEventSerializer
AsyncEvent
FlushEvent
ShutdownEvent
PayloadEvent
MetricEvent
EvalEvent
EventDispatcher
DeliveryStatus
NullEventProcessor
BasicLogger
UserBuilder
FactoryOrInstance
Type
TypeArray
NumberWithMinimum
StringMatchingRegex
Function
NullableBoolean
DateValidator
KindValidator
TypeValidators
deserializeAll
deserializePatch
DataSyncModeEnum
NullDataSynchronizer
StreamResponseEventType
generateConnectionToken
getTimestampFromDateTimeString
isNullOrUndefined
ValueConverters
defaultValues
EmptyString
MinInt
PollingError
StreamingError
UnexpectedResponseError
ClientError
isHttpRecoverable
FbClientBuilder
Thinking…

All good. UserBuilder and FbClientBuilder are exported. Now let me write the example.

Let me write:

  1. src/config.js — env-driven config with FeatBit Cloud defaults.
  2. src/index.js — the main example (cloud mode).
  3. src/demo-offline.js — runnable-without-credentials demo using TestData.
  4. scripts/check-connectivity.js — credential-free connectivity/auth verification.
  5. .env.example
  6. README.md

Let me write them.

For config:

  • FEATBIT_SDK_KEY (required for cloud)
  • FEATBIT_STREAMING_URI default wss://app-eval.featbit.co
  • FEATBIT_EVENTS_URI default https://app-eval.featbit.co

Let me confirm the streaming URI scheme: docs say "Streaming URL (wss://...)". The eval server host is app-eval.featbit.co. The SDK connects to ${streamingUri}/streaming?... probably. Let me verify by checking the streaming connection code for path. Let me grep.

Actually let me check the generateConnectionToken / streaming path to be safe.

cd /sandbox/repo && grep -rn "streaming\|/api/public" node_modules/@featbit/node-server-sdk/dist/cjs/data-sync/*.js 2>/dev/null | grep -oE '"/[a-zA-Z0-9/_-]*"|`\$\{[^`]*\}`' | sort -u | head -10; echo "=== files ==="; ls node_modules/@featbit/node-server-sdk/dist/cjs/data-sync/
=== files ===
=== files ===
DataSyncMode.d.ts
DataSyncMode.d.ts.map
DataSyncMode.js
DataSyncMode.js.map
HeaderWrapper.d.ts
HeaderWrapper.d.ts.map
HeaderWrapper.js
HeaderWrapper.js.map
IDataSynchronizer.d.ts
IDataSynchronizer.d.ts.map
IDataSynchronizer.js
IDataSynchronizer.js.map
IRequestor.d.ts
IRequestor.d.ts.map
IRequestor.js
IRequestor.js.map
NullDataSynchronizer.d.ts
NullDataSynchronizer.d.ts.map
NullDataSynchronizer.js
NullDataSynchronizer.js.map
PollingDataSynchronizer.d.ts
PollingDataSynchronizer.d.ts.map
PollingDataSynchronizer.js
PollingDataSynchronizer.js.map
Requestor.d.ts
Requestor.d.ts.map
Requestor.js
Requestor.js.map
WebSocketDataSynchronizer.d.ts
WebSocketDataSynchronizer.d.ts.map
WebSocketDataSynchronizer.js
WebSocketDataSynchronizer.js.map
index.d.ts
index.d.ts.map
index.js
index.js.map
types.d.ts
types.d.ts.map
types.js
types.js.map
utils.d.ts
utils.d.ts.map
utils.js
utils.js.map
Thinking…

Let me check Requestor.js and WebSocketDataSynchronizer.js for the URL paths used.

cd /sandbox/repo && grep -oE '(api/public[a-zA-Z0-9/_-]*|/streaming[a-zA-Z0-9/_-]*|latest-all)' node_modules/@featbit/node-server-sdk/dist/cjs/data-sync/Requestor.js node_modules/@featbit/node-server-sdk/dist/cjs/data-sync/WebSocketDataSynchronizer.js | sort -u; echo "=== ws url construction ==="; grep -nE "streamingUri|new WebSocket|token|url" node_modules/@featbit/node-server-sdk/dist/cjs/data-sync/WebSocketDataSynchronizer.js | head -12
=== ws url construction ===
=== ws url construction ===
11:        const { logger, streamingUri } = clientContext;
13:        this.streamingUri = streamingUri;
14:        this.socket = new NodeWebSocket_1.default(sdkKey, this.streamingUri, this.logger, getStoreTimestamp, webSocketPingInterval, webSocketHandshakeTimeout);
Thinking…

Let me check NodeWebSocket.js for the path.

cd /sandbox/repo && grep -rnE "api/public|/streaming|latest-all|\\$\{.*[Uu]ri.*\}" node_modules/@featbit/node-server-sdk/dist/cjs/data-sync/../ --include=NodeWebSocket.js -r 2>/dev/null | head; find node_modules/@featbit/node-server-sdk/dist/cjs -name "NodeWebSocket.js" -exec grep -nE "url|Uri|token|api" {} \; | head -15
13: constructor(sdkKey, streamingUri, logger, getStoreTimestamp, pingInterval, handshakeTimeout) {
13:    constructor(sdkKey, streamingUri, logger, getStoreTimestamp, pingInterval, handshakeTimeout) {
15:        this.streamingUri = streamingUri;
28:        const url = this.streamingUri.replace(/^http/, 'ws') + `?type=server&token=REDACTED utils_1.generateConnectionToken)(this.sdkKey)}`;
29:        this.ws = new ws_1.default(url, {
Thinking…

The streaming URL is streamingUri.replace(/^http/,'ws') + '?type=server&token=REDACTED'. So streamingUri can be given as https://app-eval.featbit.co and it becomes wss://app-eval.featbit.co?type=server&token=REDACTED. Or directly wss://app-eval.featbit.co.

So for the cloud: streamingUri = wss://app-eval.featbit.co, eventsUri = https://app-eval.featbit.co.

Now let me write the code.

Let me write all files now.

I have everything I need. Now let me build the example.

File edits

1 file

Completed
Writtensrc/config.jsView changes

/sandbox/repo/src/config.js

Written content · previous contents were not recorded

/**
 * FeatBit Cloud configuration.
 *
 * The hosted ("Online Infra") product exposes one Evaluation Server that serves
 * both real-time flag sync (WebSocket) and event ingestion (HTTP). For the
 * public cloud that host is `app-eval.featbit.co`, discovered from the
 * dashboard's own runtime config (window.env.evaluationUrl, hostingMode:"saas").
 *
 * Only FEATBIT_SDK_KEY is secret and required. Everything else has a working
 * default for the hosted cloud, and can be overridden for a self-hosted
 * deployment or a Relay Proxy without touching application code.
 */
 
const CLOUD_EVAL_HOST = 'https://app-eval.featbit.co';
 
function requiredEnv(name) {
  const value = process.env[name];
  if (!value) {
    throw new Error(
      `Missing ${name}.\n` +
        `  In the FeatBit dashboard: click the environment name (top of any page)\n` +
        `  -> "SDK config" -> copy the *server* secret, then:\n` +
        `     export ${name}=<server-secret>\n`
    );
  }
  return value;
}
 
/** Streaming URI. The SDK rewrites a leading `http` to `ws` itself. */
function streamingUri() {
  return process.env.FEATBIT_STREAMING_URI || CLOUD_EVAL_HOST.replace(/^http/, 'ws');
}
 
/** Event ingestion URI. */
function eventsUri() {
  return process.env.FEATBIT_EVENTS_URI || CLOUD_EVAL_HOST;
}
 
/** Polling URI, only used when dataSyncMode is POLLING. */
function pollingUri() {
  return process.env.FEATBIT_POLLING_URI || CLOUD_EVAL_HOST;
}
 
module.exports = {
  CLOUD_EVAL_HOST,
  requiredEnv,
  streamingUri,
  eventsUri,
  pollingUri,
  sdkKey: () => requiredEnv('FEATBIT_SDK_KEY'),
  hasSdkKey: () => Boolean(process.env.FEATBIT_SDK_KEY),
};

File edits

1 file

Completed
Writtensrc/index.jsView changes

/sandbox/repo/src/index.js

Written content · previous contents were not recorded

/**
 * FeatBit Cloud — minimal server-side example.
 *
 * Shows the four things you actually do with a feature-flag SDK:
 *   1. build a client pointed at your environment (one per process)
 *   2. wait for initialization (with a bounded wait + safe fallback)
 *   3. evaluate flags for a user, with reasons, and react to live changes
 *   4. track a metric event, then flush and close cleanly
 *
 * Run:  FEATBIT_SDK_KEY=<server-secret> node src/index.js
 */
 
const { FbClientBuilder, UserBuilder, DataSyncModeEnum } = require('@featbit/node-server-sdk');
const config = require('./config');
 
// Flag keys. Create these in the dashboard, or edit to match your own.
const FLAG_NEW_CHECKOUT = 'new-checkout'; // boolean
const FLAG_PRICING_TIER = 'pricing-tier'; // string / multi-variant
 
/** Build the application user that targeting rules are evaluated against. */
function buildUser() {
  return new UserBuilder('user-42') // stable, unique key -> also what FeatBit bills as 1 MAU
    .name('bob')
    .custom('country', 'US')
    .custom('plan', 'pro')
    .custom('beta', true)
    .build();
}
 
/**
 * Build the SDK client.
 *
 * `startWaitTime` bounds how long waitForInitialization() blocks. If the
 * service is unreachable the promise rejects rather than hanging, so a flag
 * outage degrades to your defaults instead of stalling a request.
 */
function buildClient() {
  return new FbClientBuilder()
    .sdkKey(config.sdkKey())
    .streamingUri(config.streamingUri())
    .eventsUri(config.eventsUri())
    .pollingUri(config.pollingUri())
    // STREAMING = real-time push over WebSocket (~100ms propagation).
    // Use DataSyncModeEnum.POLLING where outbound WebSockets are blocked.
    .dataSyncMode(DataSyncModeEnum.STREAMING)
    .startWaitTime(5) // seconds
    .build();
}
 
async function main() {
  const fbClient = buildClient();
  const user = buildUser();
 
  // Live updates: fires whenever a flag in this environment changes.
  fbClient.on('updated', () => {
    console.log('[featbit] flag data updated — re-evaluating');
    evaluate(fbClient, user).catch((err) => console.error('[featbit] re-evaluate failed:', err));
  });
 
  // Initialization. Never let this throw into your request path.
  try {
    await fbClient.waitForInitialization();
    console.log('[featbit] initialized:', fbClient.initialized());
  } catch (err) {
    console.error('[featbit] initialization failed — falling back to defaults:', err.message);
  }
 
  await evaluate(fbClient, user);
 
  // Metric event for experimentation/insights (value defaults to 1.0).
  fbClient.track(user, 'checkout-completed', 49.99);
 
  // Flush queued events before exiting, otherwise they are lost.
  await fbClient.flush();
  await fbClient.close();
}
 
async function evaluate(fbClient, user) {
  // Boolean flag — plain value.
  const useNewCheckout = await fbClient.boolVariation(FLAG_NEW_CHECKOUT, user, false);
  console.log(`${FLAG_NEW_CHECKOUT} = ${useNewCheckout}`);
 
  // Same flag, but with the *reason*: which rule/segment/target matched, or
  // whether you got the default. Indispensable when debugging targeting.
  const detail = await fbClient.boolVariationDetail(FLAG_NEW_CHECKOUT, user, false);
  console.log(`  value=${detail.value} kind=${detail.kind} reason=${detail.reason}`);
 
  // Multi-variant flag — pick a string variation.
  const tier = await fbClient.stringVariation(FLAG_PRICING_TIER, user, 'standard');
  console.log(`${FLAG_PRICING_TIER} = ${tier}`);
 
  // Branch on the result — this is the whole point of the SDK.
  if (useNewCheckout) {
    console.log(`-> serving new checkout experience (${tier} tier)`);
  } else {
    console.log(`-> serving classic checkout experience (${tier} tier)`);
  }
}
 
main().catch((err) => {
  console.error(err);
  process.exitCode = 1;
});
Thinking…

Now the offline demo using TestData, and the connectivity check script.

Let me verify the IFbClient API for initialized(), flush(), on('updated'), stringVariation. Let me check IFbClient.d.ts.

cd /sandbox/repo && grep -E "^\s+(\w+)\(|^\s+\w+\?:" node_modules/@featbit/node-server-sdk/dist/cjs/IFbClient.d.ts | head -40
on(event: string | symbol, listener: (...args: any[]) => void): this;
    on(event: string | symbol, listener: (...args: any[]) => void): this;
Thinking…

Let me read the IFbClient.d.ts fully to confirm methods.

cd /sandbox/repo && grep -nE "\b(initialized|flush|close|boolVariation|stringVariation|boolVariationDetail|track|waitForInitialization)\b" node_modules/@featbit/node-server-sdk/dist/cjs/IFbClient.d.ts | head -20; echo "=== events ==="; grep -nE "\"(ready|updated|failed|changed)\"|'ready'|'updated'" node_modules/@featbit/node-server-sdk/dist/cjs/*.d.ts node_modules/@featbit/node-server-sdk/dist/cjs/**/*.d.ts 2>/dev/null | head
15: * Alternately, you can detect this with [[waitForInitialization]].
15:     * Alternately, you can detect this with [[waitForInitialization]].
17:     * Alternately, you can detect this with [[waitForInitialization]].
=== events ===
node_modules/@featbit/node-server-sdk/dist/cjs/FbClientBuilder.d.ts:17: * event listener for the `"ready"` event using {@link IFbClient.on}.
node_modules/@featbit/node-server-sdk/dist/cjs/IFbClient.d.ts:14:     * - `"ready"`: Sent only once, when the client has successfully connected to FeatBit.
node_modules/@featbit/node-server-sdk/dist/cjs/IFbClient.d.ts:16:     * - `"failed"`: Sent only once, if the client has permanently failed to connect to FeatBit.
Thinking…

Let me read IFbClient.d.ts fully to see the method signatures and event names.

read /sandbox/repo/node_modules/@featbit/node-server-sdk/dist/cjs/IFbClient.d.ts{"content":[{"text":"/// <reference types=\"node\" />\nimport EventEmitter from \"events\";\nimport { IFbClientCore } from \"./IFbClientCore\";\nexport interfac…ctrl+o
{"content":[{"text":"/// <reference types=\"node\" />\nimport EventEmitter from \"events\";\nimport { IFbClientCore } from \"./IFbClientCore\";\nexport interface IFbClient extends IFbClientCore, EventEmitter {\n    /**\n     *\n     * Registers an event listener that will be called when the client triggers some type of event.\n     *\n     * This is the standard `on` method inherited from Node's `EventEmitter`; see the\n     * {@link https://nodejs.org/api/events.html#events_class_eventemitter|Node API docs} for more\n     * details on how to manage event listeners. Here is a description of the event types defined\n     * by `FbClient`.\n     *\n     * - `\"ready\"`: Sent only once, when the client has successfully connected to FeatBit.\n     * Alternately, you can detect this with [[waitForInitialization]].\n     * - `\"failed\"`: Sent only once, if the client has permanently failed to connect to FeatBit.\n     * Alternately, you can detect this with [[waitForInitialization]].\n     * - `\"error\"`: Contains an error object describing some abnormal condition that the client has detected\n     * (such as a network error).\n     * - `\"update\"`: The client has received a change to a feature flag. The event parameter is an object\n     * containing a single property, `key`, the flag key. Note that this does not necessarily mean the flag's\n     * value has changed for any particular context, only that some part of the flag configuration was changed.\n     * - `\"update:KEY\"`: The client has received a change to the feature flag whose key is KEY. This is the\n     * same as `\"update\"` but allows you to listen for a specific flag.\n     *\n     * @param event the name of the event to listen for\n     * @param listener the function to call when the event happens\n     */\n    on(event: string | symbol, listener: (...args: any[]) => void): this;\n}\n//# sourceMappingURL=IFbClient.d.ts.map","type":"text"}]}
Thinking…

The event is "update" (not "updated"), and "update:KEY". Let me fix my index.js. Also let me check IFbClientCore for method names.

The event name is "update", not "updated". Let me check the core interface and fix.

cd /sandbox/repo && grep -nE "^\s+[a-zA-Z]+(\?)?\(|^\s+[a-zA-Z]+:" node_modules/@featbit/node-server-sdk/dist/cjs/IFbClientCore.d.ts | head -40
18: initialized(): boolean;
18:    initialized(): boolean;
25:    waitForInitialization(): Promise<IFbClientCore>;
42:    boolVariation(key: string, user: IUser, defaultValue: boolean): Promise<boolean>;
60:    boolVariationDetail(key: string, user: IUser, defaultValue: boolean): Promise<IEvalDetail<boolean>>;
77:    numberVariation(key: string, user: IUser, defaultValue: number): Promise<number>;
95:    numberVariationDetail(key: string, user: IUser, defaultValue: number): Promise<IEvalDetail<number>>;
112:    stringVariation(key: string, user: IUser, defaultValue: string): Promise<string>;
130:    stringVariationDetail(key: string, user: IUser, defaultValue: string): Promise<IEvalDetail<string>>;
147:    jsonVariation(key: string, user: IUser, defaultValue: any): Promise<any>;
165:    jsonVariationDetail(key: string, user: IUser, defaultValue: any): Promise<IEvalDetail<any>>;
195:    getAllVariations(user: IUser): Promise<IEvalDetail<string>[]>;
201:    close(): Promise<void>;
212:    track(user: IUser, eventName: string, metricValue?: number | undefined): void;
221:    flush(callback?: (res: boolean) => void): Promise<boolean>;
Thinking…

All my method calls are correct. Just need to fix on('updated') → on('update'). Also initialized() exists, flush() returns Promise<boolean>, close() Promise<void>.

Let me fix the event name in index.js. Also improve: use update:KEY for a specific flag.

Let me edit.

File edits

1 file

Completed
Modifiedsrc/index.js+8−3View changes

/sandbox/repo/src/index.js

Replacement excerpt

-  // Live updates: fires whenever a flag in this environment changes.
-  fbClient.on('updated', () => {
-    console.log('[featbit] flag data updated — re-evaluating');
+  // Live updates. The SDK emits "update" for any flag in this environment and
+  // "update:KEY" for one specific flag. Note this means the flag *config*
+  // changed, not necessarily the value for this particular user.
+  fbClient.on('update', ({ key }) => {
+    console.log(`[featbit] flag '${key}' changed — re-evaluating`);
     evaluate(fbClient, user).catch((err) => console.error('[featbit] re-evaluate failed:', err));
   });
+
+  fbClient.on('failed', () => console.error('[featbit] permanently failed to connect'));
+  fbClient.on('error', (err) => console.error('[featbit] error:', err.message));
Thinking…

Now the offline demo using TestData (runnable without credentials), and the connectivity check.

Let me write the offline demo. TestData usage:

const { TestData, FlagBuilder } = require('@featbit/node-server-sdk').integrations;
const td = new TestData();
const flag = new FlagBuilder().key('x').variationType('boolean').variations([{id:'true',value:'true'},{id:'false',value:'false'}]).isEnabled(true).fallthrough({dispatchKey:'',includedInExpt:false,variations:[{id:'true',rollout:[0,1],exptRollout:1}]}).build();
await td.update(flag);
const client = new FbClientBuilder().sdkKey('dummy').dataSynchronizer(td.getFactory()).build();

Let me verify the export path for integrations and check TestData.js for how flags are stored (update(flag) uses flag.key?). Let me check TestData.js briefly.

Let me write it and test.

File edits

1 file

Completed
Writtensrc/demo-offline.jsView changes

/sandbox/repo/src/demo-offline.js

Written content · previous contents were not recorded

/**
 * FeatBit — runnable example with NO credentials and NO network.
 *
 * The SDK ships a TestData integration that feeds flags to the client from
 * memory instead of the evaluation server. That makes it possible to exercise
 * the exact same evaluation code paths (`boolVariation`, targeting, reasons,
 * live updates) that run against FeatBit Cloud.
 *
 * Use it to:
 *   - develop and run tests before you have an SDK key
 *   - verify this repo's wiring works end to end
 *
 * Run:  node src/demo-offline.js
 */
 
const {
  FbClientBuilder,
  UserBuilder,
  integrations: { TestData, FlagBuilder },
} = require('@featbit/node-server-sdk');
 
const FLAG_NEW_CHECKOUT = 'new-checkout';
const FLAG_PRICING_TIER = 'pricing-tier';
 
/** boolean flag, enabled, 100% rollout to the "true" variation. */
function booleanFlag(key, enabled) {
  return new FlagBuilder()
    .id(key)
    .key(key)
    .version(1)
    .variationType('boolean')
    .isEnabled(enabled)
    .variations([
      { id: 'true', value: 'true' },
      { id: 'false', value: 'false' },
    ])
    // specific users get a pinned variation, checked before the rollout
    .targetUsers([{ keyIds: ['user-99'], variationId: 'false' }])
    .fallthrough({
      dispatchKey: '',
      includedInExpt: false,
      variations: [{ id: 'true', rollout: [0, 1], exptRollout: 1 }],
    })
    .build();
}
 
/** multi-variant string flag with a 50/50 rollout. */
function stringFlag(key) {
  return new FlagBuilder()
    .id(key)
    .key(key)
    .version(1)
    .variationType('string')
    .isEnabled(true)
    .variations([
      { id: 'standard', value: 'standard' },
      { id: 'premium', value: 'premium' },
    ])
    .targetUsers([{ keyIds: ['user-42'], variationId: 'premium' }])
    .fallthrough({
      dispatchKey: '',
      includedInExpt: false,
      variations: [
        { id: 'standard', rollout: [0, 0.5], exptRollout: 0 },
        { id: 'premium', rollout: [0.5, 1], exptRollout: 1 },
      ],
    })
    .build();
}
 
async function main() {
  const td = new TestData();
  await td.update(booleanFlag(FLAG_NEW_CHECKOUT, true));
  await td.update(stringFlag(FLAG_PRICING_TIER));
 
  // Same builder as production; only the data source differs.
  const fbClient = new FbClientBuilder()
    .sdkKey('td-demo-key')
    .dataSynchronizer(td.getFactory())
    .build();
 
  await fbClient.waitForInitialization();
  console.log('[demo] initialized:', fbClient.initialized());
 
  const user = new UserBuilder('user-42').name('bob').custom('plan', 'pro').build();
 
  const detail = await fbClient.boolVariationDetail(FLAG_NEW_CHECKOUT, user, false);
  console.log(`${FLAG_NEW_CHECKOUT} -> value=${detail.value} kind=${detail.kind} reason=${detail.reason}`);
 
  const tier = await fbClient.stringVariation(FLAG_PRICING_TIER, user, 'standard');
  console.log(`${FLAG_PRICING_TIER} -> ${tier}  (targeted user, expects 'premium')`);
 
  // A different user: not targeted, so the 50/50 rollout decides.
  const other = new UserBuilder('user-7').name('alice').build();
  const otherTier = await fbClient.stringVariation(FLAG_PRICING_TIER, other, 'standard');
  console.log(`${FLAG_PRICING_TIER} -> ${otherTier}  (user-7 via rollout)`);
 
  // Unknown flag -> your default is returned, and the reason says so.
  const missing = await fbClient.boolVariationDetail('does-not-exist', user, false);
  console.log(`does-not-exist -> value=${missing.value} kind=${missing.kind} reason=${missing.reason}`);
 
  // Flip the flag at runtime: listeners fire, exactly like a dashboard change.
  fbClient.on('update', ({ key }) => console.log(`[demo] live update received for '${key}'`));
  console.log('[demo] disabling', FLAG_NEW_CHECKOUT, 'at runtime...');
  await td.update(booleanFlag(FLAG_NEW_CHECKOUT, false));
 
  // give the in-memory synchronizer a tick to deliver the change
  await new Promise((r) => setTimeout(r, 50));
  const after = await fbClient.boolVariation(FLAG_NEW_CHECKOUT, user, false);
  console.log(`${FLAG_NEW_CHECKOUT} after disable -> ${after}  (expects false)`);
 
  await fbClient.close();
  console.log('[demo] done');
}
 
main().catch((err) => {
  console.error(err);
  process.exitCode = 1;
});
Thinking…

Now the connectivity check script that works without credentials. Then test both.

Let me write scripts/check-connectivity.js:

  • probes the eval server's server-side and client-side endpoints
  • reports reachability + auth behavior
  • if FEATBIT_SDK_KEY is set, does a real fetch and shows flag count
  • exits 0 if reachable

Let me write it.

File edits

1 file

Completed
Writtenscripts/check-connectivity.jsView changes

/sandbox/repo/scripts/check-connectivity.js

Written content · previous contents were not recorded

#!/usr/bin/env node
/**
 * Credential-free connectivity check for FeatBit Cloud.
 *
 * Proves the wiring is correct *before* you have a working SDK key:
 *   - is the evaluation server reachable from this network?
 *   - does it reject a bad key with 401 (i.e. is auth behaving)?
 *   - with a real FEATBIT_SDK_KEY, does it actually return flags?
 *
 * Run:  node scripts/check-connectivity.js
 */
 
const config = require('../src/config');
 
const EVAL_HOST = process.env.FEATBIT_EVAL_HOST || config.CLOUD_EVAL_HOST;
const SERVER_ENDPOINT = `${EVAL_HOST}/api/public/sdk/server/latest-all`;
const CLIENT_ENDPOINT = `${EVAL_HOST}/api/public/sdk/client/latest-all`;
const TIMEOUT_MS = 10_000;
 
async function probe(label, url, init) {
  const started = Date.now();
  try {
    const res = await fetch(url, {
      ...init,
      signal: AbortSignal.timeout(TIMEOUT_MS),
    });
    const ms = Date.now() - started;
    const body = (await res.text()).slice(0, 200);
    return { label, ok: true, status: res.status, ms, body };
  } catch (err) {
    return { label, ok: false, status: null, ms: Date.now() - started, error: err.message };
  }
}
 
function report(r) {
  const head = `${r.ok ? 'HTTP ' + r.status : 'UNREACHABLE'}  ${r.ms}ms  ${r.label}`;
  console.log(head);
  if (!r.ok) console.log(`    error: ${r.error}`);
  else if (r.body) console.log(`    body: ${r.body.replace(/\s+/g, ' ')}`);
}
 
async function main() {
  console.log(`FeatBit evaluation host: ${EVAL_HOST}\n`);
 
  // 1. Server-side endpoint with a deliberately invalid key.
  //    401 == reachable and auth is working. Anything else is a network/DNS problem.
  const badKey = await probe('server latest-all (invalid key)', SERVER_ENDPOINT, {
    method: 'GET',
    headers: { Authorization: 'invalid-sdk-key-probe' },
  });
  report(badKey);
 
  // 2. Client-side endpoint, same idea.
  const badSecret = await probe('client latest-all (invalid secret)', CLIENT_ENDPOINT, {
    method: 'POST',
    headers: { 'Content-Type': 'application/json', Authorization: 'invalid-client-secret' },
    body: JSON.stringify({ keyId: 'probe', name: 'probe' }),
  });
  report(badSecret);
 
  console.log('');
  if (!badKey.ok) {
    console.log('FAIL: cannot reach the FeatBit evaluation server from this network.');
    console.log('      Check DNS/egress rules, or point FEATBIT_EVAL_HOST at your own deployment.');
    process.exit(1);
  }
 
  if (badKey.status !== 401) {
    console.log(`WARN: expected 401 for an invalid key, got ${badKey.status}.`);
    console.log('      The endpoint responded, so the host is right; the response is unexpected.');
  } else {
    console.log('OK: evaluation server reachable and rejecting invalid credentials with 401.');
  }
 
  // 3. If a real key is present, do a genuine fetch and summarise the payload.
  if (config.hasSdkKey()) {
    console.log('\nFEATBIT_SDK_KEY is set — fetching real flag data...');
    const real = await probe('server latest-all (your key)', SERVER_ENDPOINT, {
      method: 'GET',
      headers: { Authorization: config.sdkKey() },
    });
    report(real);
    if (real.ok && real.status === 200) {
      try {
        const full = await fetch(SERVER_ENDPOINT, {
          headers: { Authorization: config.sdkKey() },
          signal: AbortSignal.timeout(TIMEOUT_MS),
        }).then((r) => r.json());
        const flags = full?.data?.featureFlags ?? [];
        const segments = full?.data?.segments ?? [];
        console.log(`    flags: ${flags.length}, segments: ${segments.length}`);
        flags.slice(0, 20).forEach((f) => console.log(`      - ${f.key} (${f.variationType})`));
        console.log('\nOK: credentials work. Run: node src/index.js');
      } catch (err) {
        console.log(`    could not parse payload: ${err.message}`);
      }
    } else if (real.status === 401) {
      console.log('    FAIL: 401 with your key. Make sure it is the *server* secret for');
      console.log('          the environment you mean, not the client secret.');
      process.exit(1);
    }
  } else {
    console.log('\nFEATBIT_SDK_KEY is not set, so real flag data cannot be fetched.');
    console.log('  Dashboard -> environment name -> "SDK config" -> server secret.');
    console.log('  Then:  export FEATBIT_SDK_KEY=<server-secret> && node src/index.js');
    console.log('\nMeanwhile the no-credential demo still runs: node src/demo-offline.js');
  }
}
 
main();
Thinking…

Now let me update package.json and .env.example, then test.

File edits

1 file

Completed
Written.env.exampleView changes

/sandbox/repo/.env.example

Written content · previous contents were not recorded

# FeatBit Cloud connection settings.
# Copy to .env and fill in, or just export FEATBIT_SDK_KEY.
 
# REQUIRED. Dashboard -> environment name (top of any page) -> "SDK config"
# -> copy the *server* secret. Never commit this.
FEATBIT_SDK_KEY=
 
# Optional overrides. Defaults below are the hosted FeatBit Cloud
# ("Online Infra") endpoints and need no changes for the SaaS product.
FEATBIT_STREAMING_URI=wss://app-eval.featbit.co
FEATBIT_EVENTS_URI=https://app-eval.featbit.co
FEATBIT_POLLING_URI=https://app-eval.featbit.co
 
# Used only by scripts/check-connectivity.js
FEATBIT_EVAL_HOST=https://app-eval.featbit.co
 
cd /sandbox/repo && python3 - <<'EOF'
import json
p='package.json'
d=json.load(open(p))
d['name']='featbit-cloud-example'
d['version']='1.0.0'
d['description']='Minimal FeatBit Cloud example using the official Node.js server-side SDK'
d['main']='src/index.js'
d['scripts']={
  'start':'node src/index.js',
  'demo':'node src/demo-offline.js',
  'check':'node scripts/check-connectivity.js'
}
d['license']='MIT'
json.dump(d,open(p,'w'),indent=2)
print(open(p).read())
EOF
{
{
  "name": "featbit-cloud-example",
  "version": "1.0.0",
  "description": "Minimal FeatBit Cloud example using the official Node.js server-side SDK",
  "main": "src/index.js",
  "scripts": {
    "start": "node src/index.js",
    "demo": "node src/demo-offline.js",
    "check": "node scripts/check-connectivity.js"
  },
  "keywords": [],
  "author": "",
  "license": "MIT",
  "dependencies": {
    "@featbit/node-server-sdk": "^1.3.1"
  }
}
Thinking…

Now let me test the offline demo and the connectivity check.

Now let me test both scripts.

cd /sandbox/repo && echo "===== npm run demo ====="; timeout 60 node src/demo-offline.js 2>&1 | tail -25
===== npm run demo =====
===== npm run demo =====
TypeError: this.store.get is not a function
    at TestData.update (/sandbox/repo/node_modules/@featbit/node-server-sdk/dist/cjs/integrations/test_data/TestData.js:33:46)
    at main (/sandbox/repo/src/demo-offline.js:73:12)
    at Object.<anonymous> (/sandbox/repo/src/demo-offline.js:116:1)
    at Module._compile (node:internal/modules/cjs/loader:1781:14)
    at Object..js (node:internal/modules/cjs/loader:1913:10)
    at Module.load (node:internal/modules/cjs/loader:1505:32)
    at Function._load (node:internal/modules/cjs/loader:1309:12)
    at wrapModuleLoad (node:internal/modules/cjs/loader:254:19)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:171:5)
    at node:internal/main/run_main_module:36:49

cd /sandbox/repo && echo "===== npm run check ====="; timeout 90 node scripts/check-connectivity.js 2>&1 | tail -25
===== npm run check =====
===== npm run check =====
FeatBit evaluation host: https://app-eval.featbit.co

HTTP 401  500ms  server latest-all (invalid key)
HTTP 401  414ms  client latest-all (invalid secret)

OK: evaluation server reachable and rejecting invalid credentials with 401.

FEATBIT_SDK_KEY is not set, so real flag data cannot be fetched.
  Dashboard -> environment name -> "SDK config" -> server secret.
  Then:  export FEATBIT_SDK_KEY=<server-secret> && node src/index.js

Meanwhile the no-credential demo still runs: node src/demo-offline.js
Thinking…

The connectivity check works perfectly. The offline demo fails because TestData.update() before the client is built — this.store is undefined until the synchronizer is attached to a client. So I must build the client FIRST, then call td.update(). Let me look at TestData.js to confirm ordering.

Let me read TestData.js.

The connectivity check works. The demo needs the client built before td.update(). Let me check the ordering.

read /sandbox/repo/node_modules/@featbit/node-server-sdk/dist/cjs/integrations/test_data/TestData.js{"content":[{"text":"\"use strict\";\nvar __importDefault = (this && this.__importDefault) || function (mod) {\n return (mod && mod.__esModule) ? mod : { \"d…ctrl+o
{"content":[{"text":"\"use strict\";\nvar __importDefault = (this && this.__importDefault) || function (mod) {\n    return (mod && mod.__esModule) ? mod : { \"default\": mod };\n};\nObject.defineProperty(exports, \"__esModule\", { value: true });\nconst TestDataSynchronizer_1 = __importDefault(require(\"./TestDataSynchronizer\"));\nconst createStreamListeners_1 = require(\"../../data-sources/createStreamListeners\");\nconst DataKinds_1 = __importDefault(require(\"../../store/DataKinds\"));\nclass TestData {\n    constructor() {\n        this.currentFlags = [];\n        this.currentSegments = [];\n        this.store = {};\n    }\n    /**\n     * Get a factory for update processors that will be attached to this TestData instance.\n     * @returns An update processor factory.\n     */\n    getFactory() {\n        // Provides an arrow function to prevent needed to bind the method to\n        // maintain `this`.\n        return (clientContext, store, dataSourceUpdates, initSuccessHandler, _errorHandler) => {\n            this.store = store;\n            const listeners = (0, createStreamListeners_1.createStreamListeners)(dataSourceUpdates, clientContext.logger, {\n                put: initSuccessHandler,\n            });\n            this.dataSynchronizer = new TestDataSynchronizer_1.default(dataSourceUpdates, Object.values(this.currentFlags), Object.values(this.currentSegments), () => { }, listeners);\n            return this.dataSynchronizer;\n        };\n    }\n    update(flag) {\n        var _a;\n        const oldVersion = ((_a = this.store.get(DataKinds_1.default.Flags, flag.key)) === null || _a === void 0 ? void 0 : _a.version) || 0;\n        const newFlag = Object.assign(Object.assign({}, flag), { version: oldVersion + 1 });\n        return this.dataSynchronizer.upsert(DataKinds_1.default.Flags, newFlag);\n    }\n}\nexports.default = TestData;\n//# sourceMappingURL=TestData.js.map","type":"text"}]}
Thinking…

Confirmed: this.store is {} until getFactory() is invoked by the client build, and this.dataSynchronizer is also set then. So the order must be:

  1. new TestData()
  2. build client with .dataSynchronizer(td.getFactory())
  3. waitForInitialization()
  4. then td.update(flag)

Also note: currentFlags is never populated by update() — it only calls dataSynchronizer.upsert. So flags seeded before client build wouldn't be delivered anyway. So: build client first, then update each flag.

Let me fix demo-offline.js ordering.

Also, update() returns this.dataSynchronizer.upsert(...). Let me check TestDataSynchronizer.upsert works and delivers to store + listeners.

Let me restructure: build client, wait for init, then push flags via td.update(), then evaluate. But waitForInitialization might resolve immediately (initSuccessHandler called by TestDataSynchronizer start). Let me just reorder and test.

Let me rewrite the main() function.

Confirmed: store and dataSynchronizer only exist after the client is built. Let me fix the ordering.

File edits

1 file

Completed
Modifiedsrc/demo-offline.js+7−2View changes

/sandbox/repo/src/demo-offline.js

Replacement excerpt

 async function main() {
   const td = new TestData();
-  await td.update(booleanFlag(FLAG_NEW_CHECKOUT, true));
-  await td.update(stringFlag(FLAG_PRICING_TIER));
 
   // Same builder as production; only the data source differs.
+  // NOTE: the client must be built BEFORE td.update() — TestData only gets a
+  // store and synchronizer once getFactory() is invoked during build().
   const fbClient = new FbClientBuilder()
     .sdkKey('td-demo-key')
     .dataSynchronizer(td.getFactory())
     .build();
 
   await fbClient.waitForInitialization();
   console.log('[demo] initialized:', fbClient.initialized());
+
+  // Seed the in-memory flag data.
+  await td.update(booleanFlag(FLAG_NEW_CHECKOUT, true));
+  await td.update(stringFlag(FLAG_PRICING_TIER));
+  await new Promise((r) => setTimeout(r, 50));
Thinking…

Now let me run the demo again.

cd /sandbox/repo && timeout 60 node src/demo-offline.js 2>&1 | tail -25
error: [FeatBit] You have set custom uris without specifying the eventsUri URI; connections may not work properly
error: [FeatBit] You have set custom uris without specifying the eventsUri URI; connections may not work properly
error: [FeatBit] You have set custom uris without specifying the streamingUri URI; connections may not work properly
info: [FeatBit] FbClient started successfully.
[demo] initialized: true
new-checkout -> value=true kind=FallThrough reason=fall through targets and rules
pricing-tier -> premium  (targeted user, expects 'premium')
pricing-tier -> standard  (user-7 via rollout)
does-not-exist -> value=false kind=FlagNotFound reason=flag not found: does-not-exist
[demo] disabling new-checkout at runtime...
[demo] live update received for 'undefined'
new-checkout after disable -> false  (expects false)
[demo] done
Thinking…

The demo works. Two cosmetic issues:

  1. Two warnings about custom uris — because I set dataSynchronizer but no streamingUri/eventsUri. I can silence by disabling events and providing URIs, or just note them. Better: .disableEvents(true) and provide placeholder streamingUri/eventsUri? Actually the warning arises because options validation detects a custom dataSynchronizer without uris. Cleanest: set .offline(true)? That would use NullDataSynchronizer maybe overriding. Let me instead pass explicit dummy URIs + disableEvents(true) to keep output clean.

Hmm, but actually the check is: "You have set custom uris without specifying the eventsUri" — it thinks I set custom uris (because dataSynchronizer is custom) but didn't specify eventsUri. So specifying eventsUri and streamingUri explicitly should silence it. Let me add them.

  1. live update received for 'undefined' — the update event payload's key is undefined in the TestData path. Let me handle that gracefully: print key if present.

Let me fix both.

Note the evaluation results are all correct:

  • new-checkout true (fall through)
  • pricing-tier premium for targeted user-42 ✓
  • standard for user-7 via rollout ✓
  • FlagNotFound for missing flag with default ✓
  • live update → false ✓

Let me fix the cosmetic issues.

Works correctly. Let me clean up two cosmetic issues (spurious URI warnings, undefined key).

File edits

1 file

Completed
Modifiedsrc/demo-offline.js+8−1View changes

/sandbox/repo/src/demo-offline.js

Replacement excerpt

   const fbClient = new FbClientBuilder()
     .sdkKey('td-demo-key')
     .dataSynchronizer(td.getFactory())
+    // TestData replaces the data source, but the builder still wants the URIs
+    // to be explicit; events are pointless offline, so turn them off.
+    .streamingUri('ws://localhost:0')
+    .eventsUri('http://localhost:0')
+    .disableEvents(true)
     .build();

Replacement excerpt

-  fbClient.on('update', ({ key }) => console.log(`[demo] live update received for '${key}'`));
+  fbClient.on('update', (payload) =>
+    console.log(`[demo] live update received for '${payload?.key ?? '(all flags)'}'`)
+  );
Thinking…

Let me re-run the demo, and also test that src/index.js behaves gracefully without a key (should throw the helpful error) and with a bogus key (should fall back to defaults).

cd /sandbox/repo && echo "===== demo ====="; timeout 60 node src/demo-offline.js 2>&1 | tail -20
===== demo =====
===== demo =====
info: [FeatBit] FbClient started successfully.
[demo] initialized: true
new-checkout -> value=true kind=FallThrough reason=fall through targets and rules
pricing-tier -> premium  (targeted user, expects 'premium')
pricing-tier -> standard  (user-7 via rollout)
does-not-exist -> value=false kind=FlagNotFound reason=flag not found: does-not-exist
[demo] disabling new-checkout at runtime...
[demo] live update received for '(all flags)'
new-checkout after disable -> false  (expects false)
[demo] done

cd /sandbox/repo && echo "===== index.js with NO key ====="; timeout 40 node src/index.js 2>&1 | tail -8; echo; echo "===== index.js with BOGUS key ====="; FEATBIT_SDK_KEY=bogus-key-123 timeout 60 node src/index.js 2>&1 | tail -14
===== index.js with NO key =====
===== index.js with NO key =====
    at buildClient (/sandbox/repo/src/index.js:39:20)
    at main (/sandbox/repo/src/index.js:51:20)
    at Object.<anonymous> (/sandbox/repo/src/index.js:105:1)
    at Module._compile (node:internal/modules/cjs/loader:1781:14)
    at Object..js (node:internal/modules/cjs/loader:1913:10)
    at Module.load (node:internal/modules/cjs/loader:1505:32)
    at Function._load (node:internal/modules/cjs/loader:1309:12)
    at wrapModuleLoad (node:internal/modules/cjs/loader:254:19)

===== index.js with BOGUS key =====
info: [FeatBit] Stream connection attempt StartTime 1791252145009
warn: [FeatBit] FbClient failed to start successfully within 5 milliseconds. This error usually indicates a connection issue with FeatBit or an invalid sdkKey.Please double-check your sdkKey and streamingUri/pollingUri configuration. We will continue to initialize the FbClient, it still have a chance to get to work if it's a temporary network issue
[featbit] initialization failed — falling back to defaults: FbClient failed to start successfully within 5 milliseconds. This error usually indicates a connection issue with FeatBit or an invalid sdkKey.Please double-check your sdkKey and streamingUri/pollingUri configuration. We will continue to initialize the FbClient, it still have a chance to get to work if it's a temporary network issue
warn: [FeatBit] Variation called before FeatBit client initialization completed (did you wait for the'ready' event?) - using default value
new-checkout = false
warn: [FeatBit] Variation called before FeatBit client initialization completed (did you wait for the'ready' event?) - using default value
  value=false kind=ClientNotReady reason=client not ready
warn: [FeatBit] Variation called before FeatBit client initialization completed (did you wait for the'ready' event?) - using default value
pricing-tier = standard
-> serving classic checkout experience (standard tier)
info: [FeatBit] WebSocket connection succeeded, connection time: 428 ms
warn: [FeatBit] WebSocket closed
Thinking…

Very informative results:

  1. The demo works cleanly now.
  2. index.js with no key → throws my helpful error, but the stack trace is noisy. It's fine but let me make it a clean error message without stack. Let me catch the config error in main and print message only.
  3. index.js with bogus key → graceful degradation works: falls back to defaults (ClientNotReady), exactly the production-safe behavior.

Interesting: "WebSocket connection succeeded, connection time: 428 ms" — so the WebSocket endpoint at wss://app-eval.featbit.co accepts the connection and then closes it (auth rejected). Good: confirms streaming URI is correct.

Also note: "failed to start successfully within 5 milliseconds" — the message says milliseconds but startWaitTime(5) is documented in seconds. Let me check: IOptions startWaitTime docs. The message says "5 milliseconds" which suggests the unit is milliseconds! Let me check the docs for startWaitTime.

Let me check IOptions.d.ts for startWaitTime unit.

This matters — if startWaitTime is in milliseconds, 5 means 5ms which is way too short. Let me verify.

Important detail to verify — the SDK said "within 5 milliseconds". Let me check the startWaitTime unit.

cd /sandbox/repo && grep -B6 "startWaitTime?:" node_modules/@featbit/node-server-sdk/dist/cjs/options/IOptions.d.ts; echo "=== default + usage ==="; grep -rn "startWaitTime" node_modules/@featbit/node-server-sdk/dist/cjs/options/Options.js node_modules/@featbit/node-server-sdk/dist/cjs/FbClientCore.js 2>/dev/null | head; echo "=== README ==="; grep -n -B3 -A6 "startWaitTime" node_modules/@featbit/node-server-sdk/README.md | head -20
export interface IOptions {
export interface IOptions {
    /**
     * How long the client constructor will block awaiting a successful connection to FeatBit, in milliseconds.
     *
     * Defaults to 5000 milliseconds.
     */
    startWaitTime?: number;
=== default + usage ===
node_modules/@featbit/node-server-sdk/dist/cjs/FbClientCore.js:93:                const msg = `FbClient failed to start successfully within ${this.config.startWaitTime} milliseconds. ` +
node_modules/@featbit/node-server-sdk/dist/cjs/FbClientCore.js:104:        }, this.config.startWaitTime);
=== README ===
Thinking…

Confirmed: startWaitTime is in milliseconds, default 5000. My .startWaitTime(5) was a bug — it set a 5ms timeout, which is why initialization "failed" so fast. Let me fix it to 5000 and correct the comment.

Note: the README doesn't document it. Good catch — this is exactly the kind of subtle bug worth fixing and calling out.

Let me fix index.js: .startWaitTime(5000) with a comment noting milliseconds.

Also improve the no-key error to print cleanly without a stack trace.

Let me make both edits.

Found a real bug: startWaitTime is milliseconds (default 5000), so my 5 was a 5ms timeout. Let me fix it and clean up the error output.

File edits

1 file

Completed
Modifiedsrc/index.js+10−2View changes

/sandbox/repo/src/index.js

Replacement excerpt

     .dataSyncMode(DataSyncModeEnum.STREAMING)
-    .startWaitTime(5) // seconds
+    // MILLISECONDS, not seconds (default 5000). This bounds how long
+    // waitForInitialization() blocks before it rejects and you fall back to
+    // defaults. Do not set this to a raw "5" thinking it means 5 seconds.
+    .startWaitTime(Number(process.env.FEATBIT_START_WAIT_MS) || 5000)
     .build();

Replacement excerpt

 main().catch((err) => {
-  console.error(err);
+  // Config errors are expected and user-fixable: print the message, not a stack.
+  if (err.message && err.message.startsWith('Missing FEATBIT_')) {
+    console.error(err.message);
+  } else {
+    console.error(err);
+  }
   process.exitCode = 1;
 });
Thinking…

Let me re-test with bogus key to see the corrected behavior, and with no key.

cd /sandbox/repo && echo "===== NO key ====="; timeout 40 node src/index.js 2>&1 | tail -8; echo; echo "===== BOGUS key ====="; FEATBIT_SDK_KEY=bogus-key-123 timeout 60 node src/index.js 2>&1 | grep -vE "^info:" | tail -12
===== NO key =====
===== NO key =====
Missing FEATBIT_SDK_KEY.
  In the FeatBit dashboard: click the environment name (top of any page)
  -> "SDK config" -> copy the *server* secret, then:
     export FEATBIT_SDK_KEY=<server-secret>


===== BOGUS key =====
warn: [FeatBit] WebSocket closed
warn: [FeatBit] FbClient failed to start successfully within 5000 milliseconds. This error usually indicates a connection issue with FeatBit or an invalid sdkKey.Please double-check your sdkKey and streamingUri/pollingUri configuration. We will continue to initialize the FbClient, it still have a chance to get to work if it's a temporary network issue
[featbit] initialization failed — falling back to defaults: FbClient failed to start successfully within 5000 milliseconds. This error usually indicates a connection issue with FeatBit or an invalid sdkKey.Please double-check your sdkKey and streamingUri/pollingUri configuration. We will continue to initialize the FbClient, it still have a chance to get to work if it's a temporary network issue
warn: [FeatBit] Variation called before FeatBit client initialization completed (did you wait for the'ready' event?) - using default value
new-checkout = false
warn: [FeatBit] Variation called before FeatBit client initialization completed (did you wait for the'ready' event?) - using default value
  value=false kind=ClientNotReady reason=client not ready
warn: [FeatBit] Variation called before FeatBit client initialization completed (did you wait for the'ready' event?) - using default value
pricing-tier = standard
-> serving classic checkout experience (standard tier)
Thinking…

Both behaviors are correct and clean. Now let me write the README documenting everything: what it is, how to run, the blocker, and the pricing findings.

Let me also add a .gitignore entry for .env. Let me check the existing .gitignore.

Let me check .gitignore content.

Both paths behave correctly. Let me check .gitignore and write the README.

cd /sandbox/repo && cat .gitignore | head -20; echo "=== has .env? ==="; grep -nE "^\.env" .gitignore || echo "NO .env rule"
# Keep generated and vendored files out of source diffs.
# Keep generated and vendored files out of source diffs.

# Logs / OS cruft
*.log
.DS_Store

# JavaScript / TypeScript
node_modules/
.next/
dist/
build/
coverage/

# Python
.venv/
venv/
__pycache__/
*.py[cod]
.pytest_cache/
*.egg-info/
=== has .env? ===
NO .env rule
Thinking…

No .env rule. Let me add it since .env would hold the SDK secret.

Then write the README.

Let me do both.

cd /sandbox/repo && printf '\n# Secrets — FeatBit SDK keys live here\n.env\n.env.local\n' >> .gitignore && tail -5 .gitignore
.dart_tool/
.dart_tool/

# Secrets — FeatBit SDK keys live here
.env
.env.local
Thinking…

Now the README. Let me include:

  • What this is
  • Quickstart (two modes)
  • The credential blocker (plain)
  • Pricing findings
  • Manageability assessment for an agent
  • Verified facts with evidence

Let me write it.

File edits

1 file

Completed
WrittenREADME.mdView changes

/sandbox/repo/README.md

Written content · previous contents were not recorded

# FeatBit Cloud — minimal example
 
A small, working example of [FeatBit](https://www.featbit.co/) feature flags using the
official **Node.js server-side SDK** (`@featbit/node-server-sdk`) against the **hosted**
product ("Online Infra"). No Docker, no local service stack.
 
## Status: code complete, blocked on credentials
 
Everything here is written and verified **except** a live flag evaluation against
FeatBit Cloud, which needs an SDK key that cannot be obtained without an account.
See [Blocked](#blocked-why) below.
 
What is verified right now, with no credentials:
 
| Check | Result |
| --- | --- |
| SDK installs from npm | ✅ `@featbit/node-server-sdk@1.3.1` |
| Evaluation server reachable | ✅ `app-eval.featbit.co` responds in ~400–500ms |
| Auth behaves | ✅ invalid key → `401` on both server and client endpoints |
| WebSocket streaming endpoint | ✅ `wss://app-eval.featbit.co` completes the handshake, then closes on bad credentials |
| Flag evaluation logic | ✅ targeting, rollout, reasons, live updates — all exercised offline |
| Safe degradation | ✅ bad/missing key → defaults returned, no hang, no crash |
 
## Run it
 
```bash
npm install
 
# 1. No credentials, no network — proves the wiring and evaluation logic
npm run demo
 
# 2. No credentials — proves FeatBit Cloud is reachable and your config is right
npm run check
 
# 3. Real flags (needs an SDK key)
export FEATBIT_SDK_KEY=<server-secret>
npm start
```
 
### What each file does
 
| File | Purpose |
| --- | --- |
| `src/index.js` | The real example: connect to Cloud, evaluate a boolean + a multi-variant flag, print evaluation *reasons*, react to live flag changes, track a metric event, flush and close. |
| `src/demo-offline.js` | Same evaluation code paths fed by the SDK's built-in `TestData` integration. Runs with **no key and no network**. |
| `src/config.js` | Env-driven config. Hosted-cloud endpoints are the defaults; override to point at self-hosted or a Relay Proxy. |
| `scripts/check-connectivity.js` | Credential-free diagnostic. Reports reachability, auth behaviour, and — if a key is set — your actual flags and segments. |
| `.env.example` | Copy to `.env`. Only `FEATBIT_SDK_KEY` is required. |
 
### Getting the SDK key
 
In the dashboard: click the **environment name** at the top of any page → **SDK config** →
copy the **server** secret (not the client secret). Streaming and Event URLs are on the
same dialog.
 
## Blocked: why
 
The hosted product is real and its API is reachable, but **an agent cannot provision an
account**, so it cannot obtain an SDK key.
 
Evidence gathered:
 
- `app.featbit.co` serves the SaaS dashboard. Its own runtime config reports
  `hostingMode: "saas"`, `apiUrl: https://app-api.featbit.co`,
  `evaluationUrl: https://app-eval.featbit.co`, version `5.4.10`.
- The dashboard's auth API exposes **only** `login-by-email`, `reset-password`,
  `refresh-token`, and `logout`. Probing `signup`, `register`, `sign-up` under
  `/api/v1/identity` and `/api/v1/user` all return **404**. Its SPA routes are only
  `login`, `onboarding`, `select-workspace` — there is no signup route.
- `POST /api/v1/identity/login-by-email` returns **200** with
  `{"success":false,"errors":["EmailPasswordMismatch"]}` — login works, but you must
  already have an account.
- A second dashboard, `dashboard.featbit.co`, does offer self-serve sign-up
  ("Don't have an account? Sign up"), plus GitHub OAuth and magic-link login. Its auth
  UI is **Supabase**. Every one of those paths needs something an agent does not have:
  an email inbox to confirm with, or GitHub OAuth credentials.
 
**Unblock:** create an account at `app.featbit.co` (or `dashboard.featbit.co`), make a
project + environment, create the two flags below, then export the server secret. The
code needs no changes.
 
Flags `src/index.js` expects (edit freely):
 
| Key | Type | Notes |
| --- | --- | --- |
| `new-checkout` | boolean | variations `true` / `false` |
| `pricing-tier` | string | e.g. `standard` / `premium` |
 
## Pricing
 
Pulled from `featbit.co/pricing`, including the client-side "Online Infra" tab data that
is not in the server-rendered HTML. Prices are USD, as published.
 
### Online Infra (hosted — what this example uses)
 
Metered on **MAU**, where one MAU = one unique *user key*; the same key across multiple
projects, environments or devices counts once.
 
| Plan | Base price | MAU included | Notable contents |
| --- | --- | --- | --- |
| Free | $0 | 1,000 (hard cap) | Core flags, targeting/segmentation, unlimited projects & environments, webhooks, audit logs, community support |
| Pro | $49 /mo | 10,000 | everything in Free, plus IAM/RBAC (basic), priority support |
| Growth | $149 /mo | 40,000 | everything in Pro, plus flag change approval, scheduling, flag comparison |
| Enterprise | $449 /mo or **$4,490 /yr** | 80,000 | everything in Growth, plus SSO, global users & shareable segments, auto agents, reply SLA, Teams/Slack Connect |
 
Add-ons and rules:
 
- **Overage: +$20/mo per extra 10K MAU** above your plan's included MAU. Slider caps at 300K MAU; above that, contact sales.
- **Advanced RBAC: +$60/mo** (available on Growth and Enterprise).
- Enterprise **yearly billing saves ~16%** vs monthly ($4,490 vs $5,388).
- Published formula: `base + (extraMAU / 10,000) × $20 + ($60 if Advanced RBAC)`, ×12 for annual.
- Temporary overage does **not** cut you off — the system keeps working and they may ask you to upgrade for sustained overage.
- No seat limits; the meter is users, not developers.
 
### Self-Host (the alternative)
 
| Plan | Price | Notes |
| --- | --- | --- |
| Foundation | $0 | full open-source platform, forever free; no limits on seats/MAU/projects |
| Enterprise | $3,999 /yr | SSO, audit logs, workflow controls, Terraform/GitOps, priority support |
| + Advanced RBAC | +$600 /yr | add-on to self-host Enterprise |
| Enterprise Premium | Custom | dedicated engineering support, 4-hour SLA, custom terms |
 
Self-host plans have **no usage limits at all** — tiers differ only by feature and support.
 
### The practical read
 
Self-hosting Foundation is $0 and unlimited; hosted Free is $0 but capped at **1,000 MAU**,
which is a evaluation-size ceiling. So the real trade is operational cost (you run Kafka,
Mongo, Redis, the portal) versus a metered bill. At $49/mo for 10K MAU the hosted tiers are
cheap next to running the stack yourself — the pitch on their homepage is literally
"cut feature flag costs by up to 20×", aimed at teams leaving per-MAU-priced incumbents.
One caution: self-host Standard/Professional needs Docker Compose or Kubernetes, which is
real infrastructure to own.
 
## Will this be easy for an agent to manage?
 
Honest answer: **the runtime is easy, the provisioning is not.**
 
Good:
 
- **Server-side SDK evaluates locally.** After the initial fetch, flags are in memory and
  evaluated in-process — no network call per evaluation, so no latency or per-call cost in
  your hot path.
- **Degradation is genuinely safe.** Verified above: with an unreachable server or a bad
  key, `waitForInitialization()` rejects within `startWaitTime` and every variation returns
  *your* default with reason `ClientNotReady`. No hang, no crash. A flag-system outage
  cannot take your app down.
- **Diagnostics are excellent.** `boolVariationDetail` returns a `kind` and a human-readable
  `reason` (`FallThrough`, `FlagNotFound`, `ClientNotReady`, …). This is exactly what you
  want when an agent has to explain *why* a user got a value.
- **A no-credential test path exists.** The bundled `TestData` integration means flag logic
  is fully testable in CI with zero infrastructure — a big deal for automated workflows.
- **Clean lifecycle.** `flush()` then `close()`; a single client per process.
- **Config is portable.** Same code targets Cloud, self-hosted, or a Relay Proxy by changing
  two URIs.
 
Hard:
 
- **Provisioning is human-gated.** No self-serve signup API on the main cloud; account
  creation needs email confirmation or GitHub OAuth. An agent cannot create an org,
  project, environment, or flag, and therefore cannot obtain an SDK key. Every automated
  workflow starts with a human handing over a secret.
- **Two dashboards, some drift.** `app.featbit.co` (Angular, v5.4.10) and
  `dashboard.featbit.co` (Next.js + Supabase) both exist, with different auth models.
  Also `featbit.io` no longer resolves and `cloud.featbit.co` / `api.featbit.co` return
  Vercel `DEPLOYMENT_NOT_FOUND`. Docs still reference the cloud, so this is mid-migration —
  worth re-checking endpoints before you build anything serious on them.
- **The docs default to self-hosting.** The primary quickstart is Docker Compose
  (`git clone` + `docker compose up`, portal on `localhost:8081`, default login
  `test@featbit.com` / `123456`). Deliberately avoided here.
- **SDK doc gaps.** `startWaitTime` is in **milliseconds** but is undocumented in the SDK
  README; the natural guess of "5 for five seconds" silently produces a 5ms timeout and an
  immediate fallback to defaults. Caught and fixed in `src/index.js`. `TestData` also
  requires the client to be built *before* the first `update()` — otherwise
  `this.store.get is not a function`.
- **MAU billing is easy to trip.** Because one MAU = one user *key*, unstable keys
  (per-session or per-device IDs) inflate MAU silently and push you up a tier.
 
Net: once a human supplies an SDK key, this is straightforward and safe to operate, and
the local-evaluation design plus `TestData` make it unusually agent-friendly at runtime.
The control plane is the weak point — flag CRUD is dashboard- and human-gated, so
end-to-end automation (create flag → deploy → verify) is not achievable today.
 
## Notes
 
- Server-side SDK: local evaluation, multi-user. Client-side SDK: server evaluates,
  single-user. This example uses server-side.
- `STREAMING` (WebSocket, ~100ms propagation) is the default sync mode. Switch to
  `DataSyncModeEnum.POLLING` if outbound WebSockets are blocked.
- `.env` is gitignored. Never commit an SDK key.
Thinking…

Let me do a final verification: run all three scripts, check the repo structure, and confirm the README claims are accurate.

Let me run a final check.

Let me do a final end-to-end verification.

cd /sandbox/repo && echo "===== FILES ====="; git status --short; echo; echo "===== npm run demo ====="; timeout 60 npm run demo --silent 2>&1 | grep -v "^info:" | tail -12
===== FILES =====
===== FILES =====
 M .gitignore
?? .env.example
?? README.md
?? package-lock.json
?? package.json
?? scripts/
?? src/

===== npm run demo =====
[demo] initialized: true
new-checkout -> value=true kind=FallThrough reason=fall through targets and rules
pricing-tier -> premium  (targeted user, expects 'premium')
pricing-tier -> standard  (user-7 via rollout)
does-not-exist -> value=false kind=FlagNotFound reason=flag not found: does-not-exist
[demo] disabling new-checkout at runtime...
[demo] live update received for '(all flags)'
new-checkout after disable -> false  (expects false)
[demo] done

cd /sandbox/repo && echo "===== npm run check ====="; timeout 90 npm run check --silent 2>&1 | tail -14; echo; echo "exit=$?"
===== npm run check =====
===== npm run check =====
FeatBit evaluation host: https://app-eval.featbit.co

HTTP 401  458ms  server latest-all (invalid key)
HTTP 401  409ms  client latest-all (invalid secret)

OK: evaluation server reachable and rejecting invalid credentials with 401.

FEATBIT_SDK_KEY is not set, so real flag data cannot be fetched.
  Dashboard -> environment name -> "SDK config" -> server secret.
  Then:  export FEATBIT_SDK_KEY=<server-secret> && node src/index.js

Meanwhile the no-credential demo still runs: node src/demo-offline.js

exit=0
Thinking…

Everything works. Let me commit? The user didn't ask to commit. Let me leave it but maybe commit is nice. I'll not commit unless asked — actually it's a repo with git. Let me just leave the files; I'll mention it.

Actually, let me do a quick sanity check that the README's pricing claim about "Free 1,000 hard cap" is right — e1 free mauMax:1e3, mauIncluded:1e3. Yes.

One more: I stated Pro "10,000 MAU included" from e1 (mauIncluded 1e4). But the other array f said Pro mau "15,000". I used e1 since e7() renders e1. Let me double check that e7 (which maps e1) is what's rendered for the Online tab. Earlier: function e7(){return(0,t.jsxs)("div",{children:[(0,t.jsx)("div",{className:"grid grid-cols-1 md:grid-cols-2 lg:grid-grid-cols-4 gap-5",children:e1.map(...). And f was used by function p(e){let{tier:r}=e...}. Which one is used by the Online tab component? Let me verify quickly to avoid reporting wrong pricing.

Let me check which function renders in the Online Infra tab.

Let me verify which pricing array actually renders, since the bundle contained two variants.

cd /tmp && python3 - <<'EOF'
import re
t=open('nxt/e782eed8dd097ebf.js',encoding='utf-8',errors='replace').read()
# which function renders which array, and what the Online tab calls
for name in ['e7','e6','e8']:
    m=re.search(r'function '+name+r'\(\)\{',t)
    if m: print(name, '->', re.sub(r'\s+',' ',t[m.start():m.start()+180])); print()
# find references to e7( and f.map
for pat in [r'e7\(', r'\bf\.map', r'e1\.map', r'f\.map\(']:
    print(pat, [m.start() for m in re.finditer(pat,t)][:6])
print()
i=t.find('Online Infra')
print('CONTEXT around Online Infra button:')
print(re.sub(r'\s+',' ',t[i-400:i+1200]))
EOF
e7 -> function e7(){return(0,t.jsxs)("div",{children:[(0,t.jsx)("div",{className:"grid grid-cols-1 md:grid-cols-2 lg:grid-cols-4 gap-5",children:e1.map(e=>(0,t.
e7 -> function e7(){return(0,t.jsxs)("div",{children:[(0,t.jsx)("div",{className:"grid grid-cols-1 md:grid-cols-2 lg:grid-cols-4 gap-5",children:e1.map(e=>(0,t.jsx)(e4,{plan:e},e.key))})

e8 -> function e8(){return(0,t.jsxs)("div",{className:"max-w-5xl mx-auto",children:[(0,t.jsx)("div",{className:"grid grid-cols-1 md:grid-cols-3 gap-6 mb-10",children:e2.map(e=>(0,t.jsx)(

e7\( [30999]
\bf\.map [2931]
e1\.map [31129]
f\.map\( [2931]

CONTEXT around Online Infra button:
 mx-auto"})}):(0,t.jsx)("td",{className:"".concat(o," text-xs text-[#c7d4c7]"),children:r})}function tr(){return(0,t.jsxs)("div",{className:"mt-14",children:[(0,t.jsxs)("div",{className:"pixel-card p-6 mb-4",children:[(0,t.jsx)("p",{className:"pixel-section-label",children:"Compare All Plans"}),(0,t.jsx)("p",{className:"mt-2 text-sm text-[#c7d4c7]",children:"Foundation covers all standard plans — Online Infra (Free to Scale) and Self-Host Foundation share the same feature set. Enterprise plans unlock SSO, RBAC, audit logs, and workflow controls."})]}),(0,t.jsx)("div",{className:"overflow-x-auto pixel-card",children:(0,t.jsxs)("table",{className:"w-full text-sm min-w-[640px]",children:[(0,t.jsxs)("thead",{children:[(0,t.jsxs)("tr",{className:"border-b border-[#2b4333]/40",children:[(0,t.jsx)("th",{className:"px-4 py-3 text-left",style:{width:"35%"}}),(0,t.jsx)("th",{className:"px-3 py-3 text-center text-xs font-bold uppercase tracking-widest text-[#7ef0a7]/80 border-r border-[#2b4333]",children:"Foundation"}),(0,t.jsx)("th",{colSpan:2,className:"px-3 py-3 text-center text-xs font-bold uppercase tracking-widest text-[#c7d4c7]/60",children:"Enterprise"})]}),(0,t.jsxs)("tr",{className:"border-b-2 border-[#2b4333]",children:[(0,t.jsx)("th",{className:"px-4 py-4 text-left text-[#8fb3a1] font-medium",children:"Feature"}),(0,t.jsxs)("th",{className:"px-3 py-4 text-center font-bold text-xs border-r border-[#2b4333]",children:[(0,t.jsx)("div",{className:"text-[#7ef0a7]",children:"Foundation"}),(0,t.jsx)("div",{className:"text-[#8fb3a1] font-normal mt-0.5 text-[10px]",children:"Online
Thinking…

Let me determine which of e7/e8 is rendered for the "Online Infra" tab. Let me find the tab-switching component and see which is used for online vs self-host.

e8 maps e2 = the self-host plans (Foundation, Enterprise, Enterprise Premium). So e8 = Self-Host tab. e7 maps e1 = the online plans (free, pro, growth, enterprise). So e7 = Online Infra tab.

f (at index 2931, f.map) is used by function p — an older/alternate 3-card layout (Free $0/1,000, Pro $49/15,000, Growth $149/80,000). Let me check if p/f is still referenced anywhere (dead code?). Let me check references to p( and whether it's in the render tree.

Let me find where the tab component chooses between e7 and e8, and whether f/p is used.

cd /tmp && python3 - <<'EOF'
import re
t=open('nxt/e782eed8dd097ebf.js',encoding='utf-8',errors='replace').read()
# locate tab state and which component each tab renders
for m in re.finditer(r'(e7|e8)\b(?!\()',t):
    s=max(0,m.start()-260); seg=re.sub(r'\s+',' ',t[s:m.start()+120])
    if 'jsx' in seg or 'tab' in seg.lower() or 'online' in seg.lower():
        print(m.group(1),'|',seg); print('---')
EOF
e7 | ,"Online Infra"]})]}),(0,t.jsx)("p",{className:"text-sm text-[#8fb3a1]",children:"online"===l?"Managed hosting — we handle infrastructure, you focus on shi
e7 | ,"Online Infra"]})]}),(0,t.jsx)("p",{className:"text-sm text-[#8fb3a1]",children:"online"===l?"Managed hosting — we handle infrastructure, you focus on shipping.":"Deploy on your own infrastructure — full data privacy & control."})]}),"online"===l?i?(0,t.jsx)(e7,{}):(0,t.jsx)(m,{}):(0,t.jsx)(e8,{}),"online"===l?i?(0,t.jsx)(nf,{}):(0,t.jsx)(tr,{}):(0,t.jsx)(nx,{})]}),(0,t.jsx)(s
---
e8 | p",{className:"text-sm text-[#8fb3a1]",children:"online"===l?"Managed hosting — we handle infrastructure, you focus on shipping.":"Deploy on your own infrastructure — full data privacy & control."})]}),"online"===l?i?(0,t.jsx)(e7,{}):(0,t.jsx)(m,{}):(0,t.jsx)(e8,{}),"online"===l?i?(0,t.jsx)(nf,{}):(0,t.jsx)(tr,{}):(0,t.jsx)(nx,{})]}),(0,t.jsx)(s.default,{})]})}}]);
---
Thinking…

So the tab logic: "online"===l ? (i ? e7 : m) : e8. There's a feature flag i (ironically!) that decides between e7 (the 4-plan MAU-slider version) and m (some other component). Let me check what i is and what m renders. If i is false, m renders — which may use the f array (Free/Pro/Growth with 15,000 and 80,000 MAU).

This is important: the actual displayed pricing depends on a flag. Let me find i and m.

Let me look at the surrounding code for the definition of i and m.

Interesting — the Online tab renders e7 or m based on a variable i. Let me resolve which.

cd /tmp && python3 - <<'EOF'
import re
t=open('nxt/e782eed8dd097ebf.js',encoding='utf-8',errors='replace').read()
i=t.find('"online"===l?i?(0,t.jsx)(e7,{})')
seg=t[max(0,i-2600):i+200]
print(re.sub(r'\s+',' ',seg))
EOF
g,{className:"w-3.5 h-3.5 text-[#7ef0a7] shrink-0"}),(0,t.jsxs)("span",{className:"text-sm text-[#c7d4c7]",children:[r,n&&(0,t.jsx)("span",{className:"ml-2 text
g,{className:"w-3.5 h-3.5 text-[#7ef0a7] shrink-0"}),(0,t.jsxs)("span",{className:"text-sm text-[#c7d4c7]",children:[r,n&&(0,t.jsx)("span",{className:"ml-2 text-[10px] text-[#8fb3a1] border border-[#2b4333] px-1.5 py-0.5 rounded",children:n})]})]}),(0,t.jsx)("span",{className:"text-xs font-medium text-[#8fb3a1] shrink-0 ml-6",children:a})]},r)})}),(0,t.jsx)("div",{className:"mt-5",children:(0,t.jsx)(c.ContactModal,{trigger:(0,t.jsx)(i.Button,{className:"pixel-button pixel-button-secondary text-sm",children:"Contact Us →"})})})]}),(0,t.jsxs)("div",{className:"pixel-card p-6 flex flex-col sm:flex-row sm:items-center sm:justify-between gap-4",children:[(0,t.jsxs)("div",{children:[(0,t.jsx)("p",{className:"text-sm font-medium text-white",children:"Have other requirements? We'd love to help."}),(0,t.jsx)("p",{className:"mt-1 text-xs text-[#8fb3a1]",children:"Custom deployment, compliance needs, extended SLAs — just reach out."})]}),(0,t.jsx)(c.ContactModal,{trigger:(0,t.jsx)(i.Button,{className:"pixel-button pixel-button-secondary text-sm shrink-0",children:"Contact Us →"})})]})]})})}function ng(e){let{useNewPricingFlag:i}=e,[l,c]=(0,r.useState)("selfhost");return(0,t.jsxs)("div",{className:"pixel-home min-h-screen flex flex-col overflow-hidden",children:[(0,t.jsx)(o.default,{}),(0,t.jsxs)("main",{className:"flex-1 container py-8 md:py-10",children:[(0,t.jsxs)("div",{className:"mb-8 flex flex-col items-center gap-5 text-center",children:[(0,t.jsxs)("div",{className:"flex items-center gap-3",children:[(0,t.jsx)("span",{className:"pixel-dot"}),(0,t.jsx)("p",{className:"pixel-kicker",children:"FeatBit // Pricing"}),(0,t.jsx)("span",{className:"pixel-dot"})]}),(0,t.jsxs)("div",{className:"inline-flex items-center pixel-card p-1 gap-1",children:[(0,t.jsxs)("button",{onClick:()=>c("selfhost"),className:"flex items-center gap-2 px-5 py-2.5 text-sm font-bold uppercase tracking-[0.1em] transition-all ".concat("selfhost"===l?"bg-[#7ef0a7] text-black":"text-[#8fb3a1] hover:text-[#c7d4c7]"),children:[(0,t.jsx)(a.Server,{className:"w-4 h-4"}),"Self-Host"]}),(0,t.jsxs)("button",{onClick:()=>c("online"),className:"flex items-center gap-2 px-5 py-2.5 text-sm font-bold uppercase tracking-[0.1em] transition-all ".concat("online"===l?"bg-[#7ef0a7] text-black":"text-[#8fb3a1] hover:text-[#c7d4c7]"),children:[(0,t.jsx)(n.Cloud,{className:"w-4 h-4"}),"Online Infra"]})]}),(0,t.jsx)("p",{className:"text-sm text-[#8fb3a1]",children:"online"===l?"Managed hosting — we handle infrastructure, you focus on shipping.":"Deploy on your own infrastructure — full data privacy & control."})]}),"online"===l?i?(0,t.jsx)(e7,{}):(0,t.jsx)(m,{}):(0,t.jsx)(e8,{}),"online"===l?i?(0,t.jsx)(nf,{}):(0,t.jsx)(tr,{}):(0,t.jsx)(nx,{})]}),(0,t.jsx)(s.default,{})]})}}]);
Thinking…

So useNewPricingFlag is a prop passed to the PricingPageClient component from the server. If true → e7 (new 4-plan MAU-slider pricing: Free $0/1K, Pro $49/10K, Growth $149/40K, Enterprise $449/80K). If false → m (old 3-plan: Free $0/1,000, Pro $49/15,000, Growth $149/80,000).

I need to determine the actual value of useNewPricingFlag as rendered. The server-rendered HTML showed the Self-Host tab (default useState("selfhost")), so I can't tell from the HTML directly. But the flag value would be embedded in the RSC payload / props. Let me search the pricing HTML for "useNewPricingFlag".

Let me grep.

useNewPricingFlag decides between two Online pricing layouts. Let me find its actual value in the server payload.

cd /tmp && grep -o 'useNewPricingFlag[^,}]\{0,40\}' fb_pricing.html | head -5; echo "--- rsc payload search ---"; grep -oE 'useNewPricingFlag.{0,60}' fb_pricing.html | head -5; echo "--- any 'true'/'false' near PricingPageClient ---"; grep -oE 'PricingPageClient.{0,120}' fb_pricing.html | head -3
useNewPricingFlag\":true
useNewPricingFlag\":true
--- rsc payload search ---
useNewPricingFlag\":true}]\nb:[[\"$\",\"meta\",\"0\",{\"charSet\":\"utf-8\"}]
--- any 'true'/'false' near PricingPageClient ---
PricingPageClient\"]\n10:I[27201,[\"/_next/static/chunks/d96012bcfc98706a.js\",\"/_next/static/chunks/2532f69a4166d704.js\"],\"IconMark\"
Thinking…

useNewPricingFlag: true — so the new pricing (e7/e1) is live. My README's Online Infra table is correct:

  • Free $0, 1,000 MAU (hard cap)
  • Pro $49/mo, 10,000 MAU included
  • Growth $149/mo, 40,000 MAU included
  • Enterprise $449/mo or $4,490/yr, 80,000 MAU included
  • Overage +$20/mo per extra 10K MAU
  • Advanced RBAC +$60/mo

Good. Let me add a short note to the README that this was verified via the useNewPricingFlag: true prop, and that an older 3-tier layout (Pro 15K / Growth 80K MAU) exists in the bundle but is not active. That's a nice precision touch.

Let me add that note.

Confirmed useNewPricingFlag: true — my table reflects the live pricing. Let me note the verification in the README.

File edits

1 file

Completed
ModifiedREADME.md+5−0View changes

/sandbox/repo/README.md

Replacement excerpt

 Pulled from `featbit.co/pricing`, including the client-side "Online Infra" tab data that
 is not in the server-rendered HTML. Prices are USD, as published.
+
+The page carries two Online pricing layouts behind a `useNewPricingFlag` prop. The live
+page ships `useNewPricingFlag: true`, so the 4-plan MAU-slider layout below is what is
+actually shown. (The dormant 3-plan layout in the same bundle lists Pro at 15,000 MAU and
+Growth at 80,000 MAU — do not quote those.)
Thinking…

Let me do a final check of everything — run all scripts once more and show the file tree.

cd /sandbox/repo && echo "=== TREE ==="; find . -path ./node_modules -prune -o -path ./.git -prune -o -type f -print | sort; echo; echo "=== FINAL RUNS ==="; timeout 60 npm run demo --silent >/dev/null 2>&1 && echo "demo: PASS" || echo "demo: FAIL"; timeout 90 npm run check --silent >/dev/null 2>&1 && echo "check: PASS" || echo "check: FAIL"; timeout 40 npm start --silent >/dev/null 2>&1 || echo "start(no key): exits 1 with guidance (expected)"
=== TREE ===
=== TREE ===
./.env.example
./.gitignore
./README.md
./package-lock.json
./package.json
./scripts/check-connectivity.js
./src/config.js
./src/demo-offline.js
./src/index.js

=== FINAL RUNS ===
demo: PASS
check: PASS
start(no key): exits 1 with guidance (expected)
Thinking…

Everything works. Let me write the final summary.

I should be concise but cover:

  1. What I built
  2. That FeatBit DOES have a developer workflow I could act on (so I didn't stop)
  3. The blocker (credentials)
  4. Pricing
  5. Manageability assessment

Let me keep it tight.

Done. FeatBit does have a developer workflow I could act on, so I built the example rather than stopping — but I hit one hard blocker.

What I built — /sandbox/repo

FilePurpose
src/index.jsThe real example: connect to FeatBit Cloud, evaluate a boolean + multi-variant flag, print evaluation reasons, react to live flag changes, track a metric, flush + close
src/demo-offline.jsSame evaluation paths via the SDK's TestData integration — runs with no key and no network
src/config.jsEnv-driven config; hosted-cloud endpoints are defaults
scripts/check-connectivity.jsCredential-free diagnostic
README.mdFull findings

No Docker, no local stack, nothing long-running.

Verified live, no credentials: SDK installs; app-eval.featbit.co responds ~400–500ms; invalid keys → 401 on both server and client endpoints; wss://app-eval.featbit.co completes the handshake then closes on bad creds; targeting/rollout/reasons/live-updates all exercised offline; bad key degrades to your defaults without hanging.

Blocked: I can't get an SDK key

The hosted product is real (hostingMode: "saas", v5.4.10), but an agent cannot provision an account:

  • The main cloud (app.featbit.co) exposes only login-by-email, reset-password, refresh-token, logout. Probing signup/register/sign-up → 404. SPA routes are only login, onboarding, select-workspace.
  • login-by-email returns 200 EmailPasswordMismatch — login works, but you need an existing account.
  • A second dashboard (dashboard.featbit.co) does offer self-serve sign-up, GitHub OAuth, and magic links — but its auth is Supabase, so every path needs an email inbox or GitHub credentials I don't have.

To unblock: create an account, make a project/environment, create new-checkout (boolean) and pricing-tier (string), then export FEATBIT_SDK_KEY=<server-secret>. Zero code changes needed.

Pricing

The page hides the "Online Infra" tab in client JS, and carries two layouts behind a useNewPricingFlag prop. The live page ships true, so this is what's actually shown (the dormant layout quotes Pro at 15K / Growth at 80K MAU — don't use those):

Online Infra (hosted)PriceMAU included
Free$01,000 (hard cap)
Pro$49/mo10,000
Growth$149/mo40,000
Enterprise$449/mo or $4,490/yr80,000

Overage +$20/mo per extra 10K MAU (cap 300K); Advanced RBAC +$60/mo; annual saves ~16%; no seat limits — metered on unique user keys. Overage doesn't cut you off.

Self-host: Foundation $0 unlimited, Enterprise $3,999/yr, +Advanced RBAC $600/yr, Premium custom — no usage limits at any tier.

The real trade: self-host is free and unlimited but you own Kafka/Mongo/Redis; hosted Free caps at 1,000 MAU (evaluation-sized).

Easy for me to manage? Runtime yes, control plane no.

Good: server-side SDK evaluates locally in-memory (no per-call network); degradation is genuinely safe — verified that an unreachable server returns your defaults with reason ClientNotReady, no hang; boolVariationDetail gives machine-readable kind + human reason, ideal for an agent explaining why; TestData means flag logic is fully CI-testable with zero infra.

Hard: provisioning is human-gated, so end-to-end automation (create flag → deploy → verify) isn't achievable. Also: two dashboards with different auth models, featbit.io no longer resolves, and cloud.featbit.co/api.featbit.co return Vercel DEPLOYMENT_NOT_FOUND — it's mid-migration, so re-check endpoints before building seriously on them. Docs default to Docker Compose self-hosting.

Two doc gaps I hit and fixed: startWaitTime is milliseconds (undocumented in the SDK README — guessing "5" for five seconds silently yields a 5ms timeout and instant fallback to defaults), and TestData requires the client be built before the first update() or you get this.store.get is not a function.

AX Fundamentals

23 checks. Open an area for details.

This check is a quick preview. Test more tasks and models with Gauge Agents.

Test your product with Gauge Agents

AX Check by Gauge