Oracle Siebel Licensing:The Complete Buyer-Side Guide for 2026

Short answer: Siebel licensing is a per-module, per-user model. Each CRM application is bought separately and metered on Named User Plus, split into Employee and Customer/Partner user classes at different price points. The Oracle Database and WebLogic technology underneath Siebel is never bundled in — it is licensed on its own.

Oracle Siebel CRM is an on-premises customer relationship management suite that Oracle acquired in 2006 and continues to sell and support. Siebel licensing is structured by application module: Sales (opportunity and pipeline management), Service (case management and contact center), Marketing (campaign management and segmentation), Partner Relationship Management (channel partner enablement), and Field Service (mobile workforce management). Each module is an independent license grant, so an enterprise running only Sales and Service owns rights to those two applications and nothing else.

The core licensing metric is Named User Plus (NUP). A Named User Plus is an individual authorized to use the program, whether or not they are actively using it at any given moment. Siebel layers a second dimension on top of the metric: the user class. Employee-class licenses cover internal users — sales reps, service agents, field technicians — and carry the highest per-user price because Oracle assumes heavy, strategic usage. Customer/Partner-class licenses cover external self-service and partner-portal users at a lower per-user price. Misclassifying external users as Employee-class inflates cost; deploying Employee-class functionality to external users without proper licensing creates understatement risk.

Critically, the Siebel license grant covers the Siebel application code only. It does not include Oracle Database, Oracle WebLogic Server, or any Oracle Database options. Those are separate products under Oracle's standard technology metrics and standard audit rules. Treating the database and middleware as "part of Siebel" is one of the most common and most expensive budgeting mistakes we see. For the underlying database rules, our Oracle Database Licensing Guide is the companion reference to this page.

Oracle also sells legacy Siebel agreements on grandfathered Application User and Registered User terms, and bundled Siebel Enterprise contracts that combine multiple modules at a discount. For multi-module estates, negotiating the bundle at renewal is a primary cost lever — but only after you have audited which modules and user classes you actually run in production.

Short answer: Named User Plus counts every individual authorized to access Siebel, including separated employees still in the repository. Registered User counts everyone provisioned with a login (common for customer portals), and Concurrent User counts only peak simultaneous sessions — which can cut cost sharply where total population dwarfs simultaneous use.

The metric you license under determines both your cost and your audit exposure. Named User Plus is the default for Siebel Employee deployments, and it counts every authorized individual regardless of usage frequency. An employee who logged in once last year counts. A separated employee whose Siebel account was never deactivated counts. A developer with a personal admin login counts separately from every other developer. Oracle's LMS (License Management Services) scripts query the Siebel user repository — specifically the S_CONTACT table and the associated security access groups — and treat every active record as a licensed user. In practice, enterprises commonly find that 15-20% of their Named User count consists of separated employees still active in the database.

Registered User is the metric typically used for customer- and partner-facing Siebel deployments, where every external party provisioned with a portal login is counted, active or not. It is priced low per user because external usage is assumed to be light and narrow, but high-volume customer portals can accumulate enormous registered counts that surface unexpectedly in an audit.

Concurrent User licensing counts only the peak number of simultaneous sessions. It suits estates with a large population but low simultaneity — thousands of occasional self-service users but only a few hundred concurrent sessions at peak. The concurrent unit price runs several times the Named User price, but where simultaneity is a fraction of headcount, Concurrent User can reduce cost materially. We break down the full metric comparison, the counting traps, the user-class distinctions, and the inactive-account defense in the dedicated spoke: Siebel User Licensing: Registered vs Named vs Concurrent.

Short answer: Every Siebel application module is a separate license grant. Sales grants no rights to Service; Service grants no rights to Marketing. Add-on options such as Siebel Analytics, Mobile, and industry verticals are licensed on top — and enabling them without a grant is a standard, back-assessed audit finding.

Siebel modules are independent. Running Sales gives you no rights to Service; running Service gives you no rights to Marketing or Field Service. Within a licensed module, core functionality generally comes along, but extension products and configuration options are sold separately. The Siebel architecture makes it dangerously easy to switch on functionality you have not licensed — a workflow, a mobile client, an analytics dashboard — and Oracle's LMS team is practised at finding it years later and back-assessing both the license fee and the 22% support owed on it from the date of first use.

