Security
Product trust depends on more than encryption badges
SherpaQuant is being hardened as a production subscription product: authenticated data access, billing safety, monitored orchestration, and explicit provenance on financial surfaces.
Authentication and data boundaries
User-facing portfolio, alert, export, and key-management routes run through authenticated server access and row-level security rather than broad privileged fallbacks.
Billing hardening
Stripe webhook replay protection, authenticated checkout and portal routes, and explicit billing lifecycle handling reduce subscription risk.
Operational monitoring
The Python orchestration layer publishes health, stale-job, failure, and Redis budget signals so scheduler drift and data outages are visible.
AI ALPHA transparency
Major AI ALPHA surfaces now publish freshness, source metadata, and benchmark validation scorecards instead of hiding model evidence behind internal-only code.
Frontend hardening
The product shell uses a tightened CSP path, explicit stale/degraded states, and route cleanup to reduce ambiguous or misleading live-looking surfaces.
Need deeper methodology or live status?
Use the public methodology and status surfaces to inspect model framing and current platform health.