OCI Migration — Benoît Sigwald

Why, and how

The goal: centralize everything on one free server, without giving up the developer experience of Vercel or Render.

1 · Foundation

Ubuntu 24.04 on an OCI Ampere A1 (ARM64). Two firewall layers — OCI Security List + instance iptables — DuckDNS subdomains with a cron-based IP updater.

2 · The platform

Coolify as a self-hosted PaaS: builds from GitHub, deploys Docker containers, manages env vars and cron. Traefik terminates HTTPS with automatic Let's Encrypt certificates.

3 · The workloads

MCP servers, web services and API servers, each in its own container, routed by hostname and path. Test and prod environments, deployed by git push (Coolify webhook).

4 · The data

Self-hosted PostgreSQL/PostgREST (same API syntax as Supabase — zero code change) plus an Oracle DB. 500+ rows migrated with full-text search intact; automated backups to OCI Object Storage.

Architecture diagrams

The complete picture, from migration flow to service layer.

Migration overview

What moved from where: Vercel, Render, Supabase and local workloads consolidated onto the OCI server.

Infrastructure architecture

Internet traffic crosses two firewall layers, reaches Traefik which terminates TLS, and is routed to the right container. Coolify builds from GitHub and manages the lifecycle.

Component data flow

How requests, builds and data move between the proxy, the applications, the databases and object storage.

PaaS service layer

The Coolify control plane: builds, deployments, environment variables, scheduled tasks.

PaaS details

A closer look at the platform internals and how each hosted service fits in.

Platform services, one by one

The building blocks behind every deployed app: the deployment plane, the data layer, object storage and backups.

Coolify — deployment plane

Builds from GitHub on every push, deploys Docker containers, manages environment variables and scheduled jobs — all driven through its REST API.

Data layer — PostgreSQL + PostgREST + Oracle DB

A self-hosted, Supabase-compatible data API with French full-text search, alongside an Oracle database. 500+ rows migrated with zero loss.

MinIO — S3-compatible object storage

Self-hosted S3-style storage for application assets and files, behind Traefik like every other service.

Backups — automated, off-container

Scheduled database and volume backups shipped to OCI Object Storage (10 GB free tier), tested by restore before any cutover.

The stack

Component	Role
OCI Ampere A1 (ARM64)	4 OCPU, 24 GB RAM, Ubuntu 24.04 — Oracle free tier
Docker Engine	Runtime for every workload
Coolify	Self-hosted PaaS: build, deploy, env, cron, REST API
Traefik	Reverse proxy, automatic Let's Encrypt HTTPS, host/path routing
PostgreSQL + PostgREST	Self-hosted Supabase-compatible data API, French full-text search
MinIO	S3-compatible object storage
OCI Object Storage	Automated off-container backups, disaster-recovery restore tested
DuckDNS	Free DNS with cron-based IP updates

Migration phases

Cutover strategy: the old host stays live in parallel until the target is validated — no deletion before production validation, backups tested before final cutover.

Phase	Scope	Status
0	Foundation — Docker, 2-layer firewall, DNS + cron	✅ Done
1	Coolify platform + admin + REST API	✅ Done
2	First app migrated from local (Node)	✅ Done
3	Einstein MCP server migrated from Vercel	✅ Done
4	Render services + scheduled jobs	⏳ In progress
5	Postgres self-hosting + backups, off Supabase	✅ Done
6	Ollama — small ARM-quantized models (optional)	⏳ Planned