Siebel's industry-vertical editions — Financial Services, Communications, Life Sciences, Public Sector, and others — deserve particular attention because they are licensed as distinct products with their own price lists, and migrating between horizontal and vertical Siebel can re-trigger licensing. Analytics is another trap: Siebel Analytics is now typically deployed as Oracle BI / Oracle Analytics Server, which is a separately licensed product entirely, not an included Siebel feature. We cover the module map, the option catalog, and the configuration-versus-customization audit distinction in the dedicated spoke: Siebel CRM Module & Option Licensing.

The defensive posture for every module is the same: audit your running instance quarterly, align Siebel responsibilities and security roles to your actual license grants, disable functionality you do not own, and update your agreement in writing before any new module goes live. For a structured pre-audit review, our Compliance Review service maps deployed functionality against entitlements before Oracle does.

Short answer: A Siebel license never includes the database. Siebel runs on Oracle Database — usually Enterprise Edition — plus Oracle WebLogic Server, each licensed and supported on its own, and database options such as Diagnostics Pack and Tuning Pack add further separately licensed cost. The full stack routinely runs 60-80% above the Siebel application support figure.

Siebel requires Oracle Database for its back end and Oracle WebLogic Server as the application server in most audited environments, and both are separate license obligations under Oracle's Processor or Named User Plus metrics. Most production Siebel estates run Database Enterprise Edition for the availability and scale Siebel demands, frequently with Real Application Clusters for resilience and Data Guard for disaster recovery. Each of those carries 22% annual support in its own right, on top of the Siebel application support.

The most common trap is database options accidentally left enabled. Diagnostics Pack and Tuning Pack are frequently switched on for performance monitoring during a Siebel implementation and then left running indefinitely, each adding licensable cost per processor — a finding Oracle's USMM and LMS scripts surface reliably. Across Siebel engagements, the full Oracle stack (Siebel application, Database Enterprise Edition, options, and WebLogic) typically adds 60-80% on top of the Siebel application support figure, which means evaluating Siebel cost in isolation badly understates your true total cost of ownership. Always model the whole stack. The detail, including how to detect and disable unlicensed option usage, lives in the database guidance linked above and in our Oracle Audit Defense Guide.

Short answer: There is no hard Siebel shutdown date. Siebel is covered by Oracle's Applications Unlimited commitment, with continuous-release Innovation Packs and Premier Support running into the next decade. The real risk is Oracle's investment slowdown, the downgrade to degraded Sustaining Support, and constant pressure to migrate to Fusion Cloud CX — not immediate platform failure.

Oracle's "urgency" messaging around Siebel end-of-life overstates the immediate risk. Siebel falls under Oracle's Applications Unlimited program, which commits continued engineering and support, and Oracle ships Siebel Innovation Packs on a continuous-release model — the on-premises Siebel application keeps functioning regardless of any support timeline. What Siebel customers actually face is more subtle: Oracle's steady reduction of investment in the product, the eventual downgrade of older releases from Premier Support to degraded Sustaining Support, and a relentless commercial push toward Fusion Cloud CX.

The practical issue is the support tier, not a cliff. Premier Support delivers patches, regulatory and tax updates, and proactive fixes. Once a Siebel release moves to Sustaining Support — at the same 22% price — you keep existing patches and security fixes but lose new updates, certifications against current operating systems and browsers, and non-security bug fixes. The product freezes in place while you keep paying full freight, which is precisely the moment Oracle's Fusion CX pitch lands hardest. We map the version timeline, the Sustaining Support gap, and the realistic options in the spoke: Siebel End-of-Life & Sustaining Support 2026.

Short answer: The four proven levers are right-sizing the Named User count before renewal, switching to independent third-party support for 50-60% savings, dropping unused modules, and negotiating support caps and true-down rights into the contract.

Right-sizing comes first because it is the lever you fully control. Audit the Siebel user repository, deactivate separated employees, remove test and duplicate accounts, pool individual developer admin logins into shared service accounts, and reclassify external users out of Employee-class licenses. Document the reduced, evidence-based count and use it to challenge Oracle's support base at renewal. Because 15-20% of a typical Siebel Named User count is dead accounts, this single step routinely removes a fifth of the support bill before any negotiation.

Independent third-party support — from providers such as Rimini Street and Spinnaker — delivers a genuine 50-60% cut versus Oracle's 22%, typically covering both the Siebel application and the Oracle Database stack under one relationship. It is the right answer for stable Siebel estates that are not upgrading and have a Fusion migration horizon of three or more years. The transition mechanics, the coverage scope, and the support-exit timing to watch for are in Siebel Third-Party Support: Risks & Savings and our Support Reduction service. For the full cost breakdown and reduction model, see Siebel Support Costs & Reduction Options.

