Oracle Forms licensing in 2026. Why named user plus wins below 50 users per processor.

Oracle Forms is licensed as Oracle Forms and Reports, at $23,000 per processor or $460 per named user plus. Below 50 authorized users per processor, named user plus costs less, and the bill is set by the cores in the production tier.

Two published list prices decide which metric your Forms tier should be on, and a few engineering decisions decide whether the bundled licenses still cover it. This guide covers both, with worked numbers, and what the December 2026 support date changes.

How is Oracle Forms licensed?

Oracle Forms is licensed through a single Fusion Middleware product called Oracle Forms and Reports, on either the processor metric or named user plus. There is no separate Forms product to buy. In most cases there is no separate WebLogic Server purchase either, because the license carries full use rights to WebLogic Server Basic.

Oracle's Technology Global Price List puts Forms and Reports at $23,000 per processor and $460 per named user plus. Annual support is 22 percent of the net license fee. Named user plus has a minimum of 10 users for every processor the programs run on.

What does the Forms and Reports license include?

The license covers the whole Forms and Reports runtime stack, including the web tier and the application server. Read the entitlement before you count servers, because we regularly find customers paying for components they already hold:

• Forms Services. The Forms runtime that serves your application modules to users.
• Reports Services. The Reports server, with both the paper layout and the web layout engines.
• Oracle HTTP Server. The web tier that sits in front of Forms and Reports.
• WebLogic Server Basic. A feature limited application server grant, covered in detail below.
• Enterprise Manager Fusion Middleware Control. Included for configuring and running the domain. It is a different thing from the separately licensed Enterprise Manager management packs.

How are processors and named users counted?

Processors are counted from the physical cores in the production tier, multiplied by the core factor for the chip and rounded up to the next whole license. Current Intel and AMD server chips carry a factor of 0.5, so 16 cores need 8 processor licenses.

Named user plus counts every individual you authorize to use the programs, whether or not they are active at a given moment. Devices that drive the programs without a person count as well, such as a scheduler that submits reports overnight. Multiplexing through an application tier does not reduce the count, because Oracle measures users at the front end.

When is named user plus cheaper than the processor metric for Forms?

Named user plus is cheaper below 50 named users for each processor you would otherwise license. Divide $23,000 by $460 and you get exactly 50. The line applies per processor, which means a large company with a small Forms tier can still sit well under it.

The floor puts the cheapest compliant position at $4,600 per processor, a fifth of the processor price. Above 50 users per processor, the processor metric wins and keeps winning as the user count climbs.

A worked example on an eight processor tier

Say your Forms production tier runs on two x86 servers with 8 cores each. That is 16 cores at a 0.5 factor, or 8 processor licenses: $184,000 at list plus $40,480 a year of support, roughly $40,500. The named user plus minimum on the same tier is 80 users.

A legacy Forms application usually serves a known operational group, such as finance clerks, warehouse staff or a claims team. On a tier this size that group is often well under 400 people. Count it properly, including interface accounts and scheduled jobs, before you accept either figure.

When does the processor metric make more sense?

• External users. Suppliers, customers or partners sign in and you cannot keep a reliable list of named individuals. A processor license covers internal users, agents, contractors and third party users alike.
• Expected growth. An acquisition or a new site would push the count past the crossover during the support term.
• Heavy automation. Many devices and integrations drive the programs, and each one would need its own named user plus license.

Why do Forms production tiers carry more cores than their users need?

They carry surplus cores because the core count follows the hardware while the user count follows the business. On a legacy Forms application the user population is usually stable or shrinking: new development happens elsewhere and the remaining users are a defined operational group. The licensed core count, by contrast, only ever grows.

Each hardware refresh puts the same application on denser chips. Unless someone reduces the allocation, the licensable base grows with the machine. The infrastructure team records it as a server project, and the license owner is rarely told.

What does the surplus cost on the example tier?

Take the same 8 processor tier. If it carries 60 percent more licensed cores than its users justify, it needed 5 processor licenses and holds 3 too many: $69,000 of license and $15,180 a year of support. At 30 percent more, the need rounds up to 7 licenses, so 1 is surplus, worth $23,000 and $5,060 a year.

Support is billed at 22 percent of the net fee on the licenses you bought, whatever you still run, so a surplus processor keeps charging every year until you terminate it. Oracle requires every license in a license set to sit at the same support level, so the clean route is to terminate the surplus licenses outright.

How do you check your own position?

1. Cores. Run lscpu on each Linux host in the production tier, or read the core count from your hypervisor or hardware inventory, and compare it with the processor count on your ordering documents.
2. Users. If the application signs users in with database accounts, DBA_USERS in the application database gives a first list. If it uses a single sign on directory or its own user table, start there, then add interface accounts and scheduled report jobs. Our guide to named user plus counting shows how auditors test the list.
3. Deployments. Read config.xml in the domain directory. It lists every application and library deployed to the domain, and anything that is not a Forms or Reports component needs an explanation.
4. Features. Run the WebLogic Server Basic Feature Usage Measurement Script from My Oracle Support, Doc ID 885587.1. It is an optional WLST script, it sends no data to Oracle, and it does not test every restricted feature.
5. Repository. Query the SCHEMA_VERSION_REGISTRY view in the repository database to see the schemas the Repository Creation Utility installed, then look for anything else in that instance.

