Short answer: Siebel support costs are Oracle's annual maintenance fee of roughly 22% of the net license value, charged every year under Software Update License & Support — regardless of usage. Because Siebel licenses are perpetual, support is the only recurring Oracle cost, and it can be cut by terminating unused license sets, renegotiating the support base, or moving to third-party support at about 50% of Oracle's fee.
Key Takeaways
- Siebel support costs are ~22% of net license value per year under Oracle Software Update License & Support (SULS), calculated on the original license fee, not on current usage.
- The support fee rises annually — commonly an uplift of up to ~4% under standard policy — and the base does not fall as your user count or usage falls.
- Oracle's matching service level and repricing rules are why naive support cuts backfire: dropping part of a license set can re-price the licenses you keep, wiping out the saving.
- Because Siebel licenses are perpetual and owned, support is the only recurring Oracle cost — and it is reducible without migrating off Siebel.
- Third-party support runs at roughly 50% of Oracle's fee, halving the annual cost for a stable estate in exchange for losing access to new Oracle patches and upgrades.
- Across our Siebel engagements, clients reduced annual Siebel support spend by 30–50% through a mix of license-set termination, base renegotiation, and third-party support (Oracle Licensing Experts benchmark, 2026).
How much are Oracle Siebel support costs?
Oracle Siebel support costs run at roughly 22% of the net license fee per year under Oracle Software Update License & Support (SULS) — the standard Oracle maintenance program. Software Update License & Support is Oracle's annual program covering patches, version upgrades, and technical support in exchange for a recurring fee. On a Siebel estate originally licensed for $5 million net, that is about $1.1 million every year, and it continues whether or not you apply a single patch.
The fee is calculated on the original net license value — the discounted price you actually paid — not on your current user count or how much of Siebel you still run. That detachment from usage is the structural reason Siebel support costs feel disproportionate to a shrinking deployment. The full metric and contract context sits in the Siebel licensing guide, and the user-metric mechanics are in our spoke on Siebel user licensing types.
The line you will hear is "support is just 22%, it's standard." What goes unsaid is that 22% compounds: with annual uplifts, the fee you pay in year ten can be a third higher than year one, on a license base that has not grown an inch. The fee is engineered to be sticky, not to track the value you actually consume.
Why do Siebel support costs keep rising every year?
Siebel support costs rise because Oracle applies an annual uplift to the support stream — commonly up to ~4% under standard policy, and more where the contract permits. The fee is anchored to the original net license value and protected by matching-service-level and repricing rules, so the base does not fall as your usage falls. You pay more each year for support on software whose footprint may be flat or shrinking.
This is by design. Oracle support is one of its most profitable revenue streams, and the policies around it are written to make the support base resistant to reduction. Understanding those policies is the first step to cutting the fee — which is exactly what our Oracle support reduction service is built around, and the broader commercial context is in the Oracle negotiation guide.
| Lever | Effect on Siebel support cost | Buyer action |
|---|---|---|
| Annual support uplift | Raises fee up to ~4%/yr | Negotiate cap or freeze at renewal |
| Net license value anchor | Base ignores reduced usage | Terminate unused license sets |
| Matching service level | Blocks partial drops within a set | Restructure sets before reducing |
| Repricing on partial termination | Re-rates kept licenses upward | Model net effect before acting |
| Third-party support | Cuts fee to ~50% | Move stable estate off Oracle support |
| Reinstatement penalty | Back-support + fee to return | Decide direction once, deliberately |
Can I reduce Siebel support costs without migrating off Siebel?
Yes — and it is the highest-value move for most stable Siebel estates. Because Siebel licenses are perpetual and owned, support is the only recurring Oracle cost, and it can be cut three ways: terminate genuinely unused license sets, renegotiate the support base at renewal, or move to third-party support at roughly 50% of Oracle's fee while keeping your perpetual licenses. Each lever carries trade-offs around repricing and patch access.
The discipline that makes this work is modeling the net effect before you act, because Oracle's repricing rules can claw back a naive saving. Our license optimization service maps which licenses are truly unused and quantifies the support reduction available, and the broader keep-vs-replace economics are in our comparison, Siebel vs Salesforce cost.
Across the Siebel estates we have reviewed, clients reduced annual Siebel support spend by 30–50% through a combination of unused-license-set termination, support-base renegotiation, and third-party support — without migrating off the platform (Oracle Licensing Experts benchmark, 2026).
Paying too much for Siebel support?
Our support reduction service models every lever — termination, renegotiation, third-party support — and the repricing risk, so you cut the fee without triggering a clawback. Clients typically save 30–50% on annual Siebel support.
How much can third-party support save on Siebel?
Third-party support for Siebel typically costs about 50% of Oracle's annual support fee, so an organization paying $1 million a year to Oracle would pay roughly $500,000 to a third-party provider. Third-party support is independent maintenance — break-fix, tax and regulatory updates, and security guidance — delivered by a non-Oracle vendor on your owned perpetual licenses. The trade-off is no access to new Oracle patches or version upgrades.
That trade-off suits a stable, effectively frozen Siebel estate far better than one mid-upgrade. The strategic case, the legal precedent, and the risks are covered in our spoke on Siebel third-party support, and the platform's longevity — which underwrites a freeze decision — is documented in our Siebel end-of-life analysis.
Is dropping Siebel support a good way to save money?
Dropping Oracle support entirely stops the ~22% annual fee, and you keep the perpetual licenses you own — but you lose patches, updates, and the right to reinstate without a reinstatement penalty, which is typically back-support for the lapsed period plus a fee. For most organizations, going fully unsupported is riskier than it looks, because reinstatement later is deliberately expensive.
For a stable estate, moving to third-party support is usually the better route than going dark, because it preserves break-fix and compliance updates at about half the Oracle cost without the reinstatement exposure. Whichever direction you choose, decide it once and deliberately — and document the licenses you own so any later Oracle compliance claim meets your own evidence. Our audit defense service covers that exposure, and real outcomes are in our client case studies.
Siebel Support Costs FAQ
How much are Oracle Siebel support costs?
Oracle Siebel support costs run at roughly 22% of the net license fee per year under Oracle Software Update License & Support (SULS). On a Siebel estate originally licensed for, say, $5 million net, that is about $1.1 million a year — and it continues for as long as you keep support, regardless of whether you have applied a single patch. The fee is calculated on the original net license value, not on current usage.
Why do Siebel support costs keep rising every year?
Siebel support costs rise because Oracle applies an annual uplift to the support stream — commonly up to ~4% under standard policy and more where contracts permit. The fee is also anchored to the original net license value and protected by Oracle's matching service level and repricing rules, which make it difficult to reduce the support base by dropping individual licenses. The base does not fall as your usage falls.
Can I reduce Siebel support costs without migrating off Siebel?
Yes. Because Siebel licenses are perpetual and owned, support is the only recurring Oracle cost, and it can be cut several ways: terminate genuinely unused license sets, negotiate the support base at renewal, or move to third-party support at roughly 50% of Oracle's fee while keeping your perpetual licenses. Each lever has trade-offs around repricing and patch access, so model them before acting.
How much can third-party support save on Siebel?
Third-party support for Siebel typically costs about 50% of Oracle's annual support fee, so an organization paying $1 million a year to Oracle would pay roughly $500,000 to a third-party provider for break-fix, tax and regulatory updates, and security guidance. The trade-off is no access to new Oracle patches or version upgrades, which suits a stable, frozen Siebel estate far better than one mid-upgrade.
What is Oracle's matching service level rule on Siebel support?
Oracle's matching service level rule requires that all licenses in the same agreement or license set carry the same support level — you cannot keep support on some Siebel licenses and drop it on others within the set to cherry-pick savings. Combined with repricing, this means partial terminations can trigger a recalculation that raises the per-license cost on what you keep. It is the main reason naive support cuts backfire.
Is dropping Siebel support a good way to save money?
Dropping Oracle support entirely stops the ~22% annual fee and you keep the perpetual licenses, but you lose patches, updates, and the right to reinstate without a reinstatement penalty (often back-support plus a fee). For a stable estate, moving to third-party support is usually the better route than going fully unsupported, because it preserves break-fix and compliance updates at about half the Oracle cost.