Skip to main content

AWS Marketplace SaaS: A Practical Guide for ISVs to Publish

Marina Campos
Marina CamposJuly 6, 20265 min. read
AWS Marketplace SaaS: A Practical Guide for ISVs to Publish

ISVs that close enterprise contracts outside cloud marketplaces take an average of 9 to 12 months from first commercial contact to signature. On AWS Marketplace SaaS, the same cycle can be compressed to weeks. Procurement is already resolved. The budget is pre-approved. Security compliance has already been audited by AWS. The sale shifts from an internal buyer persuasion process to a transaction inside an environment they already know and trust.

What Is AWS Marketplace SaaS and Why Should ISVs Care?

AWS Marketplace is a curated digital catalog where corporate customers find, buy, and provision third-party software directly through AWS infrastructure. For the ISV, listing the product as SaaS on AWS Marketplace means accessing thousands of enterprise accounts with committed AWS budgets and shortened procurement cycles. The transaction happens within the cloud contract the customer already has with Amazon. Billing is consolidated. Invoicing, compliance, and renewal leave the negotiation table and become an automated flow. AppDynamics reported a 5x higher average ticket on AWS Marketplace transactions compared to the direct channel. Tigera states that contract signing cycles were cut in half.

What Are the Prerequisites for Listing a SaaS Product on AWS Marketplace?

Listing a SaaS product on AWS Marketplace requires four basic conditions. First, an active AWS account in good standing. Second, the software must be a complete, production-ready SaaS product. AWS does not accept MVPs or beta versions as public listings. Third, a documented customer support process with defined channels and a clear SLA. Fourth, for paid products, the ISV must be domiciled in or be a citizen of an eligible jurisdiction. The AWS list includes the United States, United Kingdom, European Union, Australia, Japan, South Korea, India, Israel, Switzerland, Norway, United Arab Emirates, Qatar, Bahrain, New Zealand, Hong Kong, and Colombia.

Free or BYOL products have lighter requirements. For paid software, the seller must provide a tax form (W-9 for US companies, W-8 for foreign companies) and a bank account in an eligible jurisdiction that accepts USD disbursements.

How Does the Seller Registration Process Work on AWS Marketplace?

Seller registration follows five steps in the AWS Marketplace Management Portal.

  1. Access the portal in Partner Central with the AWS account that will be linked to the selling operation. AWS recommends using IAM roles, not root credentials.
  2. Select the seller type: Independent Software Vendor (ISV), Channel Partner, Managed Service Provider, or Individual. Most readers of this guide qualify as ISV.
  3. Fill in the company's legal data, including legal name, tax address, and banking information for disbursement.
  4. For paid products, submit the tax form and go through the KYC (Know Your Customer) process if selling to customers in Europe, the Middle East, and Africa.
  5. Accept the AWS Marketplace Seller Agreement terms and wait for approval, which can take a few business days; seller reports indicate 2 to 5 days.

The AWS Marketplace Management Portal is the central interface for creating listings, configuring prices, managing private offers, and tracking sales metrics.

What Pricing Models Does AWS Marketplace Offer for SaaS?

The choice of pricing model is the most critical decision in the listing process. Once defined and published in limited mode, the model cannot be changed. Reverting requires creating a new product from scratch.

ModelDescriptionWhen to Use
SaaS SubscriptionsHourly usage-based billing (pay-as-you-go). The customer pays for actual consumption.Products with variable usage, where value lies in processing volume or number of API calls.
SaaS ContractsUpfront billing for a contracted period (1 month, 12 months, 24 months, 36 months). Single or installment payment.Products with predictable ticket sizes, where customers want cost predictability and ISVs want guaranteed recurrence.
SaaS Contracts with Pay-as-You-GoBase contract plus additional measured consumption billed separately.Products with a contracted baseline and usage spikes above the contract.
SaaS FreeAll pricing dimensions at USD 0.00. No cost to the customer.Freemium products, service-supported open source, or free tier as a gateway to private offers.

All models support free trials. AWS charges no listing fee. The marketplace revenue model is based on a referral fee on each transaction, with a percentage that varies by product category and pricing type.

How Does Billing and Metering Integration Work for SaaS Products?

Technical integration with AWS Marketplace depends on the chosen pricing model. For SaaS Subscriptions, the ISV must integrate with the AWS Marketplace Metering Service, calling the BatchMeterUsage API to report hourly consumption. Every missed hour is lost. There is no retroactive billing. For SaaS Contracts, integration is with the AWS Marketplace Entitlement Service via GetEntitlements, which verifies whether the customer has an active contract and which entitlements are enabled. For Contracts with Pay-as-You-Go, both APIs are required.

Beyond billing integration, every SaaS product must implement an onboarding flow. The customer purchases on the marketplace and is redirected to a registration page maintained by the ISV. This page must validate the purchase token, create the account in the ISV's system, and connect the AWS billing identifier to the customer profile. The registration page must include a buyer email field and support at least an English view, even if the product is in another language.

Sellers also need to subscribe to Amazon SNS topics (being gradually replaced by Amazon EventBridge for new listings) to handle lifecycle events: new subscription, cancellation, plan change, and contract expiration. These events trigger automated actions such as granting access, suspending users, and notifying the customer.

What Security and Governance Requirements Does AWS Marketplace Impose?

AWS Marketplace imposes a governance regime with 10 mandatory requirements for SaaS products. Key ones include data encryption in transit and at rest using industry standards, complete data isolation between customers (tenant isolation), mandatory authentication before any access to customer data, and security event audit logging with a minimum retention of 1 year.

