Introduction

What is ShipAny vinext

ShipAny vinext is the Cloudflare-native edition of ShipAny Next — the same agent-native headless SaaS engine (payments, credits, subscriptions, auth, RBAC, i18n, CMS), running Next.js 15 on Vite via vinext + @cloudflare/vite-plugin, and deploying to Cloudflare Workers with one command:

/deploy-cloudflare

If you deploy to Node/Docker/Vercel instead, use upstream ShipAny Next.

Why vinext

• Next.js, Workers-native — keep the Next.js 15 App Router programming model (React 19, RSC-style routing) while the app builds with Vite and runs natively on the Cloudflare Workers runtime
• Vite developer experience — instant dev server and HMR via @cloudflare/vite-plugin, dev parity with the actual Workers runtime
• Zero-infra database — D1 by default (no external services to provision), or Postgres via Hyperdrive when you bring your own database
• One-command production — /deploy-cloudflare handles wrangler login, D1/Hyperdrive setup, schema migrations, RBAC seed, secrets upload, deploy, URL fixup, and admin account — idempotent, re-run any time

Agent-Native by Design

Like the rest of the ShipAny family, vinext is built to be driven by Claude Code — built-in skills (/quick-start, /clone-website, /new-page, /new-module, /deploy-cloudflare …) encode the project's conventions, and AGENTS.md / CLAUDE.md teach any coding agent the architecture. See Agent Skills.

Relationship to ShipAny Next (upstream)

New features are developed in shipany-next and pulled into this repo with the /sync-upstream skill. This repo owns the Vite/Cloudflare layer (vite.config.ts, wrangler*, Workers DB wiring, deploy skill) — on sync conflicts in those paths, this repo's version wins.

The engine internals (auth, payment, credits, RBAC, CMS …) are identical to upstream — see the ShipAny Next docs for module reference.

Next Steps

• Quick Start — agent-driven or manual setup
• Agent Skills — the built-in skill catalog
• Deploy — one-command Cloudflare Workers deploy