Glossary

Cloud Marketplace

Buy and deploy software from inside your cloud console. A cloud marketplace lists third-party products as machine images, containers or SaaS subscriptions, bills them through your cloud account and counts the spend toward your commitments.

General definition

A Cloud Marketplace is the app store of a cloud platform. AWS Marketplace, Microsoft Azure Marketplace and Google Cloud Marketplace list software from third-party vendors in a form that deploys directly into the customer’s account: a virtual machine image, a container or Helm chart, an infrastructure template, or a SaaS subscription. The cloud provider handles billing, so the software appears as a line on the monthly cloud invoice, procurement happens under an agreement the customer already has, and the vendor gets paid without raising its own invoice.

  • Listings: an AWS Marketplace AMI or Azure VM offer is a prebuilt VM image that boots into a configured product; container and Helm listings deploy to a managed Kubernetes cluster; SaaS listings subscribe to the vendor’s hosted service with billing through the cloud account
  • Pricing models: free or bring-your-own-licence, hourly or monthly usage, annual contracts, and usage metering reported by the product
  • Private offers: a negotiated price, term and contract for one customer, published as a private listing they accept in the console
  • Committed-spend burn-down: eligible marketplace purchases count toward the customer’s committed cloud spend under enterprise agreements, so buying through the marketplace uses budget already approved

Buyers like marketplaces for reasons that have little to do with the software. Procurement is already done: the cloud provider is an approved vendor, the terms are standard and legal review is short. Security review is partly done: providers scan images and set security requirements for listings. Deployment is inside the customer’s own account, in a region they choose, within their own virtual private cloud, which satisfies data residency and network policy without the vendor seeing the data. And the spend burns down a commitment that would otherwise be left unused.

For vendors, listing means packaging the product so that it installs without hand-holding, keeping the image or chart current with each release, and accepting the provider’s fee and listing rules. Marketplaces are a channel, not a product: the same software is usually also available as a direct download or a managed service.

In the Ethora ecosystem

Ethora Core is listed on AWS Marketplace as an AMI with a first-boot setup page, plus a CloudFormation template that creates the instance and its surroundings in one step; Azure Marketplace, DigitalOcean, Vultr and Akamai listings are in progress. The marketplace image is the same self-hosted stack as the Docker Compose and Helm installs: the Node.js API and jobs, ejabberd with the Ethora modules, MongoDB, MySQL, Redis, Centrifugo and MinIO behind Caddy, which obtains TLS certificates on first boot. It runs under the Ethora Core Software License, free with per-server limits that rise after free registration.

Deploying from a marketplace keeps the chat server, its data and, with a local model, the AI inference inside your own cloud account and region, which is the usual requirement for healthcare and financial deployments. Teams that want the same outcome without operating it can have Ethora TechOps run a dedicated server in their account with an enterprise SLA. Every install route, from compose files to the Helm chart to marketplace images, is listed on the Get Ethora page, and the self-hosted chat server on AWS page covers the AWS case in detail.

Get started

Chat and AI on infrastructure you control

Run Ethora self-hosted or dedicated, with full control of data, keys and residency. Talk to our team.

Start Free
Free tier available Enterprise SLA No vendor lock-in