Mojo Platform Reviews & Product Details

The built‑in monitoring tooling is very generic out‑of‑the‑box. It only captures basic CPU and memory metrics, with no dedicated views tailored for real‑time media server workloads. I can’t pull native data for active call counts or streaming throughput directly from its UI. One incident really drove this home: two months ago, one of our bare‑metal nodes started dropping partial video packets for client consultations. Mojo’s dashboard only showed normal‑looking CPU and memory figures, so I spent close to three hours troubleshooting blind before our third‑party Prometheus collector flagged the actual streaming traffic anomaly. If native monitoring covered media‑specific telemetry, I would have spotted the issue minutes sooner. Template handling is another real pain point. We keep hardened, fully‑tested server templates built for our iland Hybrid Cloud staging environment, yet there is no native way to import them into Mojo. Last month I spun up three new bare‑metal nodes for an upcoming project. I had to push every critical configuration setting via our external automation scripts one by one. During that process one small network parameter failed to apply silently on one node. That node would not accept incoming media traffic, and I lost half a workday hunting down that oversight. All these gaps don’t fully block our deployments, but they add unexpected troubleshooting overhead to my daily deployment work. Review collected by and hosted on G2.com.

To enhance the Mojo Platform, consider integrating more advanced monitoring tools that provide detailed insights into real-time media server workloads. This could include metrics for active call counts, streaming throughput, and media-specific telemetry. Additionally, developing a feature to import existing server templates from other environments would streamline the deployment process and reduce manual configuration errors. Review collected by and hosted on G2.com.

Mojo Platform solves the severe resource bottlenecks we kept hitting during peak‑volume client video consultations. Before switching over, we ran our VideoMost media services on iland Hybrid Cloud large VMs. I still clearly remember a tough workday last year: fourteen concurrent client consultation sessions kicked off all at once, and hypervisor overhead ate up so much compute power that multiple video feeds froze. We had to pause active customer meetings, and our support team spent the rest of the afternoon sending apology emails and rescheduling appointments. That was a pretty stressful incident for our small infrastructure team. Now with Mojo, I can programmatically spin up additional bare‑metal hardware ahead of forecasted high‑traffic days. The API‑first design cuts out the slow manual hardware procurement process we used to depend on. We no longer wait weeks for vendor hardware shipments when project timelines are tight. Every newly provisioned bare‑metal node gets consistent baseline configurations pushed through our existing automation scripts. This drastically reduces the risk of inconsistent settings across our production and staging environments. We get the un‑virtualized hardware performance our real‑time video workload demands, helping us avoid those disruptive live‑meeting outages that hurt our client relationships. It lets me focus more on validating enterprise communication deployments instead of firefighting preventable infrastructure resource failures. Review collected by and hosted on G2.com.

We needed to provision 30+ datacenters with Anthos Bare Metal. We used Mojo to pave over the existing bare metal servers with Ubuntu 20.04. Mojo provided a single point to do all of this. Review collected by and hosted on G2.com.