ForgeRouter docs

Security and data handling

Gateway controls, logs, secrets, limits, Community caveats and compliance boundaries.

Data sensitivity warning

Community providers are not suitable for sensitive prompts, personal data or confidential code unless the client has consciously accepted that risk. A provider no-log policy is a provider declaration until independently verified for that dimension.

Data handling

  • Prompts and responses are not stored by ForgeRouter by default.
  • Request snapshots store routing, price, trust tier, country and policy metadata without prompt or response content by default.
  • Application logs should exclude prompts and responses by default.
  • Provider private identity, billing address and endpoint secrets are private operational data.
  • Endpoint secrets are encrypted and are not re-displayed after saving.

Gateway security controls

ForgeRouter gateway controls reduce network and routing risk before a provider endpoint is called. They are controls, not SLA guarantees.

  • SSRF guard
  • DNS rebinding checks
  • Private IP, link-local and cloud metadata IP blocking
  • Dangerous redirect blocking
  • Egress control
  • Connection, first-token, inter-chunk and total timeouts
  • Client cancellation propagation
  • RPM, TPM, concurrency, request size, response size and budget limits
  • Kill switches by provider, endpoint, deployment, model or profile

API key security

  • Client API secrets are shown once at creation and then stored hashed.
  • Keys can be revoked by the client and suspended by admins when abuse or account risk is detected.
  • Policies limit routing profile, Community opt-in, price, budget, max tokens, allowed providers and denied providers.
  • Community opt-in is per key and revocable without changing other keys.

Manage keys from API keys.

Provider security

  • Provider payout changes are sensitive operations and should require double validation before production payouts.
  • Admin suspension and reactivation actions must leave an audit trail.
  • ForgeNode reports inventory and heartbeat data; it must not collect prompts or responses.
  • ForgeNode must not accept arbitrary shell commands from ForgeRouter.
  • ForgeNode is never the single billing authority; request ledger authority stays in the ForgeRouter gateway.

Location, compliance and limits

  • Provider location can be declared by provider, inferred from observations or verified by ForgeRouter for a specific dimension. These labels are not interchangeable.
  • The private-eu profile currently restricts routing to verified/enterprise deployments in the EEA and must fail if no deployment matches. Retention compatibility is not yet modeled or enforced, so this profile is not a no-retention guarantee.
  • DPA and professional Verified workflows are future or contract-specific capabilities, not implied by Community publication.
  • Limits and budgets reduce blast radius; they are not availability, confidentiality or model-identity guarantees.
  • Public docs omit internal hosts, credentials, tokens and incident-only operational details.