Digital Sovereignty · UAE data sovereignty

KamelPay migrates its core payments platform to AWS with zero payment downtime

On-premises datacenter exitZero-downtime migrationPhased cutover with parity validationPrivate connectivity & network isolationCross-region & multi-AZ replicationInfrastructure-as-code foundationData residencySQL Server replatform to managed RDSDay-2 runbooks & team enablement

downtime to live payments and regulated bank rails

Minutes

RPO/RTO — from nightly on-premises backups

Risk retired

single-data-center exposure removed with Multi-AZ failover

AWS UAE Region (me-central-1)Amazon RDS for SQL ServerAmazon VPCAWS Site-to-Site VPN

KamelPay processes cross-border remittance, corporate payroll, and payments across the MENA region — a workload whose data has to live in the UAE. VeUP migrated the platform from a single on-premises data center into the AWS UAE region (me-central-1), keeping regulated financial data in-country while replacing single-site risk with cross-AZ in-region replication, and carrying the platform’s private bank and processor connectivity into the AWS design intact.

The challenge

For a UAE fintech, the cloud question is really a sovereignty question: regulated financial data must stay in-country, connectivity to banks and processors runs over private rails that regulators and counterparties expect to remain stable, and the migration itself cannot interrupt live payments. Meanwhile the status quo carried its own risk — a single on-premises data center as the only home of a payment platform, with no second site to absorb a failure. KamelPay needed the resilience of the cloud without the data ever leaving the jurisdiction, and without a single missed payment on the way there.

The solution

VeUP anchored the design on residency-by-region: the entire platform landed in the AWS UAE region, me-central-1, so in-country residency is a property of the architecture rather than a policy promise. The core SQL Server database moved homogeneously — same engine, same schema — onto Amazon RDS for SQL Server, Multi-AZ, replicated across two Availability Zones in-region with automated failover, converting single-data-center exposure into multi-site resilience while every replica remains on UAE soil. The platform’s regulated bank and processor connectivity — IPsec site-to-site VPN and private rails — was rebuilt into the Amazon VPC design unchanged from the counterparties’ point of view, so banks saw continuity, not a migration. The cutover itself ran with zero downtime to live payment processing and bank connectivity, and KamelPay’s co-founder and CTO signed off completion.

KamelPay — Digital Sovereignty lens on the target state in the AWS UAE Region. The deployed estate re-weighted for the Digital Sovereignty designation: the UAE region boundary with core SQL Server on Amazon RDS replicating Multi-AZ in-region alongside Mongo and BI replicas, S3 object storage and backups in-region, AWS Network Firewall at the VPC edge, and the regulated rails — CBUAE, Ajman Bank and the KamelPay data centre over IPsec Site-to-Site VPN, Network International over private MPLS, office ops and HSM access over VPN — while the application tier steps back. — The sovereignty view of the same estate — residency-by-region, the regulated rails into the VPC and in-region Multi-AZ resilience foregrounded; the app tier stays in frame but de-emphasised.

Production outcomes

KPI	Result
Data residency	Regulated financial data resident in the AWS UAE region (me-central-1) end to end — sovereignty enforced by region selection and architecture, with every replica in-country.
Continuity through cutover	Zero downtime to live payment processing and bank connectivity through the migration — KamelPay’s co-founder and CTO signed off completion.
Resilience uplift	Single-data-center risk retired: the core database now runs on Amazon RDS for SQL Server, Multi-AZ, replicated across two Availability Zones in-region, with the preserved IPsec bank rails terminating into a governed VPC design.
Lessons & continuation	Sovereignty and resilience are not a trade-off once an in-country region exists — residency-by-region plus cross-AZ replication delivers both; preserving bank rails exactly as counterparties know them is what makes a regulated migration invisible to the ecosystem around it.

AWS services in production

AWS UAE Region (me-central-1)Amazon RDS for SQL Server (Multi-AZ)Amazon EC2 (application & API tier)Amazon VPCAWS Site-to-Site VPN (IPsec bank rails)AWS IAMAmazon CloudWatch