Blog

Map of South America built from servers with São Paulo as the main hub

From São Paulo to a Five‑City Production Mesh

Update

Brazil’s MP 1.394/2026 prohibits fixed-odds betting, including offers by overseas operators to users in Brazil. The rollout examples below focus on other application workloads. Melbicom’s São Paulo server location is coming soon and open for reservations.

For businesses that already work in Europe or North America, a South America rollout should follow local demand. A dedicated origin in Brazil can serve transactional workloads, while regional CDN caching handles public assets and reduces repeat origin requests.

Choose Melbicom

— Reserve São Paulo — coming soon

— CDN in 5 LATAM countries

— Custom configs in 3–5 business days

Learn more

Melbicom data center in Brazil

The custom-build lead time applies at active locations; São Paulo reservations are tied to the facility’s launch.

This article lays out an expansion path: plan one dedicated origin in São Paulo, then serve Buenos Aires, Santiago, Bogotá, and Lima while balancing dedicated hosting in South America with caching, routing, and data-residency requirements.

Why São Paulo Should Be Your First South American Dedicated Server Location

São Paulo is a strong first-origin candidate for a Brazil-led rollout: the city accounts for about 65% of IX.br traffic, according to NIC.br’s September 2026 report. Dense local interconnection helps shorten paths to Brazilian access networks.

Intercity delay still matters. A published October 2026 operator test averaged about 12 ms RTT from one Rio de Janeiro probe to a São Paulo server over 10 pings. Applications with tighter response-time budgets need to account for their users’ access networks and the full application path.

Melbicom is taking reservations for its planned São Paulo data center. The Brazil offer includes IX.br connectivity planning and BGP options, so you can specify local peering needs alongside CPU, storage, and port requirements.

Once you have that first node, the question shifts from “Should we be in Brazil?” to a more detailed series of questions: Where do we rely on CDN? How do we keep data compliant and routes efficient as we expand beyond São Paulo?

Dedicated Servers or CDN for Each City?

Use dedicated servers for application state and transactions that need an origin. Use CDN caching for public assets and explicitly cacheable responses. For a Brazil-first rollout, plan the origin in São Paulo and add another origin when measured application latency or data-placement requirements justify it.

Flowchart separating shared-cache responses from origin requests, with São Paulo marked as a planned origin
Cache policy and cache hits determine whether a request reaches the origin. Source: HTTP Caching.

The practical rule: dedicated hosting in South America handles write-heavy or stateful flows such as purchases, matchmaking, and Web3 transaction submission. CDN South America coverage handles media, assets, and explicitly cacheable API responses. Keep personalized account data, KYC responses, and transaction writes outside shared caches; tolerating staleness alone does not make a response safe to share.

Today Melbicom’s CDN has South American PoPs in Buenos Aires, Bogotá, Lima, Fortaleza, and Rio de Janeiro. Santiago remains a market to serve and evaluate; our current footprint does not include a CDN PoP or dedicated-server location there.

A common pattern looks like this:

  • The planned São Paulo origin handles core transactional workloads for Brazil and initially serves other markets as well.
  • CDN PoPs deliver public game assets, images, media, and cacheable snapshots, while cache misses and dynamic requests continue to the configured origin.

A PoP’s location identifies an available edge; CDN routing determines which edge actually serves a request. Compare cache-hit performance with the origin-dependent flows before deciding that another city needs dedicated capacity.

Brazil Deploy Guide

— Avoid costly mistakes

— Real RTT & backbone insights

— Architecture playbook for LATAM

Get Playbook

Melbicom website opened on a laptop

Which South American Location Should Come After São Paulo?

Choose the next South American location by user demand, origin latency, and data-placement requirements. Buenos Aires and Santiago address different Southern Cone markets; Bogotá and Lima address Colombian and Peruvian demand. Expand caching first, then evaluate another origin where dynamic requests still miss the response-time target.

A practical South America dedicated server build-out can follow four stages:

Stage Trigger Signal (Business / Ops) Recommended Move (Dedicated vs CDN)
1 – São Paulo MVP Brazilian transactions miss the response-time target, and the expected benefit justifies origin and operating costs. Plan one origin for a pilot; design redundant capacity for production. Schedule a Melbicom deployment around São Paulo’s launch and use CDN coverage for other markets.
2 – Southern Cone Expansion Material user demand in Chile or Argentina; streaming or live-ops uptake. Use Buenos Aires CDN capacity for cacheable content and assess delivery into Chile. Evaluate another origin when dynamic requests miss the product target.
3 – Andean Focus Colombian or Peruvian demand grows, and origin-dependent response times remain too high after caching. Use Bogotá and Lima PoPs for cacheable content; evaluate an available origin serving the affected market when latency or data-placement requirements justify it.
4 – Five-City Service Footprint Several markets require independent capacity or recovery arrangements. Operate the origins each workload needs, with CDN coverage across markets. Design replication and failover around those roles; serving five cities does not require five origins.