What does WebLogic Server Basic allow with Forms, and what does it exclude?

WebLogic Server Basic gives you the application server features a typical Forms domain needs. Oracle's Fusion Middleware licensing manual lists the core application server, Java EE, the Administration Console and WLST, JDBC drivers and web server plug ins, basic JMS and deployment, and basic clustering with load balancing, failover and node manager.

The exclusions are published in the same manual and are not open to negotiation. Teams trip on them in predictable ways:

Every row is a decision made by an engineer solving a legitimate problem, and none of them looks like a licensing event at the time.

Why is a second application in the Forms domain so expensive?

WebLogic Server Basic is licensed only for running the components that come with the product, such as Forms and Reports. Oracle's manual makes a narrow allowance for custom Java applications written for Oracle Containers for J2EE, the older Application Server container. Deploy anything else into that domain and the included grant no longer covers the servers it runs on.

WebLogic Server Enterprise Edition lists at $25,000 per processor, so on the 8 processor tier the exposure is $200,000 plus $44,000 a year. Give anything that is not Forms or Reports its own domain on separately licensed servers, and make the domain owner approve every deployment.

Where else do restricted use limits catch Forms teams out?

The other failures happen in the database and the management tools, where an included right sits next to a paid one. We check these points on every Forms review:

• The repository database. Under restricted use it holds your middleware repository schemas and nothing else. A single application table placed in that instance makes the whole database licensable.
• Fusion Middleware Control and the management packs. Control is included for configuration. Reaching a pack feature through a console you already hold is still use of the pack.
• Duplicate purchases. Separate orders for Oracle HTTP Server or WebLogic Server for a Forms tier that already has both.

What does the repository mistake cost?

Say the repository runs on a 4 core x86 server, which is 2 processor licenses. Once an application table lands there, Oracle can ask for full licenses. On Database Enterprise Edition at $47,500 per processor list, that is $95,000 plus $20,900 a year of support for an instance the restricted use grant covered the day before.

Neither the repository nor the WebLogic problem means Forms is expensive. Both come from ordinary engineering convenience meeting a restricted grant. For the component by component picture across the product family, see our Oracle middleware licensing guide.

What have we seen in recent Forms licensing reviews?

Across roughly 25 to 35 Oracle licensing engagements we benchmarked in 2024 and 2025, legacy Forms deployments were consistently oversized against their active user base. Four patterns came up often enough to plan around:

• Core surplus. Production tiers ran 30 to 60 percent more licensed cores than the active user population justified.
• Unrecorded growth. In roughly 1 in 2 deployments, a hardware refresh had grown the licensable core base without anyone recording it as a licensing change.
• Minimums by default. On most smaller deployments, the named user plus minimum set the bill rather than a count of actual users. The price was about right, but no one had compared it with the processor licenses the customer also held.
• Enterprise Edition claims. Where a WebLogic Server Enterprise Edition claim appeared, a restricted feature or a second application in the Forms domain usually triggered it. Forms itself rarely did.

Why we do not advise keeping Forms on processors just to be safe

A common recommendation, from account teams and sometimes from internal asset managers, is to license Forms by processor because no one then has to count users. We disagree for any legacy application with a nameable user group. Processor licensing ties the bill to the hardware, so each refresh raises the cost of serving the same people.

The better course is to count authorized users and devices once, keep the list current, and choose the metric per tier against the 50 per processor line. A maintained user list is easy to show an auditor, and on most Forms tiers it costs a fraction of the processor position.

The users on a legacy Forms application shrink over time, while the cores under it grow with every refresh, and a processor license follows the cores.

What will Oracle's account team say, and how should you answer?

Expect four lines when you raise a metric change, a reduction or an upgrade. Each has a factual answer.

What does the December 2026 support deadline mean for Forms?

Premier Support for the Fusion Middleware 12c release line, which includes Forms and Reports 12c, ends in December 2026, and Extended Support runs to December 2027. Forms 14.1.2 is the successor release and is already available. Doing nothing therefore has a date attached, whether or not you have an upgrade plan.

Your Forms and Reports licenses carry forward to 14.1.2 while support is current, so the upgrade needs no new purchase. If you build new servers for it, size them to the user population, keep any second application out of the new domain, and settle the metric per tier before you sign anything new with Oracle.

What should happen before the next support renewal?

The wider set of Oracle guides sits in our Oracle knowledge hub.

What to do next

1. Count the named users. Include devices and interface accounts, then divide by the processors you would otherwise license. Below 50 per processor, named user plus is the cheaper metric.
2. Compare cores with users. Set licensed cores in the production tier against the active user population, and check whether a hardware refresh grew the base without anyone deciding to.
3. Audit the WebLogic domain. Look for excluded Basic features: server migration, versioned deployment, store and forward, GridLink and WLDF diagnostics.
4. Protect the boundaries. Confirm no second application shares the Forms domain and no application table sits in the restricted use repository database.
5. Model the saving. Price the surplus termination with repricing before you ask Oracle for anything.
6. Schedule the 14.1.2 upgrade. Plan it inside the 12c support window, on servers sized to your users. The Oracle practice runs the middleware review with you.

Frequently asked questions