Oracle ULA certification that fixes the right number for the next decade. We build the deployment count on your side, test certify against renew, draft the declaration, and negotiate what comes after.
Redress Compliance provides Oracle ULA certification support for enterprises approaching the end of an Unlimited License Agreement. We are 100 percent buyer side and led by former vendor insiders. For a fixed fee we build an independent deployment count, test certify against renew, and file a declaration you can defend.
The Certification Window
Session 9 of the Oracle ULA Series. The 30 to 90 days that fix your position for the next decade: what you submit, what Oracle checks, what evidence holds, and the mistakes that shrink a count on the last day.
Start the certification baseline twelve to eighteen months before the ULA term ends. Our 2026 ULA analysis recommends eighteen months, because the certified number becomes your permanent entitlement and cannot be revised later.
Certification is the declaration of deployed quantity at the end of a ULA, and that number becomes your permanent entitlement. Most ULA contracts give roughly 30 days after term end to file a signed declaration, so the counting must be finished before the window opens.
Under counting hands back licenses you already paid for: first pass internal counts in our file missed 10 to 25 percent of eligible deployment. Over counting costs too, because support is billed on every certified unit for as long as you hold it.
The right target is complete, not inflated. Certify everything genuinely deployed, and nothing that is merely exposed in theory by a cluster boundary.
Our ULA work from 2024 to 2026 points to four facts every ULA holder should know before the next certification or renewal.
Read our Oracle ULA guide for 2026 for the counting rules, and when to hire an Oracle licensing consultant for the timing of outside help.
Four phases, starting with the count and ending with the commercial terms that follow certification. A fixed fee cycle typically runs twelve to eighteen weeks and is best started twelve months before certification.
Fredrik Filipsson, co founder and Group CEO of Redress Compliance, leads our Oracle practice and our ULA certification work. The counting and evidence work is run by our Oracle licensing consultants.
Fredrik Filipsson co founded Redress Compliance and serves as Group CEO. Before founding the firm he held roles at Oracle, IBM, and SAP, and today he leads our Oracle practice and the most complex multi vendor engagements. He is the author of widely cited Oracle Java and ULA negotiation playbooks.
Read Fredrik Filipsson's profile or meet the wider Redress management team.
A defended count shows up in the numbers. Every figure below is taken from the linked case study.
More outcomes sit in our 281 published case studies.
Because Oracle routinely offers its own licensing team's help at certification, and the number you file is the number you keep. The buyer side move is to run your own count and control your own data.
We are 100 percent buyer side: zero vendor affiliations, no reseller agreements and no referral fees. Our fee is fixed, so it is the same whether you certify or renew, and if an audit follows the exit our Oracle audit defense team works from the same evidence.
ULA certification is a fixed fee engagement, quoted on estate size and agreed before we start. We never bill by the hour.
If you decide to renew, our Oracle contract negotiation work can run on a fixed fee or a success fee (gainshare) of 25 percent of what we save you. You keep 75 percent, and if we save nothing you pay nothing.
It is a fixed fee, quoted on estate size and agreed before we start, and we never bill by the hour. If you decide to renew instead, that negotiation can run on a fixed fee or a success fee of 25 percent of what we save you.
Twelve to eighteen months before the term ends. Most ULA contracts allow roughly 30 days after term end to file the signed declaration, so the count has to be finished before that window opens.
A fixed fee certification cycle typically runs twelve to eighteen weeks of active work, and it is best started twelve months before certification. Starting earlier leaves room to fix deployment records before the count is filed.
Let the deployment trend decide, not the renewal quote. Renewal tends to win while Oracle deployment is still growing, and certification tends to win once it has plateaued, which in our file happened 12 to 24 months before expiry in most estates.
Only deployments of products inside the ULA scope, on the entities and platforms your agreement covers. Cloud deployments may or may not count depending on how the agreement is written, and virtualized hosts are where most counting disputes arise.
Oracle routinely offers its licensing team's help with the count, and often proposes a renewal before your own count is complete. The buyer side move is to run your own count, control your own data, and hold any renewal decision until the count is finished.
Yes. Redress Compliance is 100 percent buyer side, with zero vendor affiliations, no reseller agreements and no referral fees. Our certification fee is fixed, so it is the same whether you certify or renew.
Your ULA agreement and ordering documents, the asset register, virtualization and cloud inventories, and access to the teams that run Oracle workloads. We build the deployment evidence file from these sources.
ULA exit on the desk, certification window open, or a renewal proposal tabled. We start where you are.
One letter a month. Negotiation moves, audit signals, and price book shifts.