​
FL Web

FL Web is the product-facing, multi-tenant control plane. It is separate from the intelligence REST API: browser sessions remain in FL Web, while trusted server-side functions call tenant-scoped commercial APIs when needed. The original ForwardLane repository graph is an historical deployment example, not the data boundary of an FL Web organization.

​
Public experience

​
Authenticated organization experience

After Better Auth sign-in and organization onboarding, FL Web provides portfolio, company, hosted-job, billing, CLI-run, private-report, member, and settings views. The billing area reads the credit wallet, ledger, packs, plans, and capped auto-reload policy. Hosted jobs and reports are estimate-first and require an explicit maximum-credit confirmation before submission. Explicitly allowlisted platform administrators who are also active workspace owners receive a native Observability area for Opik project health, traces, costs, latency, and dashboard definitions. Billing, jobs, reports, and paired CLI data are organization scoped; Opik is a platform-admin surface over the configured observability workspace, not a cross-tenant report browser.

​
Report center

When analysis data is available, FL Web exposes complementary report views rather than a single generic export: The selected workspace, role, source data, and deployment configuration determine which report views are available. A displayed template does not mean that an on-demand generation workflow is enabled for every organization.
Member management and parts of company detail remain planned UI surfaces. Hosted jobs and reports expose their actual fl-api status and never represent queued or running work as complete. Some dashboard report templates may still be placeholders in a given release; use the active report-center and API routes for supported workflows.

​
Security boundary

FL Web validates membership server side, obtains a request-scoped organization service credential, and sends it only to fl-api with X-Organization-Id. Browser code never receives that credential. FL Web has no direct Polar or worker authority; checkout, wallet, estimate, job, report, and billing operations all cross the fl-api boundary. Public scoring is local to FL Web. Authenticated private analysis uses the user’s GitHub OAuth access within an FL Web server function; saved score records live in FL Web’s database.

​
Local development

Use bun run check for the full FL Web test, build, production-smoke, and type-check sequence. See the operational runbook for deployment configuration.