How to Sell SaaS on Oracle Cloud Marketplace

Oracle Cloud Marketplace is where partners publish and transact applications for Oracle Cloud Infrastructure (OCI) customers, who pay through the Universal Credits they have already committed to Oracle. For a SaaS company it is the way to reach Oracle’s enterprise base and settle deals against a commitment the buyer is motivated to draw down — but the on-ramp is Oracle-specific, from partner-network membership to a concentration cap most sellers meet only when a deal stalls.

This guide is the complete publisher playbook. It covers the listing types and where each deploys, who is allowed to publish, all four pricing models, how Universal Credits billing works, the full private-offer flow and the 25% rule that decides whether a buyer can even accept, the publishing guidelines Oracle reviews against, how you get paid, and where a cross-marketplace platform fits.

What Oracle Cloud Marketplace is

Oracle Cloud Marketplace is the catalog of partner applications and services that OCI customers browse, deploy, and buy from inside their Oracle Cloud tenancy. The commercial engine underneath it is Universal Credits — Oracle’s committed-spend model, where a customer’s credits are debited as they use OCI services over the course of a year. A marketplace purchase is attractive to the buyer precisely because it consumes a commitment they have already made.

There are two ways customers reach the Marketplace, and it is worth knowing which one you are optimizing for:

The Marketplace in the OCI Console is integrated into Oracle Cloud. It requires an OCI login and lets customers browse, purchase, and deploy solutions directly into their own OCI environment. This is where transactions happen.
The public Oracle Marketplace is accessible without an OCI login. It lets prospects explore before they commit, and it serves as a marketing surface for partners. This is where discovery happens.

That makes Oracle closer in spirit to the hyperscaler marketplaces (a purchase draws down committed spend) than to Snowflake (a purchase settles inside the data platform). But the mechanics — partner-network membership, publisher registration, the listing types, the transaction models, the buyer-eligibility rules — are Oracle’s own.

Source: Oracle, Overview of Oracle Marketplace.

The listing types

An Oracle listing is one of several shapes, and the shape determines what the customer actually gets:

A click-to-deploy listing includes a deployable install package. It appears in the OCI Console Marketplace, deploys onto the customer’s infrastructure, and can use any transaction model Marketplace supports. Click-to-deploy covers the deployable artifacts — compute images, stacks provisioned through Resource Manager, and container or Kubernetes applications — that stand up real infrastructure in the buyer’s tenancy.

A lead-generation listing carries no deployable artifact. It captures interest and hands you the lead. Oracle lets partners convert a lead-generation listing to click-to-deploy at any time by adding an install package, so a lead-gen tile is a reasonable place to start while the deployable artifact catches up.

For a SaaS company specifically, Oracle defines a SaaS offering as a subscription-based cloud solution delivered and operated by the partner in OCI, with clear commercial terms — pricing tiers, usage limits, and optional trials. A SaaS listing is transactable with private offers, or offered as a “Buy From Seller” listing, and it can include an install package to make it click-to-deploy.

Source: Oracle, Publishing SaaS Applications.

Who can publish

Publishing on Oracle Cloud Marketplace has more prerequisites than most marketplaces, and skipping one stalls the launch:

An OCI tenancy subscribed to the US East (Ashburn) region, and approved Marketplace publisher status.
Oracle Partner Network (OPN) membership. You must register your company in OPN before you can publish; Oracle validates the OPN number you enter during publisher registration.
A US-domiciled legal entity for anything paid. If you intend to publish a paid listing or a private offer, Oracle requires the OPN membership to be associated with a legal entity domiciled in the United States.
Acceptance of the Oracle Cloud Marketplace Agreement (OCMA) once you have your OPN Company ID.
The required IAM policy for package listings in your tenancy, and administrator-managed access for the users who will manage listings.
Supplier setup for payouts — company details, tax ID and tax forms, bank account, and two authorized contacts — before Oracle can pay you.

Registration itself runs through the Console: open the navigation menu, select Marketplace, and under Publisher choose Publisher Registration. You provide company information, your OPN number (which Oracle validates), your tenancy details, and a description of your solutions, then submit.

Source: Oracle, Registering as a Marketplace Publisher.

The four pricing models

Oracle Cloud Marketplace supports four transaction models, and your choice determines how the customer is charged and how you get paid:

Free listing. The software carries no licensing cost; the customer pays only for the OCI infrastructure it runs on. This is the model for open-source tools, community images, and freemium on-ramps.

BYOL (Bring Your Own License). The customer brings an existing Oracle or ISV license, or purchases a license directly from you outside the marketplace transaction. Oracle charges no marketplace licensing fee; the license relationship is yours to manage. This suits enterprises with license investments they want to carry to OCI.

Paid listing. Oracle charges the customer by the hour for the software license, with no long-term commitment, and Oracle bills the customer on behalf of the partner through their Universal Credits subscription. Oracle then remits payment to you based on usage. This is the metered, pay-as-you-go model.

Private offer. A custom-priced, negotiated deal for a named customer, also settled against Universal Credits (covered in detail below). “Buy From Seller” is the adjacent self-serve path for a SaaS listing.

