×
Startup Support Program
Free AWS Credits · Dedicated Cloud Architect · Limited Seats
Trusted Digital Transformation Partner
Oracle licensing advisory is the work of establishing what an organisation is actually entitled to use, what it is actually using, and the gap between the two — across Oracle Database and its options, E-Business Suite and Fusion applications, Java SE, and licences carried into cloud under BYOL. It matters most at three moments: before a renewal, before a cloud migration, and the day an audit letter arrives. ROSTAN is an Oracle Gold Partner; we review your deployment against your entitlements and tell you where you stand, in writing. We are consultants, not lawyers — where a position needs legal or formal negotiation support, we will say so rather than improvise.
This is the single most expensive misunderstanding in Oracle licensing right now, and it is not a rumour — it is Oracle's own published model.
Oracle describes the Java SE Universal Subscription as “simple, per-employee pricing” that “eliminates issues of precisely accounting for JDK instances in bare metal, virtualized, and containerized servers across desktops, on-premises, and in clouds.”
Read that carefully. The reason it removes the need to count installations is that it does not count installations at all — it counts people.
Oracle — Java SE Universal SubscriptionUnder the old per-processor and Named User Plus metrics, you licensed what ran Java. Under a per-employee metric, the exposure is driven by organisation size.
A company of 2,000 staff with Java on 30 servers is not priced on the 30 servers. That is why bills rose sharply for organisations whose actual Java estate had not grown at all — and why a single forgotten JDK on a test box is worth finding before someone else finds it.
These are the areas where the gap between entitlement and deployment usually opens.
Per-employee subscription exposure, forgotten JDKs on servers and desktops, and whether an OpenJDK or alternative runtime is a viable route for part of your estate.
Processor vs Named User Plus, core factor tables, and the options that are easy to enable and easy to forget — Partitioning, Diagnostics and Tuning Packs, Advanced Security.
How your hypervisor affects what Oracle considers licensable. This is where the largest and most contested audit findings usually come from.
Unlimited Licence Agreements, what certification actually requires, and reviewing renewal terms before signature rather than after.
What your existing licences entitle you to in OCI, AWS or Azure, and how a migration changes your position — the point at which many organisations quietly fall out of compliance.
E-Business Suite and Fusion user counting, module entitlements, and read-only or self-service access that is often assumed to be free and is not.
The output is a written position: what you hold, what you are running, and where the two do not meet — with the assumptions stated, so you can challenge them.
Best done before a renewal date or a cloud migration. After an audit notice the same work still helps, but your options are narrower.
Collect the ordering documents, support renewals and any ULA. What you are entitled to is a contractual question, not a technical one — it starts with paper.
Establish what is actually installed and running: databases and enabled options, application users by responsibility, and every JDK we can find.
Compare the two. Quantify the exposure, and just as importantly the over-licensing — organisations are often paying for things they stopped using years ago.
Practical routes: remove or disable what is not needed, re-architect where virtualisation is driving the count, or buy — with the cost of each stated plainly.
Licensing attracts a lot of confident advice. Here is where ours stops.
Tell us which Oracle products you run and when your next renewal falls. We will come back with what a licence position review would cover for you — and whether you need one at all.
Powered by AI · Typically replies instantly