CoreMVP, Now With TanStack Start

You can now build on CoreMVP with TanStack Start. CoreMVP for TanStack Start brings our connected application to a second framework: accounts, Organizations, Projects, private file uploads, and lifetime or subscription billing with Stripe or Polar.

Choose the framework you want to build with. You should not have to reconnect authentication, payments and customer access before working on your product.

CoreMVP for TanStack Start is sold on its own for $99, or with the Next.js template in the CoreMVP Bundle for $149; see pricing. The Quickstart starts from repository access and takes you to a running local app and your first saved Project. Next.js remains available; this release adds a choice underneath the same goal: a foundation for building a product and monetizing it.

Start with a working product

Your first useful check is deliberately small: create an account, open the dashboard, create a Project, and refresh. Your Project should still be there in your Personal Organization.

From that starting point, you can build your product around the included Organization permissions, Projects, and private Storage. When you are ready to charge, choose Stripe or Polar and configure your offers.

Both payment providers connect checkout to verified payment handling and customer access. Lifetime billing supports a guest purchase path; subscriptions connect recurring payments and customer billing management. You still choose your prices and configure your own provider accounts. You do not need to design a separate payment-to-access system for each product you build.

Try these flows in test mode or sandbox before accepting live payments. The billing guides show the required setup and checks for your selected provider and model.

TanStack routes, one application

The template uses TanStack Start for routing, rendering and server functions. The application API stays in the same deployment.

For example, the native /api/* route passes the request to the included Hono app:

const handle = async ({ request }: { request: Request }) => {
  const { apiApp } = await import('@/api/app');
  return apiApp.fetch(request);
};

That small adapter preserves the existing application boundaries. Browser hooks call same-origin routes. Hono validates HTTP input, services enforce the user's permissions, and repositories access PostgreSQL. Supabase provides Auth and private Storage. Database and provider secrets stay server-side.

This gives you familiar edit points when extending the app. Add your product behavior to its service and route; you do not need another backend deployment to expose it. The application architecture guide explains the shared structure, and the Projects guide follows one concrete change through the native app.

Deploy on Cloudflare

The TanStack version includes a Cloudflare Workers deployment path. Nitro packages the pages, server functions and API as one Worker, alongside its static assets. Supabase remains the database, Auth and Storage provider; choosing Workers does not require moving your data to D1 or your files to R2.

Public settings, including your app's origin, are fixed into the browser bundle at build time. Private database, payment and email settings are configured for the Worker runtime. The guide keeps those two steps explicit and finishes with checks against your actual deployed app.

A reachable homepage is only the first check. Sign in and reload, save a Project, verify your selected test checkout, and check the resulting access. Those are the behaviors your customers depend on.

Get started and get help

The Cloudflare guide covers the TanStack Worker path. The existing Next.js template retains its Vercel guide; do not treat that procedure as verification of a TanStack Vercel deployment. We also do not promise that an application you customize is ready for live payments simply because it builds. Configure your own providers and run the checks for the behavior you intend to ship.

Start with Quickstart, then follow Deploy to Cloudflare. If setup is unclear or a documented flow fails, email [email protected] with the failing step and the expected result. Keep credentials and customer data out of the report.