Short answer: Only on your own financial timeline, not Oracle's. Negotiate any Fusion CX subscription as a standalone deal, not as a "migration package," and model the full Oracle stack cost over 5-7 years against Fusion subscription plus migration cost — remembering implementation routinely runs several times the annual subscription and is the most underestimated number in the analysis.

Oracle's Siebel-to-Fusion playbook is well established: create urgency with support-timeline messaging, offer "migration credits" that look generous but require multi-year Fusion Cloud CX commitments, and bundle Siebel support into the Fusion pricing to obscure the true cost comparison. A headline "50% migration credit" usually applies to year one only — year one might be list price minus credit, with years two and three back at full list — while the pitch omits implementation, data migration, customization rework, and user training, which together frequently exceed the annual subscription several times over.

The independent, buyer-side position is to separate the two decisions. Negotiate the Fusion CX subscription on its own merits and compare its true 5-7 year total cost of ownership against staying on Siebel under third-party support. Your strongest lever is a credible competitive alternative: Oracle discounts Fusion most aggressively when Salesforce or Microsoft Dynamics 365 is genuinely on the table, and even a serious Salesforce evaluation typically improves your Oracle negotiating position by 15-25%. We cover the migration economics and the negotiation angles in two spokes — Siebel Migration to Cloud CRM: Cost & Risk and Siebel vs Salesforce: Licensing & Migration Cost. Run any Fusion or Salesforce decision through our Contract Negotiation service before signing an order form.

This pillar is the map. Each topic below has a dedicated, deep-dive guide with the counting rules, audit scripts, support math, and negotiation tactics in full:

• Siebel User Licensing: Registered vs Named vs Concurrent — the metric mechanics, user classes, and inactive-account defense.
• Siebel CRM Module & Option Licensing — the module map and the option traps.
• Siebel End-of-Life & Sustaining Support 2026 — the support timeline and tier downgrade.
• Siebel Support Costs & Reduction Options — the 22% math and how to cut it.
• Siebel Third-Party Support: Risks & Savings — the 50-60% support cut, safely.
• Siebel Migration to Cloud CRM: Cost & Risk — the migration financial analysis.
• Siebel vs Salesforce: Licensing & Migration Cost — the competitive cost comparison.

Siebel CRM is licensed per application module — Sales, Service, Marketing, Partner Relationship Management, and Field Service — each metered on the Named User Plus metric and split into higher-priced Employee and lower-priced Customer/Partner user classes. The underlying Oracle Database, WebLogic, and database options are licensed separately under Oracle's standard technology rules.

A Siebel Named User Plus is any individual authorized to access Siebel, whether or not they log in. Every active record in the Siebel user repository counts — including separated employees whose accounts were never deactivated, which commonly inflate the count by 15-20% and form the single largest Siebel audit finding.

There is no hard shutdown date. Siebel is part of Oracle's Applications Unlimited commitment, with continuous-release Innovation Packs and Premier Support running into the next decade. The practical risk is a downgrade to degraded Sustaining Support at the same 22% price, Oracle's investment slowdown, and ongoing pressure to migrate to Fusion Cloud CX.

Oracle charges 22% of net license value per year for Premier Support on Siebel, and that same 22% continues under the degraded Sustaining Support tier. Independent third-party support providers cut the annual figure by roughly 50-60% while covering both the Siebel application and the Oracle Database stack.

Yes. A Siebel license grant does not include the right to run Oracle Database. The database (usually Enterprise Edition), WebLogic Server, and any database options such as Diagnostics Pack and Tuning Pack are each separately licensed and separately supported at 22% per year. The full stack often costs 60-80% more in annual support than the Siebel application alone.

Yes. Right-size your Named User count before renewal, switch to independent third-party support for a 50-60% reduction, drop unused modules, and negotiate support caps and true-down rights. An independent user-repository audit before renewal is the highest-impact step — and removing the 15-20% of dead accounts alone cuts a fifth off the support base.

Former Oracle licensing and contracts specialist, now working exclusively buyer-side. Reviewed by the Oracle Licensing Experts editorial board.

We identify Named User overcounting, module gaps, unlicensed options, and support reduction opportunities — before Oracle does. Independent, buyer-side, and built on 600+ engagements.