Exchange infrastructure — not a marketplace template

Exonome provides the structural foundation for discovery, coordination, and optional transactions through paid offerings — without forcing monetization, scale, or marketplace behavior.

If you’re new to the concept, start with our overview of exchange infrastructure →

What exchange infrastructure means

Exonome is not a marketplace builder, directory template, or payments-first platform.

Exchange infrastructure provides a consistent foundation for discovery, coordination, and optional transactions for paid offerings — governed by the operator.

A single Exchange can support discovery, connection, and paid offerings at the same time, or emphasize only what fits its audience and context.

An Exchange, at a glance

An Exonome Exchange is a shared space where participation and offerings are intentionally curated and governed.

The operator controls who is invited, which offerings are approved, and when different capabilities are enabled.

Providers create offerings, and paid checkout is only introduced when marketplace capabilities are enabled.

How exchanges take shape

An Exchange is configured by operator intent — not by a required sequence. Discovery, Connection, and Marketplace are independent configurations that can exist on their own or together.

🔍

Discovery Exchange

A single provider is surfaced for visibility and inbound interest through link-outs or lead requests — without coordination or transactions.

🔗

Connection Exchange

Operators invite and govern multiple providers. Inquiries, introductions, and participation are enabled without paid transactions.

🧾

Marketplace Exchange

Paid offerings and checkout are enabled. Providers may sell specific offerings while remaining discoverable and contactable.

Not sure where your exchange fits?

Most exchanges don’t start as clean categories. Discovery, coordination, and commerce often exist informally long before structure is introduced.

The Exchange Clarity Tool helps you understand how exchange already works in your network — or what you’re intentionally designing toward — before choosing configuration or capabilities.

Use the Exchange Clarity Tool →

One Exchange, many ways to serve the same audience

Most marketplace platforms are built around a single transaction model — rentals, products, services, or bookings — and force every provider to fit that structure.

Exonome is different. A single Exchange can support multiple offering types at the same time, allowing different providers to serve the same audience in the ways that make sense for them.

Offering types

Offering types define how an end user takes action inside an Exchange. Each type specifies the inputs required to complete that action.

Link-out

No input beyond intent. Redirects the user to an external destination where the action occurs outside the Exchange.

Lead request

Captures contact or inquiry information so the provider can follow up outside of checkout.

Product

Requires the end user to select a quantity before adding the item to cart and completing checkout.

Service

Represents a service-based purchase where checkout confirms intent rather than inventory selection.

Rental

Requires selecting a start date/time and end date/time before proceeding to checkout.

Class

Requires selecting a recurring schedule or session from a dynamic date selector before checkout.

Timed event

Requires selecting a specific event date and time prior to purchasing access.

Ticket

Grants entry or access to an event, typically with quantity selection before checkout.

Subscription

Requires recurring billing consent to provide ongoing access or benefits.

Digital

Delivers gated or downloadable digital content after a completed action or transaction.

Exchange configuration rules

Exchange types determine which offering actions are available to end users and how many providers can participate in the Exchange.

Offering type / rule Discovery Exchange Connection Exchange Marketplace Exchange
Exchange limits
Number of Exchanges allowed 1 Exchange Multiple Exchanges Multiple Exchanges
Exchange ownership Exonome-hosted (shared instance) Operator-owned Operator-owned
Create Exchanges under a platform — ✓ ✓
Provider participation
Providers allowed 1 provider Multiple providers Multiple providers & sellers
Invite / approve providers — ✓ ✓
Offering types (end-user actions)
Link-out ✓ ✓ ✓
Lead request ✓ ✓ ✓
Product (quantity → cart) — — ✓
Service — — ✓
Rental (start / end) — — ✓
Class (schedule selection) — — ✓
Timed event — — ✓
Tickets — — ✓
Subscription — — ✓
Digital download — — ✓

Exchange capabilities by type

Each Exchange type supports a defined set of capabilities. Marketplace Exchanges are a superset — Discovery and Connection never block future expansion.

Capability Discovery Exchange Connection Exchange Marketplace Exchange
Exchange structure
Number of Exchanges 1 (shared instance) Multiple Multiple
Platform ownership Exonome-owned White-label platform owner White-label platform owner
Custom domain Subdomain only *
xxxx.exono.me 		Yes Yes
Exchange Visibility & access
Public access Yes (unlisted URL) Yes (unlisted URL) Yes (unlisted URL)
Access control Public only Public / private Public / private
Provider & seller inclusion
Providers allowed 1 Multiple Multiple
Invite & approve providers — Yes Yes
Provider self-onboarding Yes Yes / mass imports Yes / mass imports
Offerings & end-user actions
Link-out offerings Yes Yes Yes
Lead request offerings Yes Yes Yes
Paid offerings — — Yes
$0 pricing (checkout) — — Yes
Workflows & controls
Provider messaging routing Yes Yes Yes
Offering approval workflow Yes Yes Yes
Seller approvals for authorized payments — — Yes

* Custom subdomains on the shared Discovery instance may require an additional fee.

Scale with flexibility and AI support

Exchanges can grow, enable commerce, or operate under different models, including white-labeled platforms. In any Exchange, AI supports both operators and participants with language, policies, and visual content — while keeping people in control.

Platform integrations

Exonome integrates with external systems based on how an Exchange is configured. Some integrations are available across all Exchange types, while others activate only when specific capabilities are enabled.

Stripe Logo, revised 2016 Stripe

Powers payments, payouts, subscriptions, and transaction flows for paid offerings.

Available only in Marketplace Exchanges.

Google Analytics

Provides web traffic insights and usage visibility through standard analytics reporting.

Supported in Connection and Marketplace Exchanges.

Twilio

Handles messaging, notifications, and SMS routing between operators, providers, and end users.

Used across all Exchange types. Default Exonome accounts may be replaced with dedicated accounts in white-label deployments.

Azure Storage

Stores images, documents, and digital assets used across Exchanges and offerings.

Used across all Exchange types. Default Exonome storage may be replaced with dedicated storage in white-label deployments.

How Exchanges support different user actions

Offering types control user inputs, interface behavior, and checkout requirements — without changing the Exchange, providers, or governance.

Discovery & contact actions

Link-outs and lead requests require minimal input and no checkout.

Scheduled & time-bound actions

Classes, events, and rentals require date or schedule selection.

Transactional actions

Products, services, and subscriptions require checkout and payment.

Marketplace as a superset

Discovery and connection remain available when paid offerings are enabled.

What Exonome never forces

No required commerce

No forced progression

No participation tolls

No growth mandates

No structural lock-in

Talk through your exchange

A short conversation to map structure, configuration, and intent.

Schedule a conversation