How Quantfil is structured and shipped.

Architecture

The current release is deployable to static hosting and avoids live browser API calls. Filing dashboards, comparison cards, and chart inputs are all loaded from local JSON.

Data sourcing

The long-term ingestion path is designed around SEC EDGAR build-time sourcing, allowing the site to stay fast and cacheable while still presenting filing-backed research surfaces.

The daily refresh path now also supports a tracked-symbol universe and a merged earnings collection covering last week, this week, and next week. Upcoming dates still require issuer IR calendars or a licensed calendar feed beyond SEC alone.

Quantfil now ships a formal upcoming-earnings seed contract so scheduled events can be layered into the static dataset with source URLs and company-level metadata, then refreshed into production through the Lambda worker.

Public compliance scope

The live public site currently implements static-site controls: policy routes, cookie consent, privacy-request intake, takedown intake, official SEC source links, and explicit informational-only labeling in the report UI.

Backend compliance workstream

The broader plan also requires backend controls before any paid or account-based launch, including SEC request limiting, required user-agent headers, raw document caching, provenance hashes, audit logs, PII handling, and sanctions screening. Those are tracked as engineering launch gates, not represented as current front-end features.

Examples

Use the filing console, coverage library, and company dashboards to see how Quantfil converts static data into visual research workflows.