A cloud service provider (CSP) is a company that rents out computing power, storage, networking and applications over the internet and charges for what you consume, instead of selling you hardware. Five global providers now run their own regions inside Mexico: Amazon Web Services, Microsoft Azure, Google Cloud, Oracle Cloud and Huawei Cloud, alongside Mexican providers such as KIO and Telmex Triara.
The decision changed between 2024 and 2025. Four of those providers opened regions in Querétaro, so a company operating in Mexico can now run its systems in the cloud without its data leaving the country. In this guide we compare the eight leading providers and explain how to choose between them and how to contract them.
What a cloud service provider does
The provider builds and operates data centers with thousands of servers and makes that capacity available to its customers through an online console. The company that signs up chooses how many servers it needs, how much storage and which services, and pays a monthly bill for what it uses. If it needs more, it turns it on in minutes; if it needs less, it shuts it off and stops paying.
What you contract can range from raw infrastructure to finished software. Those three levels are known as IaaS, PaaS and SaaS, and almost every company ends up using all three at once: servers for its ERP, a managed database and email by subscription.
Not all providers are the same kind. It helps to tell three types apart:
Hyperscalers. The global giants with regions in dozens of countries: AWS, Microsoft Azure, Google Cloud, Oracle and Huawei. They have the broadest catalog, the most competitive price per unit and a huge partner ecosystem.
Mexican national clouds. Mexican companies that operate their own data centers and offer private cloud or managed services on top of them, such as KIO or Telmex Triara. Their advantage is proximity: contracts in pesos, local support and data that has always stayed in Mexico.
Private cloud and colocation. The provider delivers a cloud dedicated to a single company, or rents it space, power and connectivity so it can install its own equipment there. It is the option for anyone with applications that can't move to a shared cloud.
Which model fits each case depends on how much of the stack your team wants to manage itself.
The 8 cloud providers operating in Mexico
The table summarizes where each provider has infrastructure inside the country, what it stands out for and what kind of company it usually suits best. Region and date information comes from each provider's official announcements.
| Provider | Region in Mexico | Main strength | Best for |
|---|---|---|---|
| Amazon Web Services (AWS) | Querétaro, three availability zones, since January 2025. | The broadest service catalog and the largest developer community. | Companies with their own development teams or custom-built applications. |
| Microsoft Azure | Mexico Central region in Querétaro, since May 2024. | Native integration with Microsoft 365, Windows Server and Active Directory. | Companies already built around the Microsoft ecosystem that want to move their servers. |
| Google Cloud | Querétaro, three zones, since December 2024. | Data analytics, artificial intelligence and Google Workspace. | Companies with data projects or that use Workspace as their office suite. |
| Oracle Cloud | Querétaro (2022) and Monterrey (2023), in partnership with Telmex Triara. | Oracle databases and the same vendor's enterprise applications. | Companies already running Oracle ERP or databases. |
| Huawei Cloud | Two regions with three zones, in data centers in the State of Mexico and Mexico City. | Aggressive pricing and a local presence with Spanish-language support. | Companies looking for a lower-cost alternative to the big three. |
| IBM Cloud | No region in Mexico; the closest are in Dallas and São Paulo. | Services for large enterprises with legacy systems. | Enterprises with global IBM contracts. |
| KIO | Data centers in Santa Fe, Querétaro, Monterrey, Hermosillo and Mérida, among others. | Private cloud, colocation and managed services on top of the global clouds. | Regulated companies that need dedicated infrastructure inside the country. |
| Telmex Triara | Data centers in Querétaro and Monterrey. | Private cloud on VMware and connectivity over its own fiber network. | Companies that want cloud and network links from a single Mexican provider. |
Between the two providers companies in Mexico contract most, Azure and AWS, the choice almost always comes down to what they already use: Microsoft 365 and Windows servers point toward Azure, while custom development often points toward AWS.
What changed in 2024 and 2025: the Querétaro regions
Until 2023, a company in Mexico that signed up for AWS, Azure or Google Cloud had its servers in the United States or Brazil. In less than two years that flipped:
- May 2024: Microsoft launches its Mexico Central region in Querétaro for Azure, Microsoft 365 and Dynamics 365.
- December 2024: Google Cloud opens its Querétaro region, its third in Latin America after Santiago and São Paulo.
- January 2025: AWS opens its Mexico (Central) region, also in Querétaro, with three availability zones and a planned investment of more than 5 billion US dollars over 15 years.
- Earlier, in 2022 and 2023: Oracle had already opened Querétaro and Monterrey with Telmex Triara, and Huawei Cloud added its second region in the country.
For a business this translates into three things. Data residency: information stays inside Mexico, something more and more corporate customers and regulators ask for. Latency: a system that responds from Querétaro takes a fraction of the time it took from Virginia, and you notice it in an ERP or a virtual desktop. Availability: three separate zones in the same region let an application keep running even if an entire data center fails.
That last advantage only exists if the architecture accounts for it. Having a region nearby doesn't replace a disaster recovery plan: someone has to decide what gets replicated, where to, and how quickly it must be back up and running.
How to choose a cloud provider: 7 criteria
All eight providers in the table work. The real question is which one works for your company, and these criteria answer it in order of importance:
- Where your data will live. If your industry, your customers or your contracts require information to stay in Mexico, rule out any provider without a region in the country from the start.
- What you already use. A company with Microsoft 365 and Windows servers has the shortest path in Azure; one with Oracle databases, in Oracle Cloud; one with in-house development, in AWS or Google Cloud.
- The full cost, not the list price. Ask for an estimate based on your real workloads that includes outbound data transfer, IP addresses, licenses and the support plan. The three charges that surprise people most on the bill don't show up in the calculator.
- Support in your language, backed by contract. Check which languages and hours the provider covers and what response times it commits to in writing. The basic support plan from the hyperscalers is often just documentation and forums.
- Certifications and responsibilities. ISO 27001, ISO 27017 and 27018 for cloud, and PCI DSS if you process card payments. And something many companies discover late: the provider protects the infrastructure, but configuration, access and backups are the customer's responsibility. It pays to understand how a cloud backup works before you sign.
- An exit without penalties. Ask how much it costs and how long it takes to get your data out if you decide to switch. A provider that answers with numbers is one you can negotiate with.
- Who will run it. Signing up for the cloud takes an afternoon; keeping it healthy and the bill under control is daily work. Decide whether your team, a partner or a managed service will handle it.
Why the cloud bill surprises people
Companies that end up disappointed with the cloud rarely chose the wrong provider: they started from assumptions that the bill disproves three months later.
"The cloud is always cheaper than our own server." It's cheaper when the workload varies and you shut down what you don't use. A server running at 100% around the clock can cost more in the cloud than in your office; what you gain there is availability and not having to buy the next one.
"I only pay for what I use." You pay for what is switched on, which is a different thing. Disks from servers that no longer exist, reserved IP addresses and test environments nobody turned off are the ghost resources that weigh the most.
"The list price is the final price." Compute and storage are the visible part. Outbound data transfer, backups, the support plan and licenses are billed separately and can add up to a third of the total.
"The provider's calculator is enough." The calculator reflects whatever you tell it; if you give it the size of your current server, it will quote a server that is probably oversized. Sizing on real consumption and reserving instances for what really runs all the time usually brings the bill down considerably.
Direct, through a partner or managed: how to contract the cloud
Choosing a provider is half the decision. The other half is how you contract it and who answers afterward, and there are three ways to do it:
| Direct with the provider | Through a partner | Managed cloud | |
|---|---|---|---|
| Who opens the account | Your company, with a card or a contract. | The partner, or your company with the partner as reseller. | The service provider, or it takes over the account you already have. |
| Who runs the console | Your IT team. | Your team, with occasional advice. | An external team, with your company as the account owner. |
| Support | The plan you buy from the provider; basic tiers are mostly self-service. | The partner escalates to the vendor. | An assigned engineer, contractual response times and escalation to the vendor. |
| Cost | Consumption only. | Consumption, sometimes discounted, plus projects. | Consumption plus a monthly operations fee. |
| Who it suits | Companies with cloud specialists on staff. | Companies that need to migrate and then run things on their own. | Companies that don't want to train or retain cloud specialists. |
The third option is the one that has grown the most, because it settles criterion number seven: who runs it.
A managed cloud service means that a dedicated team runs your cloud every day: console, monitoring, incidents with contractual response times and control of consumption, while your company remains the account owner. That's how we work in our managed cloud services on Azure, AWS or both, with a Level 2 engineer, support in English and Spanish, and escalation to the vendor.
Frequently asked questions about cloud service providers
CSP stands for cloud service provider. It refers to any company that rents out computing, storage or applications over the internet and charges by consumption, from global players such as AWS or Azure to Mexican providers such as KIO.
No single provider is best for everyone. If the company already uses Microsoft 365 and Windows servers, Azure is the shortest path; if it has in-house development or data projects, AWS or Google Cloud; if it runs Oracle, Oracle Cloud; and if its regulations require dedicated infrastructure, a Mexican provider. All five global providers now have a region in Mexico, so data residency is no longer the deciding factor.
Mexico's data protection law doesn't require it to stay in the country, but it does make you responsible for how your provider handles it and for agreeing on that in your contract. Some regulated industries, such as financial services, have their own rules for contracting cloud services. With the Querétaro regions, keeping data in Mexico no longer costs more.
The cloud provider supplies the infrastructure and charges for consumption; the managed service supplies the team that runs that infrastructure for you: console, monitoring, costs and support. That's how our managed cloud services work, on Azure, on AWS or on both.
Yes, and it's common: for example, email and desktops in Azure and an in-house application in AWS. The condition is that someone manages both with the same rules for access, backup and cost control, because each console is different and mistakes multiply.
There is no fixed price: you pay for the compute, storage and data transfer you consume each month, plus support and licenses. The only way to know before you sign is an estimate based on the real consumption of your current servers.