DEV Community

Ejaz Arain
Ejaz Arain

Posted on Originally published at tech-style-co.blogspot.com AI-assisted

Leaving Oracle: the licence is the easy part

First published on the Tech Style blog.

Philip Marks wrote recently about the UK public sector and Oracle. A first look at procurement records, he said, found more than £7 million of Oracle Database related contract awards in 2026 alone, and that is only the contracts he could identify. His question was a fair one: how long can tight budgets keep paying for renewals when PostgreSQL has no licence fee at all?

We agree with the direction. But in our experience the licence is the easy part of leaving. Here is where the lock-in really sits, and why we started building Paritas.

Where the lock-in sits

The contract. Licences are usually priced by processor, with options and packs on top, and support renews every year as a share of what you paid. Move to new hardware or to a cloud and the licensing rules come with you. Every renewal is a negotiation you cannot walk away from, because the alternative is not ready.

The code. This is the big one. A long-lived Oracle estate holds years of PL/SQL: packages, triggers, collections, exception handlers, calls into DBMS_ and UTL_ packages that applications lean on without anyone remembering why. Nobody wants to rewrite it, and nobody can afford to stop the business while they do.

The behaviour. Even code that converts cleanly can answer differently. On Oracle, SELECT 1 UNION SELECT 2 INTERSECT SELECT 2 returns 2. On PostgreSQL it returns 1 and 2, because INTERSECT binds tighter there. A FOR i IN REVERSE 1 .. 3 loop runs three times on Oracle and not at all on PostgreSQL. An empty string is NULL on Oracle and a value on PostgreSQL. None of these raises an error. They turn up later as wrong numbers.

The people. As Philip says, finding people who can migrate, architect and support a PostgreSQL estate is as hard as the technology. A team that has spent fifteen years in PL/SQL is an asset, and a migration that throws their knowledge away is a risk.

Put together, this is why so many estates stay put. Not loyalty, and not the licence. The cost of being sure the new system gives the same answers.

What we are building

Paritas is an Oracle-compatible database built on PostgreSQL. It runs in Oracle mode only, so your applications talk to it as they would to Oracle and real PL/SQL compiles and runs. Underneath, it is PostgreSQL, with PostgreSQL's tools, drivers and extensions, and no proprietary format to be locked into next.

We do not claim it is a perfect copy of Oracle. Nobody honestly can. Our promise is narrower and, we think, more useful: we can tell you exactly where compatibility ends for your own code, with measured evidence. Every answer Paritas gives is checked against a real Oracle Database 21c. Where it differs, it goes on our list of limitations, which runs to more than 900 entries, each saying what happens and most saying what to do instead.

Around Paritas we are building the tools a migration needs. pgrecon, our free assessment tool, is out today: it reads an Oracle schema and tells you what it contains before a migration is priced. Development tools and connectivity drivers are coming, and none of them is available yet. The enterprise layers we are working on power the PostgreSQL underneath Paritas, and they are being built so they can power plain PostgreSQL as well.

Leaving on your own terms

The way out of lock-in is not a leap. It is knowing, before you commit, which of your code will behave the same, which will not, and what each difference costs to fix. That turns a renewal from a hostage negotiation into a choice.

Paritas is in development and not for sale yet. We are aiming to release it next quarter. If you are weighing a move off Oracle, read more at tech-style.co/product-paritas, try pgrecon at tech-style.co/product-pgrecon, or write to us at tech-style.co/contact?topic=Paritas.

Top comments (0)