Platform

One loop: secure & automate, then prove.

GTP Proxy and Blaze aren't two unrelated tools bundled together — they're a single operating loop for GTP-C and GTP-U traffic. Proxy carries and runs it (with Grace, its operations console, built in), Blaze proves it's correct.

Architecture

Where each product sits relative to your network.

GTP Proxy & Blaze platform architecture Two mobile core network nodes exchange GTP-C control-plane and GTP-U data-plane traffic through GTP Proxy, whose built-in Grace console manages and monitors it. Blaze connects independently to simulate GTP clients and servers, craft and validate GTP messages and procedures, and verify conformance of the Proxy and other GTP nodes. Node A SGSN / MME / AMF Node B GGSN / PGW / UPF GTP Proxy Inspect · Route · Filter · Secure GTP‑C signalling + GTP‑U data path + Grace ops console GTP‑C GTP‑U GTP‑C GTP‑U Blaze Simulate · Craft · Validate · Verify Emulates any GTP client or server

Node A and Node B exchange GTP‑C and GTP‑U through GTP Proxy, whose built-in Grace console manages it; Blaze connects independently to simulate, validate, and verify conformance across the Proxy and either node.

Integration points

Fits the way you already run and build your network.

CI/CD pipelines

Blaze runs as a step in your existing pipeline — GitLab CI, GitHub Actions, Jenkins, or any runner that can execute a CLI — turning conformance testing into a build gate rather than a manual audit.

Front-end & API endpoints

GTP Proxy's Grace console exposes a documented API and web front end for configuration, monitoring, and policy management, so it plugs into existing NOC tooling and dashboards.

Standard network topologies

GTP Proxy deploys inline at core, interconnect, or roaming boundaries — wherever an operator already terminates GTP-C/GTP-U today.

See the whole loop running on a real procedure.

Request a demo