Test ideas in real workflows
Try AI advice, new shopping experiences and automated processes. The measure: does the idea actually help merchants and customers?
Veyndo is Stefan’s experiment platform for the next generation of e-commerce. AI, new shopping experiences and merchant workflows can be explored directly in a working commerce system.
Working prototype · developed in public

Veyndo is neither a competitor nor a replacement for Shopware. It is a development workshop where new products, services and approaches to commerce can take shape. Ideas that prove useful can inspire Shopware.
Try AI advice, new shopping experiences and automated processes. The measure: does the idea actually help merchants and customers?
Modern technology and public development can attract additional developer communities. Contributions, extensions and actual use matter more than stars alone.
Offer Shopware Payments through new products, standalone experiences and agentic workflows. Its provider integration remains a separate private service.
Storyfront shapes the shopping experience. Veyndo keeps commerce data authoritative. Each studio owns its part, connected through the same integrated interfaces.
Create a shop and manage it in Veyndo Studio.
experience.veyndo.aiConnect brand and catalog, edit in the original Storyfront Studio and publish.
Products, variants, prices, stock, customers, taxes, cart and orders.
Original Studio & rendererBrand, knowledge, questions, scenes, design, preview and publication.
Presentation and commerce stay connected: Storyfront can shape product stories, but editable narrative text cannot overwrite prices, stock or orders.
“Prepare my new collection for France.”
Products, documents, shop knowledge and existing workflows provide context.
AI can prepare content, translations or actions. Knowledge and proposals do not mean an autonomously trained, all-purpose intelligence.
Changes pass through permissions, preview and approval. Prices and orders remain authoritative in the core.
Four refreshed films follow the shared platform, product work, a product advisor app and contextual AI.
Merchant intake, shop knowledge, design references, app assistance and fictional buyer scenarios.
The video could not load. Open the download link or reload this page.
Produced 2 November from actual native Studio captures made that day. Editorial still sequences with fictional data and simulated payments. English titles and subtitles.
Follow a wool coat through merchant tools, a saved advisor record, the visual shop canvas and native checkout.
The video could not load. Open the download link or reload this page.
Produced 2 November from actual native Studio captures made that day. Editorial still sequences with fictional data and simulated payments. English titles and subtitles.
Product content, media, SEO, recommendations, the shared design canvas and selected publication.
The video could not load. Open the download link or reload this page.
Produced 2 November from actual native Studio captures made that day. Editorial still sequences with fictional data and simulated payments. English titles and subtitles.
App placements, graphical editing, contextual assistance, installation settings, data relationships and an actual saved care record.
The video could not load. Open the download link or reload this page.
Produced 2 November from actual native Studio captures made that day. Editorial still sequences with fictional data and simulated payments. English titles and subtitles.
Explore product editing, shop knowledge, App Studio and the shared shop canvas in the current native interface.
Choose the route that fits your question. Use your own test data and check that payments are configured as simulations.
Create an account or sign in. Choose an empty shop or sample products. Edit a product in Studio and open the shop.
Try a shopProvide a brand and reviewed catalog: images, CSV/Excel, product URLs or proposed AI demo products. Review the import, edit in the original Studio, test the preview and deliberately publish.
Try an experienceAdd a demo product, open the cart and finish the simulated checkout. Check the order and customer association in that shop’s Veyndo Studio.
Check a purchaseExisting public experiments may use different generations of the renderer. The tour provides a traceable reference for the current native connection.
From shops to platform operations. Protected areas require an authorized personal account.
The classic SaaS entry without automatically provisioning Storyfront.
start.veyndo.aiOnboarding and access to the connected original Storyfront Studio.
experience.veyndo.aiManage an existing shop; choose the relevant shop after signing in.
app.veyndo.aiOperator area for shops and platform operations. Authorized team members only.
app.veyndo.aiCommerce core, changes, issues and contributions on GitHub.
github.comUnderstand architecture, features, interfaces and boundaries.
www.veyndo.aiPeople and coding agents work on the same versioned app contract.
www.veyndo.aiMathematically checked properties of selected critical rules.
github.comAI connects to products, documents, shop knowledge, apps and workflows. A merchant describes a goal and the system prepares concrete proposals. It does not mean unlimited self-learning intelligence or uncontrolled changes.
Storefronts, apps and agents use the same commerce functions. Prices, stock, taxes, permissions and orders are checked centrally. Rust alone does not prove a particular speed improvement; that requires comparable measurements.
App Studio can describe data, API, admin, storefront and AI features. Versioned packages can be tested in a private environment and rolled out selectively. External apps remain language-independent; the core stays authoritative.
No. Veyndo is a working prototype. Broad production readiness, community impact and each external provider path must prove themselves separately. Verified demo workflows do not establish real payment settlement.
The public core provides a general payment-provider contract. The specific Shopware Payments implementation remains private and needs authorized provider configuration, merchant assignment and verified onboarding. A demo order does not confirm a payment.
Lean checks properties of selected critical rules, such as stock or refund limits. These bounded proofs do not replace integration tests or guarantee a completely bug-free system.
Bring a merchant task, a shopping idea or an app idea. Test a concrete workflow and tell us where it helps — and where it still gets in the way.
Start with a shopExplore the project