Oracle Marketplace

Oracle Cloud Marketplace is the narrowest integration in this documentation, and knowing its boundaries up front will save you a planning cycle. Suger does not create Oracle listings — you publish them in the Oracle Cloud Marketplace Partner Portal and Suger imports them, hourly, as products you can transact against. Only SaaS listings sync; container images, machine images, stacks, and Helm charts are skipped. Buyers are identified by their tenancy OCID, and every offer carries a contract document as a PDF.

What Suger adds is the private offer motion: a single total contract value in USD over a fixed term, sent from the console and tracked through acceptance. Pricing is one-time by design — there are no installments, and usage metering, while built, is not yet switched on. Connecting is organization-wide and uses an OCI API signing key belonging to a dedicated, least-privilege IAM user in your tenancy.

Connect and start transacting

1. Integration — create the least-privilege IAM user, grant it Marketplace Publisher permissions, and connect with an unencrypted API signing key.
2. List Product — how the hourly sync imports your published SaaS listings as Suger products, how Oracle lifecycle states map to Suger product statuses, and how to force a sync after publishing.
3. Private Offers — send an offer to a buyer’s tenancy: total contract value, a term of 6 months, 1, 2, or 3 years, and the EULA PDF Oracle requires.

Know what is and is not supported yet

• Usage Metering — how Oracle metering will behave once Suger enables it, and the one rule that differs from every other cloud: you report a monetary amount, not a quantity.
• FAQ — short answers to the questions that come up in practice, including why an offer can sit in Pending Create, what makes integration verification fail, and how to rotate the API signing key.

Scope and limits