G2

Verified User in Wireless

Mid-Market (51-1000 emp.)

10/20/2026

"Powerful DevOps Automation and 24/7 Support, with Documentation Gaps"

4/5

What do you like best about ITGix?

I value ITGix’s hands-on team of certified DevOps and cloud engineers and the reliable, repeatable automation they built for our wireless monitoring workloads. Before switching over from CloudNexus, every update to our RF monitoring agents had to be pushed manually to each tower location one at a time. It was tedious work, and we constantly worried about typos or misconfigured settings taking our telemetry offline. ITGix stepped in to help us containerize our RF monitoring tools and build end-to-end CI/CD pipelines that automatically validate every single change before it ever touches live infrastructure. We had a real win on that regional carrier project with our 12 tower sites. Previously, a similar update would require two of my engineers to pull an overnight shift, logging into each edge node individually. With the pipeline ITGix built, we rolled out a major agent update in just a few minutes. The automated checks caught a minor log formatting error before release, so it never reached the live tower hardware. That completely avoided the kind of outage we had back when CloudNexus was our provider. Their Kubernetes setup also makes it much faster to spin up new monitoring instances whenever we add new tower sites across our AWS, Google Cloud, and on-prem edge environment. I also really appreciate their ISO27001-compliant practices. We work closely with regional carriers, and they regularly request evidence of our security controls for audits. ITGix helped us lock down permissions and organize audit logs, which cut down the hours we spend prepping for compliance reviews. Their 24/7 proactive monitoring and support is another huge plus. A few months ago, our Kubernetes cluster hit an unexpected overnight memory and CPU spike. ITGix’s on-call team spotted the anomaly through our monitoring stack before any of our internal alerts went off. They quickly rebalanced the workload and stabilized the environment before our tower telemetry feeds went down and the carrier noticed anything was wrong. Their experts don’t just set up tools and disappear either. They give us tailored strategy advice for our unique wireless edge workloads, not generic enterprise software recommendations. All of this takes a massive load off my plate. I spend way less time firefighting infrastructure failures and chasing manual deployments, and I get to focus more on planning long-term network expansions for our carrier customers. We still keep using our supporting stack, including Fast.io, Prometheus, Grafana, Terraform and Slack alongside ITGix. Review collected by and hosted on G2.com.

What do you dislike about ITGix?

Even though ITGix has delivered great automation for our wireless infrastructure, there are some pain points that still create headaches for our team. The biggest one is outdated documentation. The Kubernetes runbooks they provided don’t always reflect what’s actually running in production. We ran into a critical issue a few months ago during an incident. One of my senior engineers followed their written rollback procedure to revert a monitoring agent change, but the instructions pointed to an old, retired cluster namespace. The rollback command failed entirely, and we ended up with partial telemetry loss across three of our tower sites overnight. We burned a couple of hours scrambling to manually restore service before we could get everything back online. That whole mess could’ve been avoided if their docs stayed synced with production changes. Their standard onboarding workflow also feels pretty generic. It’s built for traditional enterprise software development teams, not telecom companies running RF telemetry on remote tower edge hardware. When we first got started, the default CI/CD playbooks they handed over didn’t account for our edge network constraints. We had to spend extra engineering time modifying and adapting those templates to work for our tower deployments. I wish they’d spend more time up front learning about our wireless use case instead of dropping pre-built generic workflows on us. The monthly performance reports they send over also leave a lot to be desired. The reports mostly focus on cloud spending and overall cluster uptime. Those metrics matter, but what I really need to share with leadership is data around our edge deployments, like how often we push agent updates and how many rollbacks we perform. ITGix’s standard reports don’t track those telecom-focused KPIs, so I have to build my own separate tracking spreadsheets each month to compile that information. I also remember the transition over from CloudNexus was tougher than expected. Our old environment was messy and poorly documented, and during migration testing, we had temporary telemetry gaps on our edge nodes. We had to spend extra time adjusting firewall rules on our tower hardware, which pushed our cutover timeline back a few days. None of these issues are dealbreakers, but better live-updated documentation, telecom-specific onboarding, and customized operational reporting would save our team a ton of extra manual work. Review collected by and hosted on G2.com.

What problems is ITGix solving and how is that benefiting you?

Before partnering with ITGix and leaving our old vendor CloudNexus behind, our team was stuck relying on slow, risky manual deployments across our multi-cloud and on-prem wireless monitoring systems. Back then, every time we needed to push updates to our RF monitoring agents, engineers had to manually log into each remote tower edge node. That process was error-prone, and we learned the hard way how damaging a simple configuration mistake could be. We had a major incident when we tried rolling out an update for our 12-site carrier deployment with CloudNexus; a bad config parameter knocked out telemetry on half the towers overnight. We lost hours of data and almost lost that carrier client’s trust. ITGix solved that core problem by building us automated CI/CD pipelines and Kubernetes orchestration for our edge workloads. Now every configuration change and agent update runs through automated validation checks first. If something is wrong, the pipeline blocks the release before it reaches our live tower hardware. This eliminates the human error that used to cause costly telemetry outages. ITGix also helped us implement ISO27001-aligned security controls, which drastically improved our audit readiness for carrier clients. Before, we spent weeks gathering logs and proof of access controls every audit cycle. Now most of that evidence is already organized within the infrastructure they built. Another big win is their round-the-clock incident support. Our wireless tower systems run nonstop, and outages can happen at any hour. Previously, overnight issues were fully on our small internal team to troubleshoot alone. A few months ago, our Kubernetes cluster hit a sudden resource spike after hours. ITGix’s on-call team detected the problem early and remediated it before the carrier saw any disruption. This shift has had a huge positive impact on our operations. My engineers no longer need to pull late-night shifts doing repetitive manual deployments. We spend less time putting out fires and responding to preventable outages, and more time designing and scaling wireless networks for our carrier partners. We still run Fast.io, Prometheus, Grafana, Terraform and Slack alongside ITGix, and all these tools work together to keep our tower monitoring reliable. ITGix took the heavy lifting of complex DevOps and multi-cloud management off our plate, making our whole wireless infrastructure operation more stable and scalable. Review collected by and hosted on G2.com.