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.
Related Articles.
More from the engineering frontline.
Dive deep into our research and insights on design, development, and the impact of various trends to businesses.
Apr 23, 2026
Why Healthcare AI Initiatives Fail Before They Reach Clinical Impact
This blog covers the key reasons healthcare AI initiatives fail before reaching clinical impact, from poor data infrastructure and stalled pilots to the physician buy-in gap.
Apr 20, 2026
AI MVP Development Challenges: How to Overcome the Roadblocks to Production
80% of AI MVPs fail to reach production. Learn the real challenges and actionable strategies to scale your AI system for enterprise success.
Apr 17, 2026
How to Build an AI MVP That Can Scale to Enterprise Production
Most enterprise AI MVPs fail before production. See how to design scalable AI systems with the right architecture, data, and MLOps strategy.
Apr 17, 2026
How to De-Risk AI Product Investments Before Full-Scale Rollout
Most AI pilots never reach production, and the reasons are more preventable than teams realize. This blog walks through the warning signs, the safeguards, and what structured thinking before the build actually saves.
Apr 17, 2026
Business Cost of Shipping an AI Prototype Too Early
85% of AI projects fail to deliver ROI. Explore the hidden costs of early prototypes and how to move from demos to production-ready AI systems.
Apr 9, 2026
Building an AI-Powered Proposal Automation Engine for Presales — With Live Demo
A deep dive into how GeekyAnts built an AI-powered proposal engine that generates accurate estimates, recommends tech stacks, and creates client-ready proposals in seconds.