Buenos Aires Region
Olimpia runs in Buenos Aires. What this means for your data and your users, and how traffic reaches your apps and databases.

Olimpia was born in Buenos Aires. The first region, BUE, runs in the city: your apps, your databases, and your Redis instances live there, side by side.
Why it matters
- Close to your users. Your app and your database run in Buenos Aires, in the same country as your users in Argentina.
- App and database, together. Queries between your app and its database travel over the region’s internal network, without going out to the internet.
- Your data stays in the country. Postgres databases and Redis instances store their data in Buenos Aires.
How traffic gets in
navegador ── HTTPS ──▶ Olimpia CDN ──▶ región BUE ──▶ tu app
cliente ── TLS ──▶ proxy TCP protegido ──▶ región BUE ──▶ tu base (si es pública)
- Web and APIs. All HTTP traffic comes in through Olimpia CDN, which terminates TLS close to the user and filters attacks before they reach the region. The region’s servers only accept web traffic that comes from there.
- Databases with external access. Connections to Postgres and Redis from outside Olimpia come in through a TCP proxy with DDoS protection, which forwards them over an encrypted tunnel. The region’s address does not appear in any DNS record.
- Builds. Code is built on isolated machines, separate from where your apps run. A heavy build doesn’t take CPU away from your production workloads.
What the region includes
| Product | Status |
|---|---|
| Apps | Available |
| Postgres 18 | Available |
| Redis 8 | Available |
| S3 Buckets | Available (global storage) |
| Available | |
| CDN | Available |
| Stream | Coming soon |
Buckets use globally distributed, S3-compatible object storage, so your files are served quickly outside Argentina too.
More regions
Within the region, each project is assigned to a server (Projects). Olimpia is designed to run in multiple regions. We’ll announce new ones as they open. See Coming soon.