Web enqueues only
Next.js app does not process queues.
Public PreviewTesting header enabled
Open sitemap
/workers
Async workers
Heavy workloads belong in job processors, not the API.
Risk jobs, market ingestion, reports, and notifications run in separate workers for safety and scalability.
What runs asynchronously
Risk analytics
Jobs
VaR, stress, scenarios
Market ingestion
Pipelines
Snapshots and refresh
Reporting
Exports
PDF/Excel artifacts
Notifications
Fanout
Alerts and ops signals
Production-safe boundaries
Idempotent handlers
Safe retries and dedupe keys.
Backoff + timeouts
Integration boundaries are guarded.
Queue monitoring
Operational visibility for stuck jobs.
Correlation IDs
Connect jobs to API actions and audits.
Extraction-ready
Workers can become separate services later.
Want to see a job trace?
We can show a full run from API action → job enqueue → processor → artifact publish.
Related pages
Cross-links across the public site for architecture, trust, specialty modules, and rollout.
Risk
Async analytics and explainable risk outputs.
Reporting
Governance-ready exports and artifact workflows.
Architecture
Modular monolith approach with extraction-ready boundaries.
Observability
Structured logs, trace context, and queue visibility.
Integrations
Port-based adapters for external providers and systems.
Docs Index
Top-level public documentation index.