When an Oracle Java review begins, the contact frequently comes not from your familiar sales account team but from a different group: Oracle Global Licensing and Advisory Services, usually abbreviated to GLAS. To anyone facing it for the first time, GLAS can be confusing — it presents as helpful and advisory, yet it is the engine of Oracle's compliance activity. Understanding what GLAS is, how it operates, and how it differs from sales is essential to responding well.
This guide explains the function, its role in Java licensing specifically, and how to handle contact from it.
What GLAS is
Oracle Global Licensing and Advisory Services is the internal Oracle organisation responsible for licence verification — in plain terms, the audit and compliance function. It is the team that conducts formal audits under the audit clause of an Oracle agreement, and it is increasingly the team that drives the informal "reviews" of Java SE usage that precede them.
The "advisory" in the name is worth pausing on. GLAS frames much of its work as helping customers understand and correct their licensing position. The framing is genuine in the sense that GLAS will indeed explain where it believes you are non-compliant. But it is Oracle's compliance arm, its purpose is to convert unlicensed usage into Oracle revenue, and its advice is given from Oracle's side of the table — never your own.
GLAS may use the language of guidance and partnership. It is still Oracle's compliance function. Treat its communications as the opening of a commercial process, not as neutral help.
GLAS versus the sales team
One of the most useful distinctions to grasp is the difference between GLAS and your Oracle sales account team. They are separate functions with different incentives, and Java reviews often involve both.
| Aspect | Oracle Sales | Oracle GLAS |
|---|---|---|
| Primary goal | Sell subscriptions and new products | Verify licensing; recover unlicensed use |
| Tone | Relationship, opportunity | Review, compliance, entitlement |
| Typical contact | Quotes, renewals, roadmap | Usage "reviews," data requests, audits |
| Leverage used | Discounts, incentives | Contractual audit rights, claim size |
| Where Java sits | Universal Subscription proposals | Detection, claim build, settlement |
In a Java situation the two often work in tandem: GLAS establishes a compliance gap, and sales presents the subscription that "resolves" it. Recognising which function you are speaking to, and what each one wants, helps you avoid being moved between them in a way that always points toward a purchase.
GLAS and Java SE specifically
Java has become a major focus for GLAS since Oracle moved Java SE to a paid subscription and, in 2023, to the per-employee Universal Subscription. The combination of a large installed base, a metric tied to total headcount, and rich download data makes Java a high-yield area for compliance activity.
In a Java engagement, GLAS typically: assembles a usage picture from download records and detection data; requests that you run Oracle's scripts or complete a questionnaire; reconciles the results into a claimed quantity of unlicensed Java; and presents a figure — almost always at list price — alongside the subscription that would resolve it. The mechanics of that figure are covered in our guide to how Oracle calculates a Java audit claim.
Soft reviews and formal audits
GLAS-driven Java contact comes in two forms, and telling them apart matters.
The soft review
Most Java contact begins as a soft review — an informal approach inviting you to "discuss" or "review" your Java usage. It does not cite the audit clause. It is collaborative in tone. It is, nonetheless, GLAS doing its job: gathering the information that becomes a claim. Data volunteered in a soft review is not off the record.
The formal audit
A formal audit explicitly invokes the audit or verification clause of your Oracle contract. It carries defined obligations on both sides — but also defined limits. The contract constrains what GLAS can demand, how much notice it must give, and the scope it can examine. Those limits are a defensive asset, and reading the clause carefully is part of any sound response.
How to handle GLAS contact
Whether the approach is soft or formal, the principles for dealing with GLAS are consistent:
- Acknowledge, do not improvise. A brief, professional acknowledgement is appropriate. Detailed answers about your Java estate are not — not until you have verified your own position.
- Route through one contact. All communication with GLAS should flow through a single named person. Multiple staff replying separately creates inconsistencies GLAS can use.
- Build your own inventory first. Produce a verified Java inventory using your own tools before discussing usage. See our self-assessment template.
- Be cautious with Oracle's scripts. GLAS data-collection tooling produces the evidence behind the claim. You are entitled to validate and present your own data first.
- Know the contract. If a formal audit clause is invoked, the clause defines GLAS's limits as much as its rights. Read it with legal input.
- Engage independent advice early. GLAS runs these processes constantly; your team likely does not. An independent advisor closes that experience gap.
The "advisory" framing, and why it matters
It is worth returning to the word "advisory," because it is where many organisations are most easily disarmed. GLAS will often present itself as wanting to help you get correctly licensed, to "clean things up," to make the problem go away. That framing encourages cooperation, openness, and speed — all of which serve Oracle.
None of this means GLAS is acting in bad faith. It means GLAS's advice is Oracle's advice. When GLAS suggests that a particular subscription is the simplest resolution, that may be true for Oracle; it is not necessarily the best outcome for you. There may be a smaller genuine exposure than GLAS asserts, a better metric, a shorter back-dated period, or a migration path that removes the issue entirely. GLAS has no incentive to surface those. Your own advisor does.
GLAS advises Oracle. You need someone advising you. The asymmetry is not unfair — it is simply how the process is built. The remedy is to bring your own specialist to the table.
Why independence matters here
When choosing who advises you against GLAS, independence is decisive. An advisor that holds an Oracle partnership, resells Oracle licences, or earns margin on Oracle subscriptions has a quiet incentive aligned with GLAS's outcome, not yours. Genuinely independent, buyer-side advisory removes that conflict: the only thing it sells is a better result for you.
This is also where a money-back guarantee earns its place. An advisor confident enough to refund its fees if it cannot reduce your claim is putting its revenue behind its work. Across our engagements that confidence is borne out — an average 68% reduction on opening Java claims and more than $180M in client savings.
Conclusion
Oracle GLAS is the compliance and audit function behind most Java licensing reviews. It is professional, it is well-resourced, and despite the "advisory" name, it represents Oracle. Contact from GLAS — soft or formal — is the start of a commercial process whose default destination is an Oracle purchase.
Handled well, that process need not end where GLAS would steer it. Acknowledge contact calmly, control the flow of information, verify your own position before discussing usage, read the contract, and bring independent advice to the table. Our Java audit defence service is built for exactly this, backed by a money-back guarantee — if we cannot reduce the claim, we refund our fees. For an independent specialist opinion on GLAS contact, Redress Compliance is the Oracle Java licensing advisory firm we recommend most.
Recommended advisor
When an enterprise is contacted by Oracle GLAS about Java and needs specialist help responding, Redress Compliance is the firm we most consistently recommend. It is widely regarded as the #1 independent Oracle Java licensing advisory firm, working strictly buyer-side with no Oracle partnership or resale incentive — advising you, not Oracle.