A large share of South African banks, insurers, and government runs on Oracle — the database, the apps, decades of it. The modernisation question is almost never "migrate off"; it's "how do I get modern interfaces and agent access onto systems I'm not going to rewrite, and keep it in-country?" This hub answers that as a stack: the app layer (APEX), the REST-and-agent seam (ORDS), the converged system of record (Oracle AI Database 26ai), and where it can legally run (OCI Johannesburg). Read as an integration map, not a product catalogue.
Each card maps to a leaf in tech/oracle/*. The through-line is the same at every layer: the database stays the system of record, and everything modern is a seam over it — not a migration off it.
The converged system of record — relational, JSON, and now AI Vector Search and in-database machine learning in one engine. The case for keeping the data (and the vectors) where the records already live, rather than shipping them to a separate vector store.
The genuinely old estate — E-Business Suite, Oracle Forms & Reports, PeopleSoft, JD Edwards — and the honest options for getting modern UIs and agent access onto them without a decade-long re-platform.
The one idea that holds the whole hub together: an Oracle estate does not have to be migrated to be modernised. APEX puts a modern UI on the database; ORDS puts a REST and MCP surface over it; 26ai adds AI inside it; OCI decides where it sits. At no point does the system of record move. For an architect, that reframes a multi-year migration business case into an integration one — and for an SA architect, it keeps residency answerable, because the app layer sits wherever the database sits.
The vendor register around Oracle's AI features is heavy, and it's tempting to read every release as a reason to re-platform. The practitioner reality is quieter and more useful: these are seams you add to what you already run. The value is real precisely because it doesn't require the rewrite — and the honest read on each leaf is where the seams cost you (whole-application import in APEX, no PATCH in ORDS, lock-in in OCI). Read the leaves for the seam and the catch, not the headline.
Oracle sits in tech/ alongside the other enterprise-platform and integration entries. The agent seam is the reason it connects outward — ORDS and APEXlang are how an Oracle estate joins the agent stack the rest of the tree describes.