Proxies & Gateways
Relevant source files
The following files were used as context for generating this wiki page:
FusionOps utilizes a multi-layered proxy and gateway architecture to facilitate secure, anonymous, and cross-origin communications. This system serves two primary purposes: providing a CORS-enabled bridge for frontend applications to access external APIs and maintaining an operationally secure proxy pool for ban intelligence and risk analysis.
The architecture consists of Cloudflare-based workers for lightweight request forwarding and a dedicated Operations Proxy Gateway for more complex routing and IP quality management. These components integrate with the wider Hermes + FBIS System to ensure traffic quality and account isolation.
Sources: CLAUDE.md, HERMES_FBIS_AUDIT.txt, INFRASTRUCTURE_SETUP.md
CF Proxy (CORS Proxy)
The cf-proxy is a specialized Cloudflare Worker designed to resolve Cross-Origin Resource Sharing (CORS) limitations. It acts as a transparent intermediary for the FusionOps dashboard, allowing the Astro-based UI to interact with external APIs that do not natively support browser-side requests from the project's domain.
Architecture and Flow
The CF Proxy intercepts incoming requests, strips or modifies restricted headers, and forwards the request to the target destination. It then appends the necessary CORS headers to the response before returning it to the client.
This worker is extremely lightweight, with a raw size of approximately 2.31 KB and a deployment name of lp-cors-proxy.
Sources: apps/cf-proxy/worker.js, CLAUDE.md, PRODUCTION_STATUS.md
Proxy Gateway (Operations)
The Proxy Gateway is a more robust component situated within the apps/proxy-gateway/ directory. Its primary role is to manage an operational proxy pool utilized by the FBIS (FusionOps Ban Intelligence System) agents. It provides internal services for rotating IPs and maintaining anonymity during automated audits.
Proxy Intelligence Tools
Integration with the FBIS MCP Server enables the following tools for proxy management:
- Proxy Intel (
proxy.py): Provides telemetry and health checks for the current proxy pool. - Risk Scoring (
risk.py): Utilizes proxy data to calculate risk scores (0-100) based on IP quality and historical ban patterns. - Argus Agent: A specialized agent dedicated to proxy and IP analysis.
Operational Component Table
| Component | Technology | Purpose |
|---|---|---|
ops-proxy-gateway | Node.js (MJS) | Primary entry point for operational proxy routing. |
ip-quality-pipeline | JavaScript | Service for validating IP integrity and preventing leaks. |
argus.skill.md | Hermes Skill | Autonomous agent logic for proxy/IP risk analysis. |
Sources: apps/proxy-gateway/ops-proxy-gateway/index.mjs, HERMES_FBIS_AUDIT.txt, src/services/ip-quality-pipeline.js
IP Quality Pipeline
The IP Quality Pipeline is a critical service that ensures operational security by validating the proxy exit nodes. It prevents "IP leakage" where the actual server or user IP might be exposed to target platforms.
The pipeline calculates a proxy_risk component as part of the overall system health assessment. A score between 81-100 results in a CRITICAL status, triggering auto-pause rules for associated advertising accounts.
Sources: HERMES_FBIS_AUDIT.txt, src/services/ip-quality-pipeline.js
Configuration and Deployment
The proxy infrastructure is managed through environment variables and Cloudflare Worker bindings. The system distinguishes between "Production" and "Legacy" databases for storing proxy-related telemetry.
Key Configuration Variables
FUSIONOPS_API_URL: The endpoint for the API Worker to write risk scores derived from proxy intel.FUSIONOPS_API_KEY: Bearer token for authenticating proxy-derived analysis.database_id: D1 binding forfusionops-main-new-v2which tracks operational logs.
Deployment Status
| Worker Name | Production URL | Status |
|---|---|---|
lp-cors-proxy | https://lp-cors-proxy.misty-feather-556e.workers.dev | Deployed |
proxy-gateway | Internal Only | Operational |
Sources: INFRASTRUCTURE_SETUP.md, PRODUCTION_STATUS.md, HERMES_FBIS_AUDIT.txt
Summary
The Proxies & Gateways module provides the necessary anonymity and connectivity layer for FusionOps. While the CF Proxy handles the technical requirements of the frontend UI, the Proxy Gateway and IP Quality Pipeline provide the security infrastructure required for the Hermes autonomous agents to perform ban intelligence and traffic quality analysis without compromising the project's operational integrity.