📄️ Overview
Each carrier integration has its own flow module and API lib built on shared infrastructure (CDM, session management). For the rationale behind Fastlane's approach, see Why Fastlane. State and LOB variations within a carrier are handled through CDM configuration overrides managed by PMs in Fastlane Admin.
📄️ Fastlane Portal
The customer-facing quote-and-bind application. Customers arrive via a deep link from the agent's quoting tool (DA/Digital Agent) and are routed into the correct carrier flow based on session parameters.
📄️ Carrier Flows
Each carrier × LOB combination is a self-contained flow module under apps/fastlane-portal/src/app/pages/carriers///. They share a single SPA build and common providers, but each flow owns its own step sequence, page components, and navigation logic.
📄️ Session Management
Session data lives in Redis and is fetched per-page via API calls. The Zustand store holds only non-PII metadata (sessionUuid, quoteId, lob, carrier, state). If a session is missing from Redis, it is rehydrated from the legacy CRN database.
📄️ Fastlane Admin
The internal CMS where product managers configure how the platform behaves for each carrier × state × LOB combination — without touching code.
📄️ Canonical Data Model
The CDM is the backbone of Fastlane's configuration system. It defines a base schema of fields (drivers, vehicles, coverage, contact, common) that can be overridden at multiple levels:
📄️ Tech Stack
| Layer | Technology |