Bengaluru 1
PilotPilot region listed in the platform. Placement depends on enrolled worker readiness and available capacity.
Know where your application runs.
Region availability is explicit. A planned region is not an active deployment location.
Region rollout
A measured India footprint.
Mumbai 1
PlannedNot accepting workloads. No launch date is promised.
Delhi NCR 1
PlannedNot accepting workloads. No launch date is promised.
Hyderabad 1
PlannedNot accepting workloads. No launch date is promised.
Chennai 1
PlannedNot accepting workloads. No launch date is promised.
The region catalogue describes rollout state. It does not independently certify the physical location of every backend. Confirm runtime, database, object storage and backup locations for your pilot setup.
Location + dependencies
Data location needs the full picture.
Application resources
The project region guides placement. Stateful data services stay pinned to their current node; moving regions is not an automatic migration.
Object storage + backups
Storage uses a replaceable S3-compatible backend. Its configured location and backup location must be checked separately from application worker placement.
Your next applicationBuild the product.
Build the product.
Keep infrastructure from
becoming the product.
Start with one application. Add data, domains and capacity as it grows.