Plan draft
05 / Commerce & subscriptions

Commerce, without the complexity tax.

The planned commercial layer for product plans, subscriptions, invoices, pricing state and payment integration.

The intent

Connect value with commerce.

Merchant is intended to separate the business meaning of a subscription from how usage is measured or access is granted. That separation can help teams evolve their commercial model without tying every other subsystem to a billing vendor.

For platforms that need pricing and subscription operations with explicit ownership.

01

Plans & subscriptions

A planned source of truth for commercial packages and recurring relationships.

02

Invoices & payments

Commercial documents and payment orchestration as distinct bounded capabilities.

03

Pricing state

Explicit models for rates, currencies and offer evolution.

04

Product interoperability

Commercial signals designed to work alongside Gauge and Sentinel — not replace them.

Architecture perspective

Designed as a clear sequence.

A conceptual workflow that illustrates the product direction — not a claim of complete implementation.

01 /

Define an offer

02 /

Manage subscriptions

03 /

Reconcile commercial state

Development transparency

Where it stands today.

Plan draft

Merchant remains in Plan Draft. Commercial boundaries are described for portfolio clarity, not as a currently available product.

CONTINUE EXPLORING / 06

Surveillance — Observability & evidence.

Discover the product