--- title: 'Roadmap' description: 'Honest near-term plans, what is exploring vs committed, and what cartwright will not do.' canonical: 'https://cartwright.app/docs/roadmap' --- # Roadmap (/docs/roadmap) The [changelog](/changelog) shows the current engine release and the full shipped history — it reads the version from the engine, so it cannot go stale the way a number typed here would. The roadmap below is intentionally short and forward-looking. Items are marked `[committed]`, `[exploring]`, or `[planned]` so readers can tell production-ready from "we are not even sure we want this." ## Shipping now [#shipping-now] A sample of what's already shipped and live in production — the [changelog](/changelog) has the complete list. * **Public MIT engine template** `[shipped]` — [`Teloz1870/cartwright-template`](https://github.com/Teloz1870/cartwright-template) is the source downloaded by the CLI. Tagged releases are the stable channel; public branches are visible for review and testing. * **`create-cartwright` on npm** `[shipped]` — `npx create-cartwright@latest` scaffolds `light`, `full`, and database-free `site` profiles. The CLI installs dependencies and prepares the selected profile rather than leaving a half-configured starter. * **AI discovery and commerce surfaces** `[shipped]` — MCP, structured data, `llms.txt`, agent rules and scoped API tooling live in the engine. Exact surfaces depend on the selected profile and enabled feature flags. * **[`/integrations`](/integrations) top-nav page** — 15 core integrations, plus the 10 planned Plus-tier MCP integrations, with real brand logos and category eyebrows. * **[`/onboarding`](/onboarding) Plus-tier preview** — type a URL, watch the five-agent migration demo, join the waitlist. * **[`/pricing`](/pricing) with four tiers** — Self-hosted $0, Plus $49/mo, Cloud $199/mo, Enterprise. Resend-backed waitlist for Plus and Cloud. * **A2A Headless Merchant foundation** — three new endpoints (`/api/agent-card`, `/api/negotiate`, `/api/escrow/verify`), Anchor-Resume negotiation engine, Guardian middleware, P2K scanner. See [changelog v3.1.0](/changelog). * **[`/docs/in-the-box`](/docs/in-the-box)** — developer-tone integration walkthrough sitting next to the marketing-tone `/integrations`. ## Current adoption work [#current-adoption-work] * **More industry templates** `[committed]` — at minimum `eyewear` and one home-goods category beyond `generic`. * **`demo.cartwright.app` live** `[shipped; continuously upgraded]` — the Northbound coffee shop is the public engine demo. Engine upgrades must preserve its coffee identity and storefront design. * **Auto-rendered `/changelog`** `[in progress]` — the homepage `SoftwareApplication` version and the `/changelog` "current engine release" line now read the engine version straight from `CHANGELOG.md` at build/ISR time (`lib/engine.ts`), so the version never goes stale. Full per-entry auto-render from `CHANGELOG.md` is the remaining step. * **Onboarding polish** `[in progress]` — clean scaffold output, profile-accurate docs, actionable GitHub issue routes, and reproducible smoke tests for every profile. * **Video walkthrough** `[exploring]` — 5-minute screencast from `npx create-cartwright` to first sale; timing depends on bandwidth. ## Next [#next] * **Shopify migration** `[self-hosted on-ramp shipped in v0.10.0; full agentic flow planned for Plus]` — the **Hoptify** "import from Shopify" onboarding shipped in v0.10.0 (`--profile full` — the module is pruned from the default profile): with a Firecrawl key and an AI key it lifts your palette (design-import) and brings products across from the product URLs you list, fail-soft to a demo otherwise. The full five-step agentic migration (customers, deploy) is planned for Plus and still in development; interactive preview at [/onboarding](/onboarding). * **API auto-reference** `[planned]` — generate the `/docs/api/mcp-tools` page from `lib/tools/registry.ts` at build time instead of hand-maintaining it. The current page will drift; this fixes it. * **`cartwright upgrade` tooling** `[planned, Plus]` — automated fork upgrades. Today upgrades are manual: the `.cartwright/release.json` marker + changelog security advisories tell you what to pull, but nothing auto-updates your fork (see the engine's [versioning policy](https://github.com/Teloz1870/cartwright-template/blob/main/docs/versioning-policy.md)). * **Algolia search** `[planned, Plus]` — planned Plus-tier MCP integration. Instant product search wired to the storefront and agent-callable for typed queries. Orama-based search stays for self-hosted forks under \~1000 products. * **Plus-tier MCP integrations** `[planned, Plus]` — ten brand integrations planned for Plus: Klaviyo (email marketing), Mailchimp (email marketing), QuickBooks (accounting), Notion (knowledge), Airtable (operations), HubSpot (CRM), Slack (notifications), Zapier (meta-connector), ShipStation (fulfillment), Algolia (search). All tool-callable from the storefront AI and admin. See [/integrations#plus](/integrations#plus) for per-brand pitches. * **Multi-tenant docs** `[exploring]` — fork-specific docs hosted on subpaths or via the CLI. Mostly a "would be nice" — unclear if there is real demand. ## Maybe later [#maybe-later] * **Headless CMS adapter** `[exploring]` — Sanity / Contentful / Storyblok for the admin Sider CRUD. Likely a separate package, not core cartwright. * **B2B / wholesale module** `[exploring]` — tiered pricing, NET-30 invoicing, bulk-order workflows. Big surface, only worth building if a paying user funds it. * **EDI** `[exploring]` — only relevant for shops integrating with traditional retail. Unlikely unless a specific fork pulls. ## What cartwright will not do [#what-cartwright-will-not-do] These are explicit non-goals. Listing them here so contributors do not propose them and operators do not expect them. * **The template stays MIT, forever.** Everything that lands in `Teloz1870/cartwright-app` is MIT, and so is the public template repo, [`Teloz1870/cartwright-template`](https://github.com/Teloz1870/cartwright-template). The free, self-hosted path is permanent — you can always run cartwright without paying Teloz a cent. Optional paid tiers (Plus, Cloud, Enterprise) layer hosted services, support, and — as they ship — premium integrations on top; they never gate the core template. * **No per-order pricing.** Every transaction on a cartwright fork is yours. There are no affiliate-style hooks, revenue-share kickbacks, or volume reporting back to Teloz — even on paid tiers. * **No closed-source feature gating of the template.** Paid tiers add hosted services and add-on integrations. They do not paywall features inside the template itself. There will not be a "Pro" branch of cartwright with paywalled core features. * **No mandatory telemetry.** Cartwright forks do not phone home. The MCP introspection surface exists for *external* AI agents to discover *your* tool surface, not for cartwright to discover your traffic. Paid tiers add opt-in analytics for your own shop, not for us. ## How to influence this [#how-to-influence-this] * For engine and scaffold requests, [open an issue on `cartwright-template`](https://github.com/Teloz1870/cartwright-template/issues). * For docs and CLI requests, [open an issue on `cartwright-app`](https://github.com/Teloz1870/cartwright-app/issues). * Ship it yourself in a fork and document the integration; recipes get pulled upstream when they generalise.