API gateway

Connect the gateway you already run, or install ours in front of your API — this is where the credentials live; API Gateway and API Monitoring only read what it collects

Connect a gateway you run

The backend reads per-route counters straight from the gateway, so nothing has to be installed beside it. Supported today:

  • Apache APISIX, Kong, Tyk, Traefik, KrakenD — Prometheus metrics endpoint
  • AWS API Gateway — CloudWatch, via the account's IAM role
  • Azure API Management — Azure Monitor metrics
  • Apigee — Google Cloud service account

The form is built from the backend's own catalogue, so the fields always match what it validates.

Install ours

No gateway yet? "Install our gateway" enrolls an APISIX instance in front of your API and returns the commands to run it. It reports the same route counters, so every page downstream works the same way.

Routes themselves come from the APISIX config file, not the API.

Connected gateway

One row per organization — the gateway this tenant connected, and whether it answers

GatewayProviderAccountRegionRoutesStatus

nothing connected yet

0Not connected

No matching results

LoveHeartBeat - A Product from RootVyana.

v1.24.0

Theme Customizer

Explore different styles according to your preferences

Color Scheme
RTL

Change text direction

Support Chat

Toggle support chat

Navigation Type
Vertical Navbar Appearance
Horizontal Navbar Shape
Horizontal Navbar Appearance
Purchase template
customize