Sovereign Cloud
The question isn't how many services a catalog has. It's where your data lives, who operates it, and who you sign with.
IPXON is infrastructure operated from inside Latin America. You choose the country for each service, you talk to the engineers who run it in your own time zone, and you contract with an entity in the region. Everything this solution is built from can be contracted today.
The reframe
A bigger catalog answers a different question
A hyperscaler has more managed services than we do, and it will keep having them. That comparison is settled and not worth arguing. The one that decides a regulated workload is a different question, answered by architecture and by who sits on the other side of the contract.
Control points
Four things you decide, service by service
Sovereignty isn't a checkbox: it's the sum of concrete decisions about where the workload runs, who can touch it and how it travels. These four are already built into how the services work.
Residency is chosen per service, not inherited from a region
Every instance, every server and every volume is pinned to the PoP you choose, so you decide service by service which country processes and stores the data. A File Storage volume is mounted only from servers in its own PoP: if you operate in several countries, each keeps its own data with no implicit cross-replication.
The operator is in your jurisdiction and your time zone
Network engineers and on-site smart-hands technicians, in the same country or region as your team. 24/7/365 technical support for critical incidents. Operational requests. Escalating a physical incident never routes through a support center on another continent. IPXON operates legal entities and issues local invoices in countries across the region, so the commercial relationship is settled where you operate too.
Dedicated when it matters: the workload's boundary has a name
Edge Bare-Metal delivers single-tenant physical hardware (no hypervisor in the path, with CPU, memory and PCIe bandwidth dedicated exclusively to your workload), and Colocation racks the equipment that is already yours without changing owner. When someone in risk asks which machine runs that workload, there is a concrete answer instead of an abstraction.
The private path between your sites is yours
Private Connect extends your own L2 or L3 network across sites, data centers and PoPs with no Internet in the path, and Cloud Connect reaches what already runs in a public cloud over a dedicated port rather than an exposed endpoint. The private circuit and your Internet egress ride separate logical planes: contracted capacity stays reserved.
Due diligence
Questions your risk team has to be able to answer
We don't issue legal opinions about your workload (that's your counsel's job), but the architecture has to let you answer with verifiable facts instead of a region label.
What city and country is this service running in?
The PoP is chosen at contract time and stays pinned to the service. You can name the location of every instance, every server and every volume instead of inferring it from a regional label.
Who can physically touch the equipment?
In Colocation, site access is by named authorization with escort, and every intervention we perform on your equipment is logged. The hardware and the disks remain yours.
Does this traffic go out to the public Internet?
Between your sites and our PoPs, no: the private circuit and Internet transit ride the same fiber on separate logical planes, and the circuit's bandwidth never competes with public traffic.
Which entity do we contract with, and who issues the invoice?
IPXON operates legal entities and issues local invoices with in-country tax identifiers across markets in the region, among them Colombia, Mexico and Peru. Country-by-country scope is confirmed by our commercial team before signing.
What standards apply at the site where the workload runs?
There are PoPs in Tier III facilities and locations with a PCI-DSS Ready environment. Scope depends on PoP location, the contracted plan and the jurisdiction, and is confirmed with our team before you deploy a regulated workload.
Who controls the image and operating system in production?
You do. Upload and mount your own ISO from the PRESENCE® platform or over remote IPMI, with out-of-band access to the server, so the software running on the hardware is defined by your team and not by a closed image catalog.
Certifications and controls apply according to PoP location, the contracted plan and the jurisdiction. Check scope and availability with our team, and the regulatory reading of your workload with your own counsel.
Coverage
These are the markets you choose from
- Brazil3 PoPs
- Mexico3 PoPs
- Argentina2 PoPs
- United States2 PoPs
- Chile1 PoP
- Colombia1 PoP
- Ecuador1 PoP
- El Salvador1 PoP
- Guatemala1 PoP
- Panama1 PoP
- Paraguay1 PoP
- Peru1 PoP
- Uruguay1 PoP
Every service is pinned to the PoP you choose, and data residency is decided right there. Availability of a specific service can vary by location: the configurator shows what is enabled in each PoP and our engineering team confirms the rest while shaping the topology.
What it's built from
Built from services you can contract today
Sovereign Cloud isn't a SKU: it's a way of combining the catalog. These are the pieces, each with its own page, its own sizing and its own path to contract.
Where the workload runs
Single-tenant dedicated hardware or elastic instances, pinned to the PoP you choose.
- Edge Bare-Metal
100% dedicated, no noisy neighbors.
Configure - Virtual Machines
Elastic KVM-based instances.
Configure
How it travels
Private circuits between your sites, to the public clouds, to the IXPs and out to the Internet.
- Private Connect
Private circuits between your sites and our PoPs.
Request quote - Cloud Connect
Private interconnection to the public clouds.
Request quote - IP Transit
Multihomed corporate transit with automatic bursts.
Request quote
Where the data lives
Shared volumes in the same PoP as the servers that mount them.
- File Storage
Shared storage for your servers.
Request quote
Your own hardware, in-region
Space, power, on-site hands and interconnection for equipment that is already yours.
- Colocation & Remote Hands
Dedicated space with high-speed cloud interconnection.
Request quote
The specific topology (which service in which PoP, and with what interconnection) is defined with our engineers from your markets and your internal requirements.
See every serviceBring us the workload that can't leave the country
Tell us what has to stay inside a jurisdiction, which markets you operate in, and what your risk team measures it against. Our engineers shape the topology from the pieces that exist today, and tell you just as plainly what it solves and what it doesn't.