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

Gateway Pattern Page
nginx auth_request (recommended) or direct OpenResty Lua nginx
Envoy ext_authz HTTP service envoy
Kong pre-function call to /v1/decision kong
Traefik forwardAuth middleware traefik
Cloudflare Worker decision check (recommended) or reverse-proxy origin cloudflare
AWS API Gateway Lambda authorizer decision check aws api gateway
GCP API Gateway external auth pattern (ESPv2-style) gcp api gateway
Azure APIM inbound policy decision check azure 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.