Connect your repo
Pick a GitHub repo and a branch: every push is built and released on its own. You can also upload a folder or use a Docker image.
Early access · BUE region
Olimpia runs your apps, your Postgres and Redis databases and your buckets on first-class infrastructure in Buenos Aires, connected by a private network. Manage it from the console or ask your agent to.
Obelisco
Av. 9 de Julio, 1936 · Buenos Aires
How it works
Connect your repo, add what your app needs and Olimpia takes care of the rest.
Pick a GitHub repo and a branch: every push is built and released on its own. You can also upload a folder or use a Docker image.
Postgres, Redis and buckets on the same private network as your apps. Once connected, your app gets DATABASE_URL, REDIS_URL and the S3 credentials.
Railpack detects your stack or uses your Dockerfile. The new version starts before the old one stops, and rolling back is one click.
Point a CNAME and you're done: we verify the domain, issue the certificate and serve it through Olimpia CDN.
The platform
Each product works on its own and they all talk over a private network. Start with one and add the rest when you need it.
Automatic deploys from GitHub on every push, a Docker image or your local folder. Read the guide
Infrastructure
Servers in the city, a private network per account and databases that are born closed to the internet.
Runs in Buenos Aires
The BUE region is in the city. Your data stays close to your users and your responses don't cross the continent.
Internal network
Apps and databases talk over a private network. Nothing is exposed to the internet unless you ask.
Private by default
Postgres and Redis start without public access. If you need to connect from outside, you turn it on with one click.
Backups to your S3
Schedule Postgres backups to AWS S3, Cloudflare R2, Backblaze B2, MinIO or any S3.
High availability
Every project has a copy on another server, with its image pulled and its databases replicated by streaming. If the primary server stops responding, the other one takes over on its own: it promotes the databases, starts the apps and moves the traffic.
The server stops responding and stops renewing its lease with the witness.
If it got isolated, it stops its projects so two copies never write at the same time.
The witness hands the takeover to the other server, which promotes the replicas.
Your apps start on the other server and your domains point there, without you touching anything.
The only thing that can be lost is what hadn't replicated yet, usually milliseconds. When the server comes back, it catches up on its own.
For agents
Olimpia has an MCP server. Connect your agent once and it deploys code, creates databases, reads logs and sets up domains for you, always with your permission.
claude mcp add --transport http olimpia https://api.olimpia.dev/mcpcodex mcp add olimpia --url https://api.olimpia.dev/mcpbunx skills add olimpiacloud/olimpia-skillsPricing
We measure, every minute, the CPU, memory and disk your services actually use, not what they reserve. A stopped service costs nothing. Every plan includes usage.
To try everything before deciding.
USD0once
For side projects and prototypes.
USD5per month
For products in production.
USD20per month
Databases are billed like apps: their memory, CPU and disk. Builds, certificates, custom domains, logs, metrics and the MCP are free.
Prices in US dollars, plus taxes. Included usage doesn't roll over. Set a spending limit and, if you reach it, we stop your services without deleting anything.
FAQ
Still have a question? Write to us and we will get back to you.
[email protected]Waitlist
We're onboarding the first teams. Leave your email and we'll let you know when you have access.