Rohan SoniAuthor of the Inspired Entertainment case studyGoogle
Integration team. Java Spring Boot adapters for betting-operator wallet APIs. Gemini CLI, now Antigravity CLI.
Google Developer forums (Google case study), published Read the case study (opens Google Developer forums (Google case study) in a new tab)
Observation
Inspired Entertainment had Gemini CLI take over its payment-adapter builds and cut the manual dev days on each.
- Takeaway
- Gemini CLI paid off on an adapter the team builds again for every operator, guided by written markdown guidelines. Counting dev days per integration gave the team a before and after it could report.
- What happened
- Each new betting operator needed a custom Java Spring Boot adapter, built by a scrum team of five over 6 to 8 weeks. Developers now give Gemini CLI the operator's API documentation and the company's markdown guidelines, and it writes the adapter. Google's write-up reports builds down to one week and manual work down from 40 dev days to 5. Staffing per integration fell from five people to two.
- Vendor case study
- Customer-reported figures
Deployment details
Integration team. Java Spring Boot adapters for betting-operator wallet APIs. Gemini CLI, now Antigravity CLI.
- Vendor case study
- Customer-reported figures
- Team
- Inspired Entertainment integration team, now 1 developer and 1 QA per integration
- Workload
- Wallet adapters for betting operators, plus a Java 8 to Java 25 upgrade
- Product version
- Gemini CLI, now Antigravity CLI
- Measurement
- Dev days per integration, 40 to 5; build time, 6 to 8 weeks to 1 week