AI-operable commerce · Configured on your production server
Configure commerce on your own APPSS runtime application server for production, with a storefront hosted on Cloudflare. Shape it in a few prompts, connect your own payment provider and keep adapting the configuration as your business changes.
Not vibe coding. Adaptable configuration. Your choice of AI.
“Configure our own Shopify-style store on the APPSS production runtime. Products, variants, cart and checkout with our own payment provider. Make it unmistakably ours.”
Everyday objects. Extraordinary by design.
Considered essentials, made for your everyday.Interactive concept of an APPSS runtime configuration. The prompts illustrate your intended setup and interfaces; this page does not provision a customer server.
Your commerce behaviour is configuration on the APPSS runtime application server. Cloudflare hosts the experience. DataInbox controls web agents, chats and messages with partners and customers. Adapt the configuration without rebuilding your tech stack.
Cloudflare
APPSS runtime
DataInboxCloudflare hosting. APPSS production runtime. DataInbox agent and conversation control. Your own payment provider.
Get out of SaaS limitations
Your investment grows your business. Paying more for the same service as a result is a SaaS model we can rethink in the AI era.
Your growth should grow your business. Not your SaaS bill.
Your catalogue, pricing, approvals and order flows are configuration on the existing APPSS production runtime. Adjust that configuration as your business evolves. You are shaping business behaviour, not maintaining a new AI-generated codebase.
Always adaptable configurationKeep your commerce configuration, business rules and data on the APPSS runtime. Connect compatible agents and AI providers through agreed API, MCP and CLI interfaces. Choose and change AI connections while keeping your business configuration in your own runtime.
Your rules, your choice of AIStop paying more for the same service just because your business grows. APPSS has no fee per user, employee, revenue or transaction. Agree server capacity, usage, AI and payment-provider costs explicitly, and keep control of access, export and handover.
Growth without a per-user SaaS billSaaS & Big Tech · The value of your growth
Easy to start. Fun to use. Your business data, customer relationships and revenue are valuable assets. Keep control of how they are used, connected and priced as your business grows.
| What matters |  Shopify · SaaS reference | APPSS · Your runtime |
|---|---|---|
| The cost of growth | A plan subscription, payment charges and any paid apps. An external payment provider can add a Shopify percentage of transaction value. | No APPSS fee per user, employee, revenue or transaction. Capacity, usage and external services are explicitly agreed. |
| Your business rules | Configure the platform and extend it with apps, APIs and custom integrations. Options depend on the plan and extension. | Adjust business behaviour as configuration on your existing production runtime. AI helps shape and operate it within your permissions. |
| Your payment provider | Choose a supported provider. External-provider transaction fees can apply on top of the provider’s own charges. | Connect your chosen provider to the APPSS runtime. Keep your merchant relationship and pay the agreed provider and integration costs. |
| AI and MCP | Already supports AI, APIs, CLI and MCP. Multiple shopping capabilities share one merchant MCP endpoint. | Proposed API, MCP and CLI contracts expose the runtime’s permitted actions. Connect compatible AI providers through agreed interfaces. |
| Data and your exit path | CSV exports are available for products, customers and orders. A complete move can still require work on apps, settings and data. | Agree data access, exports, configuration deliverables and handover for your runtime. Keep your business model separate from individual AI providers. |
| Who runs the operation | Shopify hosts and operates its commerce platform. You manage the store, settings and selected apps. | Cloudflare hosts the storefront. APPSS runs commerce and business rules. DataInbox controls web agents, chats and messages. |
Shopify is one concrete SaaS reference. The APPSS column describes the proposed commerce configuration; the scope and connections are agreed for your business.
Example: €100,000 in monthly transaction value subject to Shopify’s external-provider fee. The last column is the additional Shopify fee alone, before the payment provider’s own costs.
| Plan | Per month, billed yearly | Billed monthly | External-provider fee | Extra fee at €100,000/month |
|---|---|---|---|---|
| Basic | €21 | €28 | 2% | €2,000 |
| Grow | €59 | €78 | 1% | €1,000 |
| Advanced | €289 | €384 | 0.6% | €600 |
| Plus | By contract | From €2,100 | 0.2% | €200 |
Netherlands, EUR. Standard subscription prices, excluding introductory offers. Fees apply where eligible; exceptions and provider terms matter. Paid apps, payment processing and your own agent costs are additional where used. Checked 1 November 2026.
Shopify also offers an Agentic plan with no monthly subscription for selling through AI channels from an existing platform. It does not include publishing a Shopify online store; payment and other applicable costs remain.
The APPSS runtime foundation
This is the existing Dedicated as a Service runtime starting price. Your commerce configuration, Cloudflare, DataInbox, AI and payment connections are scoped in the proposal. This is not a complete commerce quote or a claim of guaranteed savings.
From€295/month
View APPSS pricingStop paying a software premium simply for growing. Get your freedom to operate.
AI operable. Under your control.
Configure and operate the APPSS runtime through API, MCP and CLI. People, systems and authorised agents work with the same business rules. Explore the proposed interfaces.
Create an order on the APPSS runtime from your storefront, partner portal or ERP using a documented API contract.
POST /api/v1/orders
Authorization: Bearer <scoped-token>
{
"customer": "customer_001",
"items": [{ "sku": "bottle-01", "quantity": 2 }],
"priceList": "wholesale"
}Illustrative API, MCP and CLI contracts for configuring and operating the APPSS runtime. These examples describe intended interfaces, not a generated application codebase or live endpoints on this page.
From familiar commerce to your own platform
Configure the commerce capabilities your business needs on the existing APPSS runtime. Start with an agreed scope, connect your services and adapt the configuration as you grow.
APPSSShopify is a reference for the concept. This is an independent APPSS proposal, with no Shopify affiliation or endorsement.
Commerce on APPSS runtime + Cloudflare. Agents and conversations through DataInbox.
Integrated with your own payment service provider
Configure the connection between your payment service provider and the APPSS runtime. Keep your merchant relationship and shape checkout around your business, with payments, refunds and verified payment updates in your order flow.
No. You configure commerce behaviour on an existing APPSS runtime application server for production. AI helps express and adjust the configuration and can operate permitted actions through the agreed interfaces. The runtime executes the configured rules. Scope, service connections and production checks are agreed for your application; the concept does not promise complete Shopify feature parity.
Cloudflare hosts the experience. Your APPSS runtime application server runs commerce data, business rules, permissions and actions. DataInbox controls web agents, chats and messages with partners and customers. Deployment, accounts, maintenance, licensing, access and handover are specified for the project.
Freedom means control over your business configuration, integrations, access, export and handover. Cloudflare, the APPSS runtime, DataInbox and your chosen AI and payment providers still have their own costs, conditions and responsibilities. Your business rules stay in the runtime, while provider connections are explicit choices.
That is the design goal for the agreed commerce actions. Each operation needs a defined contract, permissions, validation and any required approval. The examples on this page illustrate that design; they are not live integrations.
Yes: configure the connection between your chosen provider and the APPSS runtime using its supported API and webhooks. The project defines checkout, payment confirmation, refunds and reconciliation around your merchant account. The connection is configured and tested before production use.
Yes. Business behaviour remains adjustable configuration on the existing production runtime. Change pricing, approvals or order flows as your operation changes, then validate the changes before putting them into use. You keep the production foundation instead of starting a new tech stack for every change.
The design keeps your commerce configuration, business rules and actions in the APPSS runtime, outside an individual AI provider. Compatible agents and AI providers connect through agreed interfaces. Define those connections, data access and replacement conditions explicitly so AI remains a choice, while your business configuration stays yours.
Your production runtime. Your configuration. Your freedom.
Start from the existing APPSS production runtime and Cloudflare hosting. Configure your business rules, connect your own payment provider and control agents and conversations through DataInbox. Keep adapting the configuration as your business evolves.
Shape your commerce briefPrepare a project brief for a first conversation. This does not provision a store.