Skip to main content

​
What this is

When a customer purchases MagOneAI through a public cloud marketplace, they can onboard themselves without a manual setup call. The purchase provisions (or links) their organization and applies the plan’s usage entitlement automatically, and billing lifecycle events keep that entitlement in sync as the subscription changes.
This is billing and procurement onboarding, not an in-app catalog. There is no marketplace of templates, prebuilt agents, or workflows to browse and install inside MagOneAI. “Cloud Marketplace” here means the AWS, Azure, and GCP marketplaces where a customer buys the MagOneAI subscription itself.
A marketplace purchase is an onboarding channel, not an authentication method. It never changes how anyone signs in: after onboarding, the customer logs in exactly like any other user, with email and password or SSO. The shipped login and signup flows are untouched.

​
Providers

MagOneAI ships adapters for three marketplaces:

AWS

Live. Purchase and lifecycle flow through the AWS Marketplace with entitlement-gated go-live.

Azure

In preview. Adapter for the Azure Commercial Marketplace SaaS offer.

Google Cloud

In preview. Adapter for Google Cloud Marketplace (Producer Portal).
Every provider is disabled by default and must be turned on individually by a superadmin. Until a marketplace is enabled, its landing endpoint does not resolve purchases.

​
How onboarding works

1

Customer buys on the marketplace

The customer completes the purchase on AWS, Azure, or GCP and is redirected to MagOneAI with a marketplace token.
2

MagOneAI resolves the purchase

The landing endpoint verifies the token server-side and records a normalized subscription. The token never reaches the browser: the customer is handed only a single-use, short-lived registration link.
3

Customer registers or links an org

From the registration page, the customer either provisions a brand-new organization (standard signup) or links the subscription to an organization they already own. Linking to an existing org requires the caller to be an OWNER of that org.
4

Entitlement is applied

Once the subscription is activated with the marketplace, the plan is mapped to a usage entitlement and applied to the organization as its default token limit. The customer then lands in a normal, signed-in session.
For AWS, an organization is entitled only once the marketplace confirms the purchased dimension (surfaced by a lifecycle event), never at registration alone. This keeps a customer from being provisioned ahead of the confirmed purchase.

​
Staying in sync

A subscription is not a one-time event. MagOneAI listens for the marketplace’s billing lifecycle notifications and moves the subscription and its entitlement accordingly: Redelivered notifications are safe: events are de-duplicated, so re-processing the same message does not double-apply an entitlement or corrupt state.

​
The entitlement

The plan-to-entitlement mapping resolves to an organization-default token limit - the same usage quota mechanism used everywhere else on the platform. A plan can grant a finite token budget or be unlimited. Suspension and cancellation drop the org to the free-tier floor rather than deleting anything.
Entitlements are token-limit only in this integration. A plan does not toggle feature flags or unlock modules; it sets the org’s token allowance.
An unmapped plan does not fail onboarding: the org onboards with the platform default entitlement and the gap is logged for an admin to reconcile.

​
Configuration (superadmin)

Cloud Marketplace onboarding is configured entirely by platform superadmins, not by org admins or end users. Two things are managed:

Enable flags

Turn each marketplace (AWS, Azure, GCP) on or off. All are off by default.

Plan map

Map each marketplace plan to the entitlement applied to the buyer’s org. Unmapped plans fall back to the platform default.
Provider credentials are stored in HashiCorp Vault under a platform-scoped path, never in the database or the workflow definition.

​
What is out of scope

To set expectations clearly, this integration deliberately does not cover:
  • An in-app marketplace of templates, agents, or workflows to install.
  • Metering or usage-based (consumption) billing back to the marketplace.
  • Private offers.
  • In-app plan self-service (changing plans from inside MagOneAI).
  • Marketplaces other than AWS, Azure, and GCP.

​
Next steps

Usage & quotas

How the token entitlement a plan grants is enforced across the org

Admin Portal

Where superadmins manage the platform, including marketplace configuration

Organizations & projects

The org that a marketplace purchase provisions or links to

Secrets & Vault

Where marketplace provider credentials are stored