Across all paid models, the customer’s marketplace spending is capped: the amount a customer can spend on third-party solutions is limited to 25% of the customer’s active Universal Commit Credit (UCC) amount, and that limit is measured against the commitment, not the available balance.

Source: Oracle, Pricing Models for Marketplace.

How Universal Credits billing works

Universal Credits are the reason a marketplace deal is easy for an Oracle buyer to say yes to: they have already committed the money, and a marketplace purchase draws it down against services they were going to use anyway. For a paid or private-offer listing, Oracle meters consumption, bills the customer’s Universal Credits subscription, and pays you as the registered supplier. That is why the supplier record — tax forms, bank details, authorized contacts — is a hard prerequisite for any paid listing: without it, Oracle has no way to remit what the customer has spent.

The flip side is the 25% cap. Because Oracle protects the customer’s commitment for Oracle’s own services, only a slice of it can go to marketplace partner products — which is the single rule that most often surprises a seller late in a deal.

Private offers on Oracle Cloud Marketplace

A private offer is a custom-priced deal a publisher extends to a specific OCI customer, settled against that customer’s Universal Credits. Enabling them is a deliberate, multi-week process, not a toggle:

Your publisher account must be qualified by Oracle’s Marketplace and Strategic Partnerships team — an email request with your OPN company ID and tenancy ID, with roughly a 48-hour acknowledgment and two to three weeks for full enablement.
Each listing must have deployable artifacts and, when you publish, you define the unit of measure and quantity for entitlements. The publisher is responsible for monitoring consumption.
Manage offers from an artifact tenancy, not your operational service tenancy — Oracle recommends against using an operational service tenancy, and you can create a child tenancy under the Universal Credits subscription for this.
Set the IAM policies for the users who will create and manage offers.

Source: Oracle, Prerequisites for Private Offers.

The 25% Universal Credits rule

This is the buyer-side prerequisite that surprises sellers late in a deal. For a customer to accept a private offer, Oracle requires:

“The customer’s Universal Credits commit credit spending for Marketplace partner products, including the prospective private offer, must be less than 25% of the customer’s active Universal Credits commit credits.”

In plain terms: a customer cannot spend more than a quarter of their Oracle commitment on marketplace partner products, and your prospective offer counts toward that quarter. The customer also needs an active Universal Credits commit subscription in an approved country, and the subscription currency must match the offer currency. Check the buyer’s headroom before you build the offer, or you will price a deal the customer is not eligible to accept. (Note that some third-party summaries state this cap as 15% — Oracle’s own documentation states 25%, which is the figure to plan against.)

What Oracle reviews: the publishing guidelines

Every listing is reviewed and approved by Oracle before it goes on the Marketplace, and the review checks concrete things. Build the listing to pass on the first pass:

Customer-facing documentation with prominent, detailed instructions for connecting to an instance, usage documentation (or a link to it), support details, the compatible compute shapes, and documentation of every network port open by default on the instance.
A Support section with accurate contact details — a real phone number or email a customer can use to reach partner support.
System Requirements listing the required OCI components: compute shapes, security rules, IAM policies, block volumes, secondary VNICs, and anything else the solution needs.

These are not formalities. A listing that hides its ports, omits real support contacts, or under-specifies its shapes is the kind that comes back from review, and each round adds days.

Source: Oracle, Publishing Guidelines.

How you get paid

An Oracle marketplace purchase draws down the customer’s Universal Credits, and Oracle pays you as the supplier — which is why the supplier setup (tax forms, bank details, authorized contacts) is a hard prerequisite for any paid listing. Because payout runs through Oracle’s royalty process, get the supplier record complete early; it is the kind of finance-and-legal task that adds weeks if it is left until a deal is ready to close. BYOL is the exception: there, the license payment is yours to collect directly, and Oracle is not in the money path.

Deployable listings: images, stacks, and containers

Click-to-deploy is a family, not a single shape, and the artifact you ship decides how the customer stands your product up:

A compute image packages your software as a bootable OCI image the customer launches as an instance. It is the most direct path for a product that runs on a VM.
A stack provisions infrastructure through Oracle Resource Manager, which uses Terraform underneath. A stack listing can stand up a whole environment — networking, compute, storage — from one deployment, which suits products that are more than a single instance.
A container or Kubernetes application targets OCI’s container services for products that ship as containers.

For a SaaS company, the SaaS listing type sits alongside these: a subscription solution you operate in OCI, transactable with private offers or as a “Buy From Seller” listing, and convertible from a lead-generation tile once the deployable artifact is ready. Pick the artifact that matches how your product actually runs, because it determines the customer’s deploy experience and the System Requirements Oracle reviews.

OCI regions and tenancy strategy

Two Oracle-specific setup decisions catch first-time publishers:

The Ashburn requirement. Your publisher tenancy must be subscribed to the US East (Ashburn) region. This is a publishing prerequisite, independent of where your customers deploy.
Separate the artifact tenancy from operations. Oracle recommends managing listings and private offers from an artifact tenancy rather than your operational service tenancy, and you can create a child tenancy under the Universal Credits subscription for it. Keeping publishing separate from the environment that runs your own workloads avoids a class of access and billing tangles later.

