112 users, 4 months, zero major incidents: Pintu's Grafana Cloud IRM migration

Pintu, one of the top three crypto exchanges in Indonesia, runs 24/7 trading operations where every incident affects revenue and user trust. In this talk, Pintu's Yusuf Hari Putera Perkasa explains how the team migrated 112 users from its previous incident-response vendor to Grafana IRM, consolidated eight self-managed Grafana instances into one Grafana Cloud account, and cut incident-response costs by roughly 38% — all without a major incident, by piloting in production, rolling out team by team, and keeping a fallback vendor live throughout. Chapters: 00:00 – Why Pintu looked at switching: cost and consolidation 02:00 – Why on-call reliability matters at a 24/7 crypto exchange 03:00 – Choosing Grafana IRM over a more mature incumbent 04:00 – The 5-week proof of concept, run in production 05:00 – Mapping the rollout by risk: low, medium, high 07:00 – Lesson 1: a cloud-region mistake that meant starting over 08:00 – Lesson 2: Okta sync bugs and schedule reverts 09:00 – Lesson 3: routing sensitive alerts to private Slack channels 10:00 – The result: one on-call page, self-service schedule swaps 11:00 – Consolidating 8 self-managed instances into Grafana Cloud 12:00 – Final numbers: 38% cost cut, 112 users, 4 months 13:00 – Advice for teams considering a similar migration