FAIRVISOR Docs
⌘K
GitHub fairvisor.com

Gateway Integration

Integration patterns for self-managed and managed API gateways.

Fairvisor integrates as an inline decision service (POST /v1/decision) or as a reverse proxy.

Integration matrix

GatewayPatternPage
nginxauth_request (recommended) or direct OpenResty Luanginx
Envoyext_authz HTTP serviceenvoy
Kongpre-function call to /v1/decisionkong
TraefikforwardAuth middlewaretraefik
CloudflareWorker decision check (recommended) or reverse-proxy origincloudflare
AWS API GatewayLambda authorizer decision checkaws api gateway
GCP API Gatewayexternal auth pattern (ESPv2-style)gcp api gateway
Azure APIMinbound policy decision checkazure apim

Decision API contract

  • Method/path: POST /v1/decision
  • Required headers in decision_service mode: X-Original-Method, X-Original-URI
  • If policies use selector hosts: also forward X-Original-Host
  • Typical statuses: 200 allow, 429 reject, 503 unavailable

See Decision API for details.

MD

nginx
Integrating Fairvisor Edge with nginx using auth_request or direct Lua embedding.
Envoy
Integrating Fairvisor Edge with Envoy Proxy via the ext_authz filter.
Kong
Integrating Fairvisor Edge with Kong Gateway using the pre-function plugin.
Traefik
Integrating Fairvisor Edge with Traefik using the forwardAuth middleware.
Cloudflare
Integrating Fairvisor Edge with Cloudflare via Workers decision checks or reverse-proxy origin pattern.
AWS API Gateway
Integrating Fairvisor Edge with AWS API Gateway using Lambda authorizer decision checks.
GCP API Gateway
Integrating Fairvisor Edge with Google Cloud API Gateway/ESPv2 external auth pattern.
Azure API Management
Integrating Fairvisor Edge with Azure APIM using inbound policy decision checks.