Live endpoints in use
Authentication
`/login`, `/me`, `/logout`
Assessments
/history, /scan, /scan-status/{job_id}
Assets
/reports/{file_path}
Workspace / Admin
Backend disconnected
Restoring session...
Documentation
Operator guide
How this scanner runs today
The parallel Next.js frontend reuses the live staging API and presents the existing backend workflow more clearly. The current Node-served staging frontend remains available during migration.
Backend flow
Current pipeline unchanged
Crawl website, analyze DPDP signals, build LLM input, generate report, render HTML, generate PDF.
Scan lifecycle
1. Crawling
Collect pages, normalize domains, and identify likely legal endpoints.
2. Analyzing
Extract DPDP-relevant signals from the crawl result.
3. Scoring
Prepare model input and generate the compliance assessment payload.
4. Report output
Render HTML, generate PDF, and store report links in history.
Operator notes
This migration keeps the working staging frontend available while the Next.js frontend matures in parallel.
Backend crawler, classifier, report generation, and PDF flow remain unchanged unless explicitly edited.
Real-world blocked or anti-bot sites may still fail scans. Those outcomes should surface through history and report status, not hidden in the UI.