VEYNDO

Run a shop.
Build what it needs.

Veyndo is an AI native commerce platform built in Rust. Your storefront, Studio, apps and agents work with the same products, permissions and orders.

Überblick auf Deutsch · Architecture & SDK · Current platform status

Veyndo storefront with a Product Guide in the shopper conversation and a reviewed cart offer
From product advice to a reviewed cart in the hosted Lumen shop. 11 November 2026.

Choose where to start

Open a shop

Start with a catalog, test checkout and use Studio to manage products, orders and releases.

Create a shop

Design a Storyfront

Build an Experience with Storyfront and use Veyndo for stock, price, checkout and orders.

Open Experience Studio

Many interfaces.
One shop.

Your own storefront, Storyfront, Studio and agents all work with the same catalog, stock and orders. Use the JavaScript SDK to build your interface. Connect individual services where your project needs them.

Storefront & Storyfront Studio & POS Apps & agents
SDK over HTTP · MCP tools
Commerce Core Catalog · Pricing · Inventory · Orders
Checkout & Payments
Review, confirm and recover a purchase.
Apps & Connectors
Run workflows and deliver to external systems.
Knowledge
Give interfaces and agents shop context.
Core commits the order, stock movement and event together. That event can start a Flow for invoicing or delivery.

What you can build

Start with the whole shop or use a component with the system you already run.

A storefront and merchant workspace

Manage a catalog, channel pricing, customers and orders in Studio. Build a storefront, run a register or import marketplace orders against shared inventory.

Explore the feature guide

Apps inside the conversation

Shoppers can filter an app result, choose a variant and review its price and delivery before adding it to the cart. Merchants can inspect private app data and approve a proposal in a sandbox.

Build an interactive Product Guide

Rules and background work

Connect commerce events, rules and app actions in Flows. Core commits the order and stock together. Workers handle follow-up activity such as connector delivery.

Explore rules and Flows

A shop built from components

Use the shared Rust contracts or connect independent services through HTTP and MCP. The commerce host keeps authoritative prices, inventory and orders.

See the component map

Verified in the hosted shop

The Lumen pilot brings eight services together. The release record links the running versions, instance checks and tested shop journeys. Native and Storyfront purchases completed with PayPal Sandbox refunds.

Order confirmation for a simulated purchase in the native Veyndo storefront
One stock ledger. A native simulated purchase consumed the last unit. Storyfront showed the item as sold out after reload.
Studio showing a private Product Guide table and an approved change in a sandbox
One reviewed Studio change. A merchant applied a proposal based on a private app note in the sandbox.

See the variant review · Read the current acceptance record · Check shared migrations · View the release inventory

Try the workflows yourself

Run the local playground

Place a simulated order, inspect it in Studio and publish a selected catalog change.

Open the playground guide

Four product films

Actual native Studio captures from 2 November 2026. English subtitles, no sound. Follow the shared canvas, product work, a product advisor app and contextual AI.

Earlier workflow recordings, captured 13 October 2026

13 October 2026

One core.
More possibilities.

Three earlier connected tours, retained with their original capture date. Actual UI, readable English captions and no sound. Choose a tour or jump to a chapter.

Real application recordings1080p · English captionsLocal synthetic shops
CONNECTED COMMERCE0:38 · Actual UI

POS → shared native order · Company → unit → budget

Shared orders. Controlled purchasing.

One catalogue. Shared orders. Controlled business purchasing.

Actual UI screencast. A cash sale was recorded only in an isolated synthetic shop; no fiscal-device or external EDI delivery is demonstrated.

BUILD AND AUTOMATE0:29 · Actual UI

App draft → private preview → selected product release

Build it. Test it. Publish deliberately.

Typed apps. Visible workflows. Deliberate releases.

Editorial sequence of fresh actual UI stills. An app draft version, an unsaved Flow edit and a selected product release are shown as distinct operations.

CONNECTED INTELLIGENCE0:50 · Actual UI

Sources → review → explicit autonomy limits

Knowledge with explicit boundaries.

Connected knowledge. Reviewed sources. Explicit limits.

Actual UI screencast of reviewed synthetic knowledge and explicit autonomy limits. No continuous business optimization or model training is demonstrated.

The product. In motion.

See what you
can actually build.

A fashion shop. A visual app builder. Knowledge, flows and controlled releases. Six real workflows, recorded inside Veyndo.

Actual product recordingsEnglish interfaceSimulated commerce
02 / APP STUDIO45 sec · Recorded UI

Visual canvas → component properties → undo / redo

Build the interface. Keep the contract.

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 KNOWLEDGE50 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 BUILDER24 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 & RELEASE20 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 CATALOG18 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.

Displays existing translated content; switching language does not trigger an AI translation call.