PlatformDTC Enters Public Beta

Open to Anyone

PlatformDTC is in public beta. Anyone can create an account at platformdtc.com/register. There is no sales call, no approval queue, no invite code and no waitlist.

Signup ends with something real rather than an empty dashboard. At the end of it there is a working store on a PlatformDTC subdomain, with a default theme already seeded — ready to be edited, rebranded or replaced. It is the same product the merchants already trading on the platform use, not a demo of it.

What signup does not do is put the store in front of shoppers. Building is open to anyone; publishing is what a plan buys. The storefront begins serving the public when a plan starts, and each plan covers one store.

What One Account Covers

The beta is not one feature behind a signup form. A single account covers the working parts of a direct-to-consumer business:

• Storefront and themes: the customer-facing store and the themes it is built from
• Product catalog and the editor: products, variants, and the editor used to build the pages that sell them
• Checkout and payments: taking the order and taking the money
• Subscriptions: recurring plans and the billing that runs them
• Fulfillment and shipping: including branded order tracking the customer sees under the merchant's own brand
• Email and SMS marketing: both channels, in the same account as the store they sell for
• Analytics: reporting over the store's own orders and traffic

Checkout Runs on the Merchant's Domain

Once a custom domain is attached to a store, checkout runs on that domain. The buyer does not get handed off to a third-party address at the moment they are asked to pay. Before a custom domain is attached, checkout runs at platformdtc.com/checkout/<session>.

Express wallets available at checkout in the beta:

• Apple Pay
• Google Pay
• Link
• Amazon Pay
• Klarna

Skills, and Agents That Take Real Actions

Capabilities on PlatformDTC ship as skills. An agent assembled from them does not stop at describing the work — it calls the same systems a person's dashboard calls, through the Agent Gateway. Four things hold on every call that goes through it:

• A scoped key per agent, so an agent's reach is the reach it was granted and nothing wider
• An audit record for every call, so what an agent did is a matter of record rather than of memory
• Idempotency on every write, so a retry repeats the request without repeating the effect
• An approval gate on spend, which parks the action until a person resolves it

The Gateway is documented in public. The developer documentation and the OpenAPI reference are at docs.platformdtc.com, and both are readable without an account — you can see exactly what an agent is able to do before you create one.

What We Publish About Reliability

status.platformdtc.com publishes the live state of the surfaces that are probed: storefronts, checkout, the dashboard, the core API, notifications and the documentation. Each component is listed with its p50 and p95 response times, not just a colour.

That is deliberately a partial picture, and the page says so on its face: background jobs and analytics are not probed yet. We would rather name the gap than let a page of green marks imply coverage we have not built.

Beta in the Honest Sense

Calling this a beta is not a disclaimer bolted onto a finished product. Things will change: behaviour will be corrected, defaults will move, and surfaces will be reworked as merchants use them in ways we did not anticipate.

Notable changes are written down in a merchant-facing changelog, so a change that affects a store is something a merchant can read rather than something they discover.

Every plan is paid and priced per store. The plans, and what the first month costs, are listed at platformdtc.com/pricing.

Start

The fastest way to judge the platform is to stand a store up in it. Sign up at platformdtc.com/register.