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.
Where each product sits relative to your network.
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.
Secure & automate → test & assure.
GTP Proxy
Sits in the live GTP-C/GTP-U path, inspecting, routing, filtering, and securing traffic between nodes — with Grace, its built-in console, for day-to-day configuration and monitoring.
Test & assureBlaze
Emulates GTP nodes, crafts and plays procedures, and validates that everything behaves to spec.
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.