The seller must disclose their data handling practices (collection, storage, usage, sharing, and retention) in documentation accessible to the customer. They must delete customer data when it is no longer needed or when the customer requests it, within the timeframe stipulated in the EULA. They must notify affected customers about relevant security incidents. They must maintain a documented process for customers to report incidents.

For products that run entirely on AWS, the marketplace grants a special designation in search results. To obtain it, the ISV must submit an architecture diagram (non-public, for AWS review only) demonstrating that the application plane and control plane operate exclusively on AWS infrastructure. The rule took effect in May 2025.

Products that fail to meet these requirements may be temporarily removed from search until corrected.

How Does the AWS European Sovereign Cloud Affect SaaS Distribution?

The AWS European Sovereign Cloud is an isolated infrastructure, operated by European personnel, with full data residency within the European Union. It was announced in October 2023 with an investment of EUR 7.8 billion and a planned launch in 2025, starting with the Brandenburg region in Germany.

For ISVs selling SaaS, the direct impact is the requirement for a separate listing. The European Sovereign Cloud operates in physically distinct regions from AWS commercial infrastructure. A product listed on AWS Marketplace SaaS commercial does not automatically appear on the European Sovereign Cloud. The ISV that wants to serve European government customers and regulated sectors (defense, healthcare, finance, critical infrastructure) must create a dedicated listing, with the same SaaS integration but targeting this sovereign infrastructure.

The listing process is similar, but data residency and access control criteria are more rigorous. AWS requires that product support and maintenance operations be executed exclusively by personnel located in the EU. This operational barrier is significant for ISVs with teams distributed outside Europe.

How Much Does It Cost to Sell on AWS Marketplace?

AWS charges no listing fee or monthly fee. The cost is variable and based on a referral fee on each closed transaction, with a percentage that varies by category. For general software, market practice indicates percentages between 3% and 5% of net revenue. The ISV pays nothing to list, nothing to keep the product published, and nothing for unconverted private offers.

The real cost, however, lies in integration. Implementing the SaaS Subscriptions or SaaS Contracts flow requires API development. Typically 2 to 6 weeks of engineering, depending on pricing complexity. Customer onboarding, SNS/EventBridge integration, and homologation testing with the AWS Seller Operations team consume another 2 to 4 weeks. The total engineering investment rarely falls below USD 30,000 for a mid-sized ISV, based on reports from ISVs and specialized integrators.

AWS offers the List & Sell Incentive program, which covers part of the listing costs for new sellers and for expansion into new countries. Reimbursement is processed via the AWS Partner Network.

Cloud Marketplace vs. Direct Sales: Which Channel to Choose?

The answer is not binary. AWS Marketplace SaaS does not replace direct sales. It accelerates them.

The direct channel offers total control over pricing, negotiation, and relationships. But it imposes on the ISV the cost of enterprise procurement: legal review, security questionnaire, vendor assessment, procurement process. Each step adds weeks to the sales cycle and requires active participation from the sales team.

AWS Marketplace SaaS eliminates these steps for transactions covered by the customer's cloud budget. The software is purchased as an AWS service, within the umbrella contract the customer already has. For the ISV, the advantage lies in closing speed and reduced friction. For the customer's CFO, it lies in consolidating software spend within the AWS consumption commitment, often offsetting the value against EDP (Enterprise Discount Program) credits.

The model that works for most B2B ISVs is hybrid: keep the direct channel for strategic customers who require custom negotiation and use the marketplace as a scalable acquisition channel for customers already in the AWS ecosystem. In this configuration, the marketplace does not compete with the sales team. It feeds the pipeline.

Frequently Asked Questions

Do I need my SaaS hosted on AWS to list on AWS Marketplace?

Not necessarily for listing. But to receive the special "deployed on AWS" designation in search results (which increases visibility), the product must run entirely on AWS infrastructure, both application plane and control plane.

Can I change the pricing model after publishing?

No. Once the product is published in limited mode with a pricing model, it cannot be changed. If there is an error in the initial choice, the ISV must create a new product with the correct model and migrate customers.

How long does it take for a SaaS product to be approved on AWS Marketplace?

Initial seller registration can take a few business days; seller reports indicate 2 to 5 days. Product creation and review by the AWS Seller Operations team take an additional 5 to 15 business days, depending on integration complexity and the quality of submitted documentation.

Does AWS Marketplace work for Latin American ISVs?

Brazil and most Latin American countries are not on the list of eligible jurisdictions for paid product sellers on AWS Marketplace. Latin American ISVs can list free products or operate through a subsidiary in an eligible jurisdiction, such as the United States or the European Union. To sell SaaS in Brazil in local currency with tax documentation, alternatives such as Nexforce Marketplace offer cloud marketplace distribution with settlement in BRL. The RevOps consulting team assists ISVs in structuring the marketplace channel within Brazilian financial operations.

This article covers the process of listing SaaS products on AWS Marketplace. It does not address alternatives such as Microsoft Azure Marketplace, Google Cloud Marketplace, or marketplace strategies as a complementary acquisition channel to resellers. It also does not cover the specific integration with AWS PrivateLink for delivery via VPC endpoint, nor the listing process for AMI-based products and container products. Each format has its own set of rules and security requirements.

ISVs seeking to distribute SaaS via cloud marketplaces and needing local presence in Latin America, with tax documentation, local currency billing, and centralized procurement management, find in Nexforce Marketplace a complementary path to the AWS ecosystem. The platform eliminates the need to establish an international subsidiary solely to enable marketplace sales. For deeper analysis on SaaS distribution and tax compliance in Latin America, the Nexforce blog publishes updated guides focused on B2B operations.

References and Further Reading