COMMERCE, FROM THE CORE UPRust/PostgreSQL/Wasm apps/MCP + UCP/Local LLMs
Source release · 9 October 2026
One commerce core. Connected intelligence.
Reviewed source facts, current-right agent tools and graph-native apps
share the same commerce owners. Read the complete change record, actual
integration checks and the remaining release boundaries.
A fashion shop. A visual app builder. Knowledge, flows and controlled
releases. Six real workflows, recorded inside Vendune.
Actual product recordingsEnglish interfaceSimulated commerce
01 / SHOP & CHECKOUT28 sec · Recorded UI
Native SKU → reviewed quote → saved order
From a coat to a confirmed order.
Choose a real SKU, review the server-calculated quote and complete a
simulated order. Product, stock, checkout and order history share the
same commerce core.
Add UI blocks, inspect their properties and undo or redo your changes.
App Studio uses the versioned data, API and interface schema that
coding agents use too.
Design preview uses explicitly labelled sample data. This clip does
not show a paid coding-agent call.
03 / SHOP KNOWLEDGE6 sec · Recorded UI
Private source → publication review → public knowledge
Give your shop knowledge it can use.
Move a fictional care document through the publication decision.
Sources retain their origin and visibility; private information does
not become customer knowledge just because it was uploaded.
Native knowledge workflow; no model-training or external inference
result is claimed.
04 / FLOW BUILDER8 sec · Recorded UI
Order event → rule branch → durable actions
Branch. Wait. Act.
Explore a saved six-step order flow with conditions, two branches, a
durable delay and document generation. Native actions and declared app
capabilities live in the same graphical workspace.
Editor walkthrough. This recording does not assert external email or
Slack delivery.
05 / STAGING & RELEASE6 sec · Recorded UI
Private sandbox → selected app version → release
Ship one change. Keep the rest private.
Publish the selected versioned app package from a private sandbox.
Separate app-record data stays in staging instead of being silently
copied into the live shop.
Actual selective package release in a synthetic shop; no production
tenant was modified.
06 / MULTILINGUAL CATALOG5 sec · Recorded UI
Saved translations → one language selector → Markdown
One field. Every language.
Switch between saved product translations, then open their Markdown
source. A single content-language control keeps the product editor
focused while the shop language provides inheritance.
One million products plus one million translations in PostgreSQL. Release
build. Fixed arrivals of 500 requests/s. Every response checked.
1M PRODUCTS / 50-PRODUCT PAGE12.9ms p95
500 offered requests/s · real HTTP + PostgreSQL
20-LINE CART / 1M PRODUCTS21.4ms p95
500 offered requests/s · full validated quote
DURABLE CHECKOUT17.7ms p95
500 offered requests/s · fresh durable orders
One core. Every interface.
Give agents tools. Keep the keys.
The browser, an MCP client and UCP checkout reach the same commerce
operations. Permissions stay in the server. Follow the request, checkout,
tenant security and intelligence paths in the
illustrated architecture guide. The core hardening review
explains trusted identity, shared resource limits, transaction-local
tenant scope and recoverable event processing, including the deployment
cutover.