Source: https://mayphus.org/mayphus-store/
Title: Mayphus Store
Metadata: {"category":"artifact","id":"mayphus-store","kind":"artifact","language":"en","route":"/mayphus-store/","tags":["cloudflare","commerce","software"],"type":"project"}

Mayphus Store explores running a small shop on Cloudflare, with the owner administering it through ChatGPT or Codex. The products to sell are still undecided. This is a separate project from the archived [Shop Prototype](/shop/).

## Architecture

A Cloudflare Worker serves the storefront and API. D1 holds the catalog, inventory and orders. Private R2 storage holds digital files. KV and Durable Objects support the owner-authenticated administration interface used through ChatGPT and Codex.

The implementation includes product browsing, a cart, orders combining physical and digital items, inventory reservations, signed payment webhooks, expiring download links, manual fulfillment and recovery paths.

## Current status

As of 8 October 2026, payment integration uses **Stripe test mode**. Physical shipping is limited to the United States, with one currency per deployment.

The latest development audit passed TypeScript checks, 31 unit and integration tests, local D1 transaction checks, 10 migrations and a deployment dry run. Two Chromium scenarios exercised storefront, cart, stock errors, repeated checkout, payment confirmation and download validation with a mocked payment provider. Local administration checks rejected missing and forged credentials. The active project dependency audit, including development tools, reported no known vulnerabilities; the legacy archive was outside that audit.

These are development checks. Real-provider payments, authenticated OAuth administration and an R2 backup rehearsal remain unverified, as do hosted CI and deployment of this draft. A passing test preview is not proof of a successful purchase.

The code remains private. A source release is planned; this is not yet a public open-source release. The existing MIT license is unchanged.

## Before opening the shop

Choose the first products, payment provider, merchant policies and deployment budget, then rehearse payment, inventory, delivery and recovery together. Verify owner administration and private downloads in the deployed environment before treating the shop as ready for customers.

Cloudflare's free allowances have separate request, compute, database, storage and operation limits. They are a starting budget, not a zero-cost guarantee; suitability depends on actual usage and service configuration. Check the current [Workers](https://developers.cloudflare.com/workers/platform/pricing/), [D1](https://developers.cloudflare.com/d1/platform/pricing/), [R2](https://developers.cloudflare.com/r2/pricing/) and [Durable Objects](https://developers.cloudflare.com/durable-objects/platform/pricing/) pricing before deployment.