Early on, CDN coverage buys you reach and cost-effective offload. As origin-dependent latency starts to affect checkout completion, session setup, or RPC responsiveness, evaluate a city’s move from “edge-only” to “edge + dedicated origin.”

Data Residency and LGPD Transfer Rules

Logical personal-data transfers from a planned São Paulo origin to Madrid or Atlanta through the applicable transfer controls
Logical data transfers, with hosting location and packet routing treated separately. Source: ANPD Resolution 19/2024 and ANPD Resolution 32/2026.

Infrastructure decisions in South America must distinguish data residency from international transfers. Brazil’s LGPD does not impose a blanket requirement to store personal data in Brazil. Under ANPD’s transfer rules, transferring personal data abroad requires both a legal basis for processing and a valid transfer mechanism.

For many platforms, that translates into a practical playbook:

  • Choose residency per dataset. Use dedicated servers in Brazil where local performance, contracts, or applicable sector rules call for them. Include backups, logs, processors, and overseas support access in the data-flow inventory.
  • Check anonymization before exporting analytics. Under LGPD Article 12, anonymization must meet the law’s reidentification standard. Pseudonymized telemetry can still be personal data; encryption alone neither anonymizes records nor authorizes an international transfer.
  • Apply the destination’s transfer mechanism. Transfers to Madrid can use ANPD’s EU adequacy decision. Transfers to Atlanta require another valid LGPD mechanism, such as ANPD standard contractual clauses. Security, transparency, and other applicable obligations still apply.

Routing affects response time separately from data placement. Use Melbicom’s free BGP sessions on dedicated servers for route and prefix policy, and configure application destinations separately:

  • Select available regional routes. Prefer suitable routes from the received feed and compare latency and loss with alternatives.
  • Control prefix policy. Announce your prefixes and use supported communities to influence upstream routing.
  • Separate application destinations. Send permitted analytics to distinct services or endpoints in Atlanta or Madrid; BGP selects network routes, not the sensitivity of individual records.

Each network controls its own routing policy, so BGP preferences do not guarantee an in-country path or the return route. A transfer assessment must account for the organizations receiving or accessing personal data, separately from the packet path.

Who Can Design a Brazil‑First Mesh?

Choose a provider that can coordinate origin capacity, CDN caching, and routing around your release roadmap. Melbicom can combine São Paulo reservations with current South American CDN coverage and available overseas dedicated hosting. Choose additional origins by workload latency, data-placement, and operating requirements.

Using Melbicom for the origin and CDN lets your team coordinate capacity, cache policy, and routing with one provider. Size the origin for cache misses and dynamic requests, and assess those paths separately from responses served at the edge.

Key Steps to Expanding in South America (Without the Big Bang)

Planned São Paulo origin connected to selected CDN PoPs in Bogotá, Lima, and Buenos Aires
Planned cache-fill relationships between a future São Paulo origin and selected South American CDN PoPs.

Rather than lighting up five cities at once, treat South America as a rolling program with explicit decision gates. In practice, a phased plan for dedicated hosting in South America and regional caching looks like this:

  • Plan the São Paulo origin. Give yourself headroom on CPU, NVMe, and bandwidth, and align your Brazil launch with facility availability.
  • Use existing CDN coverage. Use the South American PoPs for assets and explicitly cacheable APIs. Watch hit ratios, TTFB, and rebuffering before ordering new servers.
  • Promote cities based on measured demand. Add an available origin when its response-time improvement or data-placement role justifies the added operating cost.
  • Tie procurement to milestones. Map hardware orders to concurrent users, transaction volume, and regulatory requirements, so capacity follows demand in each market.
  • Separate routing and data placement. Decide which datasets can be processed in Atlanta or Madrid and which need Brazilian storage, then evaluate routes for the application’s response-time needs.

These infrastructure decisions balance capital outlay, regulatory exposure, and performance headroom.

Your South America Dedicated Server Plan

A five-city service footprint—São Paulo, Buenos Aires, Santiago, Bogotá, and Lima—can combine an origin, CDN edges, and markets considered for later expansion. Users expect local responsiveness; regulators expect clarity on where data lives; and finance expects capacity to track revenue.

A good South America dedicated server strategy keeps three constraints in balance:

  • Latency: Keep origin-dependent traffic close to users, with São Paulo as the planned Brazilian anchor and additional origins where response times justify them.
  • Compliance: Align storage, overseas processing, and access with LGPD and local rules.
  • Capital discipline: Use CDN and routing improvements to delay additional origins until their performance or operational benefit justifies the cost.

Your footprint can evolve from one Brazilian origin into a regional architecture in which each market has a defined role. Add replication, failover, and overseas dependencies where the application needs them.

 

Plan your Brazil‑first server rollout

Share your Brazil launch requirements, traffic profile, and preferred hardware so we can plan São Paulo reservations alongside current CDN coverage and available overseas origins.

Get servers

 

Back to the blog

Get expert support with your services

Phone, email, or Telegram: our engineers are available 24/7 to keep your workloads online.




    This site is protected by reCAPTCHA and the Google
    Privacy Policy and
    Terms of Service apply.