Company Name: Pintu
Industry: Financial Services (Cryptocurrency)
Pintu, one of the top three crypto exchanges in Indonesia, runs 24/7 trading operations where an outage can hit both revenue and user trust immediately. In 2024, Pintu migrated 112 users from a legacy incident-response vendor to Grafana IRM, consolidated eight self-managed Grafana instances into a single Grafana Cloud account, and cut its incident-response costs by roughly 38% – without a major incident during the switch itself.
The challenge
Pintu had been running the same observability and incident-response setup for four years, split across three vendors. By 2024, the team was reviewing the stack to see if it was time to consolidate. “The motivation was more about consolidation and cost reduction,” said Yusuf Hari Putera Perkasa, who led the migration.
Underneath the vendor question was an operational one: Pintu was running eight separate self-managed Grafana instances, each with its own user access to manage, patch, and upgrade. “It was honestly exhausting,” Perkasa said.
The solution
The team gave itself five weeks for a Grafana IRM proof of concept – run directly against production, not staging, “because replicating production is hard” — piloting with 66 users across research, a sandbox, a live pilot, team training, and a final review. Once the POC confirmed the fit, Pintu had four months to migrate everyone, rolling teams out gradually by risk category: low-risk teams first, then medium, then the highest-risk teams — including the operations team, the finance team, and the C-level’s own escalation chain – last. That vendor stayed live as a fallback throughout, and any users who’d only been using their old tool for on-call rotation, without any alerts wired in, were cut from the list entirely.
The journey wasn’t always linear – as any migration can be – but Pintu worked through it in close partnership with Grafana Labs’ support team. Grafana Cloud’s flexibility meant Pintu could build its own workaround to route sensitive, money-related alerts to private Slack channels instead of public ones, fitting the platform to Pintu’s own data-sensitivity requirements.
What came out the other side: a single dedicated page showing who’s on call for every team, one click away from paging the right people through Grafana IRM; monitoring data from tools like Datadog rerouted directly into Grafana IRM instead of the old vendor; and self-service schedule swaps for on-call engineers, powered by Grafana Cloud’s RBAC, instead of needing someone else to make the change for them.
The impact
Pintu now runs its entire incident-response and observability stack through Grafana Cloud, with one team managing access and cost instead of eight separate instances.
- Migrated 112 users to Grafana IRM in four months, without a major incident
- Cut incident-response costs by roughly 38%, with additional savings from consolidating vendors and infrastructure
- Consolidated eight self-managed Grafana instances into a single Grafana Cloud account
- Centralized user access management instead of handling it instance-by-instance
- Gave on-call engineers self-service schedule swaps via Grafana Cloud RBAC