System Telemetry OverviewLIVE DATA PLANE
Real-time proxy pipeline enforcement, sliding window rate limits, and quota telemetry.
SETUP IN PROGRESS (0/5)Getting Started
Get Your First Request Through GateForge
Configure these once, then test the complete pipeline.
Step 1
Plan
Define traffic limits
Define rate limit + monthly quota
Next ActionCreate Plan →
Step 2
Organization
Create a tenant and assign its plan
Assign the organization to a Plan
PendingCreate Organization
Step 3
Upstream
Connect GateForge to your API
Tell GateForge where your API lives
PendingAdd Upstream
Step 4
Route
Decide which API path goes to which upstream
Map an API path to your upstream
PendingCreate Route
Step 5
API Key
Give a client permission to send requests
Create credentials for your client
PendingCreate API Key
WHAT HAPPENS WHEN A REQUEST ARRIVESRequest Lifecycle
1. API Key
Authenticate tenant
Verify X-API-Key hash
2. Organization
Resolve tenant
Lookup tenant identity
3. Plan
Resolve policy
Enforce limits & quota
4. Route Match
Find longest prefix
Match URI to upstream
5. Upstream Proxy
SSRF-safe forwarding
Filter DNS & forward
When a request arrives with X-API-Key, GateForge authenticates the key, resolves its organization and policy, matches the route, enforces traffic limits, and proxies the request to the configured upstream.
Active API Keys
0/ 0 total
SHA-256 Hash Verified
Registered Routes
0Active prefixes
Longest-Prefix Match
Tenants & Plans
0Organizations
Deterministic Policy
Rate Limiting
60sSliding Window
Atomic Redis Lua
Cluster Infrastructure & Upstream Health
GATEWAY DATA PLANE
Port :4000
REDIS 7 ATOMIC LUA
Port :6379
MOCK ORDERS UPSTREAM
Port :5001
MOCK PAYMENTS UPSTREAM
Port :5002
Recent Administrative & Telemetry Audit Feed
Live DB Stream| Action | Target | Actor | Organization | Timestamp |
|---|---|---|---|---|
| No recent audit events recorded. | ||||