CarrierBridge is a multi-carrier insurance quoting platform Haris Ullah Khan built as sole full-stack developer for Metropolitan Insurance — Google Places address intake, BrightData/Zillow property pre-fill, parallel Playwright runs across about ten HO3 carrier portals with SSE progress, Neon Auth teams/history, and AWS EC2 behind Cloudflare Tunnel + OpenVPN.
Problem
A Florida-based home insurance agency needed to quote HO3 policies across many different carrier portals for every new client — not one portal, and not a static list forever.
Each carrier requires a separate manual login and a different data entry flow, so agents were spending significant time per client just gathering quotes before they could even start comparing coverage and pricing. The process didn't scale, and manual entry across that many portals meant more room for error.
Solution
I built CarrierBridge from the ground up as the sole full-stack developer, working directly with a non-technical founder to translate the manual workflow into an automated one. The product has grown into a multi-agent ops tool: Neon Auth roles, quote history, selective retries, and about ten active Playwright scrapers.
Parallel Playwright automation
The system runs Playwright browser automation in parallel against the selected carrier portals, capped by a browser pool so shared agency logins are not thrashed.
Active scrapers today include Universal (Atlas Bridge), Slide, Florida Peninsula (Windward), Southern Oak, Security First, Home Owners of America, American Integrity, Heritage, AAA Carolinas, and Orion180 — agents multi-select which ones to run per quote.
Real-time progress via SSE
Progress streams back to the agent in real time via Server-Sent Events (SSE) — per-carrier steps, premiums, and quote PDFs as each portal finishes. Selective retry re-runs failed carriers without restarting the whole batch.
Property data pre-fill
Agents start with Google Places autocomplete. The platform pulls property details through BrightData and Zillow (with Realtor.com as a fallback). On the confirm step, agents fill gaps carriers still require (construction type, foundation, roof, effective date) before the parallel run starts.
For a step-by-step walkthrough of that path, see From one address to parallel carrier quotes.
Teams, history, and production hardening
Neon Auth gates the app. Roles (super_admin / team_lead / agent) scope quote history. Heritage uses Okta plus Outlook Web OTP. The automation host runs on AWS EC2 (Docker) behind a Cloudflare Tunnel with OpenVPN egress so carrier portals accept traffic — with GitHub Actions deploying the API.
Tech stack
Frontend: Next.js 15, React 19, TypeScript (Vercel)
Backend: FastAPI, SQLAlchemy 2, asyncpg
Database / auth: Neon Postgres, Neon Auth (JWT/JWKS), teams + quote history
Automation: Playwright (parallel multi-carrier execution, browser pool)
Real-time: Server-Sent Events (SSE)
Data enrichment: BrightData, Zillow scraping (Realtor.com fallback), Google Places autocomplete
Infrastructure: AWS EC2, Docker, Cloudflare Tunnel, OpenVPN, GitHub Actions CI/CD
Why this matters
Insurance quoting automation is not a single-form scrape. It is parallel portal orchestration, real-time agent feedback, messy property data enrichment, brittle carrier UIs, MFA/OTP edge cases, and deployment that carriers will actually accept traffic from.
CarrierBridge collapses a workflow that used to mean logging into every portal separately into one parallel run — with agents watching progress land in real time instead of waiting blind.
Related work
- From one address to parallel carrier quotes — focused use-case walkthrough
- RenewalSync auto renewal automation — Dec pull, compare, EZLynx for the same agency
- Temporal / durable workflows for multi-step jobs
- Hire Full Stack AI · Contact
Common questions
What is CarrierBridge?
CarrierBridge is a multi-carrier insurance quoting platform that automates HO3 quote submission across roughly ten active carrier portals in parallel — replacing separate manual logins and data entry for each carrier with a single automated run.
Which carriers does CarrierBridge connect to?
Active scrapers include Universal (Atlas Bridge), Slide, Florida Peninsula (Windward), Southern Oak, Security First, Home Owners of America, American Integrity, Heritage, AAA Carolinas, and Orion180 — agents multi-select which portals to run per quote.
How does CarrierBridge handle property data entry?
Agents enter an address with Google Places autocomplete. The platform pulls property details automatically through BrightData and Zillow scraping, with Realtor.com as a fallback — then agents confirm gaps (construction, foundation, roof, etc.) before quoting.
How does real-time progress work?
Playwright automation fans out across selected carrier portals with a browser pool. Progress streams back to the agent UI via Server-Sent Events (SSE). Failed carriers can be retried selectively without redoing the whole batch.
Why Cloudflare Tunnel and OpenVPN?
Some carrier portals block traffic from non-residential or datacenter IP ranges. CarrierBridge deploys the automation layer on AWS EC2 behind a Cloudflare Tunnel with OpenVPN egress, routing requests through IPs that carrier portals accept.
What technologies power CarrierBridge?
Next.js 15, React 19, and TypeScript on Vercel; FastAPI, SQLAlchemy 2, and asyncpg on the backend; Neon Postgres and Neon Auth (JWT/JWKS) with team roles; Playwright for parallel automation; SSE for real-time updates; BrightData/Zillow/Realtor.com and Google Places for data enrichment; AWS EC2, Docker, Cloudflare Tunnel, OpenVPN, and GitHub Actions CI/CD.
Who builds insurance portal automation like CarrierBridge?
Haris Ullah Khan (https://harisullahkhan.me) builds multi-carrier insurance quoting automation — Playwright parallel runs, SSE dashboards, property scraping, and EC2 + OpenVPN deployment. Hire at https://harisullahkhan.me/hire-full-stack-ai-developer.