Set the IAM policies for the users who manage listings and offers as part of this, so the people who publish have exactly the access they need and nothing they don’t.

The mistakes that slow a first Oracle listing

Oracle’s on-ramp is longer than most, and the delays cluster in predictable places:

Leaving OPN and the US-entity requirement to the end. Membership and a US-domiciled legal entity gate every paid deal; both take time to sort.
Enabling private offers reactively. Qualification runs two to three weeks. If you wait for a live deal, the deal waits for you.
Discovering the 25% cap during negotiation. Check the buyer’s Universal Credits headroom before you price the offer, not after.
An incomplete supplier record. No tax forms and bank details means no payout, and finance tasks are exactly what slip when a deal is otherwise ready.
A listing that fails review. Missing open-port documentation, vague support contacts, or under-specified System Requirements send a listing back for another round.

Oracle Cloud Marketplace vs the hyperscaler marketplaces

Oracle shares the committed-spend shape of the hyperscaler marketplaces but differs in the details that matter operationally:

The commitment is Universal Credits, and only a quarter of it (the 25% cap) can go to marketplace partner products — a tighter constraint than the equivalent on AWS or Microsoft.
The prerequisites are heavier — OPN, a US entity for paid, an Ashburn tenancy, the OCMA — where a hyperscaler onboarding is lighter.
Payout runs through Oracle’s royalty process against a supplier record you set up in advance.

None of this makes Oracle harder to sell on once you are set up; it makes the setup the thing to start early. Everything after the first paid listing is the familiar committed-spend motion.

Where Oracle fits a multi-marketplace GTM

Oracle is one of several marketplaces most ISVs eventually sell on. Alongside AWS, Microsoft, Google Cloud, Snowflake, and Alibaba Cloud, the real cost is not the Oracle listing — it is reconciling six committed-spend models, six payout processes, and six sets of eligibility rules like the 25% cap.

Suger is a Cloud GTM platform for selling and billing through cloud marketplaces — AWS, Microsoft, Google Cloud, Snowflake, Alibaba Cloud, and Oracle — so private offers, metering and billing, and disbursement reconciliation run from one system. For the broader ISV walkthrough of Oracle specifically, see the Oracle Cloud Marketplace seller guide; for the cross-cloud operating model, the Cloud GTM guide is the pillar.

Frequently asked questions

Do you need to be an Oracle partner to sell on Oracle Cloud Marketplace? Yes. You must register your company in Oracle Partner Network (OPN) before publishing, and Oracle validates your OPN number during publisher registration. For paid listings or private offers, the OPN membership must be tied to a US-domiciled legal entity.

What pricing models does Oracle Cloud Marketplace support? Four: Free (customer pays only for infrastructure), BYOL (the customer brings or buys a license directly), Paid (hourly metered, billed through the customer’s Universal Credits), and Private Offer (a negotiated deal settled against Universal Credits).

What is the 25% rule on Oracle private offers? A customer’s Universal Credits spending on marketplace partner products — including the offer being made — must be less than 25% of their active Universal Credits commit credits. Confirm the buyer’s headroom before building the offer.

What is the difference between click-to-deploy and lead-generation listings? A click-to-deploy listing includes a deployable install package and can transact through the marketplace. A lead-generation listing captures interest with no artifact and can be converted to click-to-deploy later by adding an install package.

How long does it take to enable private offers on Oracle? Oracle’s Marketplace and Strategic Partnerships team must qualify your publisher account. Expect roughly a 48-hour acknowledgment and two to three weeks for full enablement, so start well before a live deal needs it.

How do sellers get paid on Oracle Cloud Marketplace? For paid and private-offer listings, purchases draw down the customer’s Universal Credits and Oracle pays you as a registered supplier. Complete the supplier record — tax forms, bank details, authorized contacts — early. Under BYOL, you collect the license payment directly and Oracle is not in the money path.

What does Oracle check when it reviews a listing? Customer-facing documentation (connection and usage instructions, open network ports, compatible shapes), a Support section with real contact details, and System Requirements listing the OCI components the solution needs. Missing any of these is a common cause of review rounds.

Takeaways

The prerequisites are the hard part. OPN membership, a US-domiciled entity for paid listings, an Ashburn-subscribed tenancy, the OCMA, the IAM policy, and a complete supplier record all gate your first paid deal.
Pick a listing type and a pricing model. Click-to-deploy for a deployable artifact or lead-generation to start capturing interest; Free, BYOL, Paid, or Private Offer for how you charge.
Understand the money path. Paid and private-offer listings draw down Universal Credits and Oracle remits to you; under BYOL you collect the license directly.
Enable private offers early. Qualification runs two to three weeks, so it cannot wait for a deal that is already moving.
Check the 25% cap first. A buyer can spend less than a quarter of their Universal Credits commit on marketplace partner products, and your offer counts toward it.
Build the listing to pass review — real documentation, real support contacts, and complete System Requirements — so it does not bounce back for a second round.

See how Suger lists, transacts, and reconciles across every marketplace on the platform overview, or book a demo to map your Oracle motion onto the rest of your Cloud GTM.