Mar 13, 2026
GeekyAnts migrated one of India’s largest banks from .com to .in during a code freeze
RBI deadline. Code freeze. Peak traffic. See how GeekyAnts executed a seamless .com to .in migration for one of India’s biggest banks.
Author
Subject Matter Expert
Book a call
Table of Contents
Background Information: On February 7, 2025, the RBI mandated that banks migrate to the new domain framework before the October 31 deadline. The bank’s internal release policy restricted major changes until after Diwali in October, compressing the execution timeline. Here’s how the migration was delivered on time — without disrupting a single transaction.
Getting the exception approved
A code freeze is a commitment. To get one approved at a bank of this scale, you need to demonstrate that the change carries less risk than leaving it undone.
Discovery before the freeze started
- A full audit of 100+ external partner integrations and their domain dependencies.
- Domain segmentation: specialist teams assigned to critical product areas such as the Loans Expressway, where user journeys had unique architectural dependencies that a generic migration approach would have broken.
2 AM deployments and what they covered
The technical scope covered five categories:
What changed during the migration windows
- Backend microservices: environment variables and base URLs updated to reference the .in domain.
- Infrastructure: Ingress rules updated to accept .in traffic into the pods. SSL/TLS certificates are provisioned to prevent browser security warnings.
- Firewall layers: WAF rules updated across AWS WAF, Nginx, and Palo Alto to allow traffic from the new domain.
- CDN and cache: old .com references purged. CDN reconfigured to serve exclusively from the .in origin — required to ensure Diwali offer pages served accurate, fresh content.
- SEO continuity: 301 redirects implemented from .com bookmarks and indexed URLs to .in equivalents. CORS policies updated to allow API calls from the new domain.
- Identity systems: Keycloak and internal email infrastructure migrated to .in.
The trust problem: telling customers before they notice
What the migration actually required
The code freeze added a constraint that forced every decision to be made in advance. There was no room to discover a missed WAF rule at 3 AM during Diwali week. The discovery phase and the segmentation of teams by domain were the risk controls that made the nocturnal execution possible.
As a result, the bank met its RBI compliance deadline. No customer transaction was interrupted during the festive period. The domain change was invisible to end users.
Three things that made this work
1. Discovery before the constraint hit
The 100+ partner audit and the domain segmentation happened before the freeze. By the time the deployment windows opened, there were no unknowns left in the scope.
2. The deployment window as a forcing function
Working in 3-hour nocturnal windows with no room for incident response concentrated the team’s planning. Every step was scripted, every rollback condition defined, before the first change went live.
3. Communication ran ahead of the technical change
About this Project
The migration was executed by GeekyAnts in partnership with the bank’s internal engineering and compliance teams. The work spanned infrastructure, security, CDN, identity, and product communications. If you are working through a comparable constraint — regulatory deadline, legacy system dependency, or a change that cannot go wrong during a peak period — the approach documented here is one we have tested and delivered under production conditions.
Subscribe to Our Newsletter
Subscribe to RSS
Press & Media Hub RSS FeedRelated Articles.
More from the engineering frontline.
Dive deep into our research and insights on design, development, and the impact of various trends to businesses.
Jun 17, 2026
Google I/O 2026 Mobile Playbook: AI Studio, Android CLI, and Antigravity for App Development
Google I/O 2026 shifted mobile development from code assistance to full lifecycle delivery. This blog breaks down what that means for Android, Flutter, and React Native teams.
Jun 17, 2026
Beyond the Chatbot: Architecting Enterprise Workflows with Managed Agents in the Gemini API
A practical guide to building production-ready agentic workflows with Google's Managed Agents API, covering architecture, governance, and where enterprise teams should start.
Jun 16, 2026
Integrating AI with Wearable Healthcare Apps: Architecture, Compliance & ROI
A technical and compliance-focused guide for U.S. healthcare founders and providers on building AI-enabled wearable healthcare apps across architecture, compliance, and ROI.
Jun 16, 2026
HL7 and FHIR for AI Healthcare Platforms: What It Takes to Build for Production
A practical guide covering the HL7 and FHIR standards, production readiness requirements, implementation roadmap, architecture considerations, and compliance controls that AI healthcare teams need to address before enterprise deployment.
Jun 12, 2026
How AI-Driven Fraud Prevention Reduces Financial Losses and Operational Costs
This blog examines how AI-driven fraud detection reduces financial losses and operational costs, backed by real data from HSBC, the US Treasury, Visa, and Forter.
Jun 11, 2026
How AI-Powered Financial Platforms Are Increasing Customer Retention and Revenue
This blog breaks down how AI helps financial institutions retain customers and grow revenue, using real data from banks like DBS and NatWest to show what that looks like in practice.