Implemented product system / Integrated evidence
VantaBlade FreeScan
A compact public data product connecting anonymous intake, external-data retrieval, normalized results, generated reporting, delivery, analytics, and a paid-product transition.
System overview
FreeScan turns a low-friction public action into an API-backed product workflow. Its engineering value comes from joining a real provider, a stable backend contract, result-state UX, report persistence, delivery, analytics, and the downstream DeepScan funnel.
Product problem
A public exposure check must make external provider data useful without leaking provider schema into the interface. Input validation, result transformation, clear states, report generation, storage, delivery, and funnel context all need explicit boundaries.
Engineering scope
- Public Next.js and React product flow with a FastAPI scan boundary
- Input validation, HIBP retrieval, and provider-response transformation
- Normalized result contract and explicit result, clear, and error states
- Report assembly, PDF rendering, artifact storage, and persisted records
- Separate scanned and delivery identity fields
- First-party analytics and the FreeScan-to-DeepScan product funnel
High-level architecture
From product input to durable outcome.
- Public product UI
- FastAPI boundary
- HIBP retrieval
- Normalized result contract
- Result-state UI
- Report assembly and PDF
- Storage and delivery
- Analytics and DeepScan funnel
Important system boundaries
- FreeScan is anonymous and does not inherit the company, membership, or entitlement model used by Workforce Exposure.
- The scanned identity and report-delivery identity are represented separately.
- Provider payloads are transformed by the backend; the frontend does not independently infer provider truth.
- FreeScan is a one-email baseline. DeepScan is a broader, separate paid workflow.
Capabilities demonstrated
- Anonymous API-backed public product with server-owned provider truth
- External-data transformation behind a stable application contract
- Clear result, no-known-exposure, error, and downstream CTA states
- Generated report, storage, persistence, and delivery workflow
- Attribution context and first-party product-funnel analytics
Reliability, authority, and privacy
- Scan and report paths are separate operations with separate failure boundaries.
- Rendering, storage, persistence, and email delivery can fail independently.
- The backend persists scan/funnel records, report records, and generated report artifacts.
- Privacy claims remain conservative and defer handling details to the Privacy Policy.
Transferable engineering patterns
- Public assessment, calculator, and qualification products
- External-data lookup and normalization workflows
- Generated-report products and document delivery
- Anonymous-to-paid product funnels
- First-party product analytics
Related focused public proofs
Inspect selected patterns independently.
These repositories demonstrate related patterns. They do not reproduce the complete product or imply code identity.
Engineering / Next action
Built this pattern into your own product?
Discuss a bounded product system, integration, workflow, or applied-AI capability with VantaBlade Engineering.