Plans

Reference.

MaShop has three plans: Free at $0/month, Pro at $20/month, and Max at $100/month. This page lists the exact monthly price, the included monthly credit allowance, and the deploy limit for each, straight from the code that bills you. For how credits are spent see Credits; to add credits without changing plan see Top-ups; to change or cancel a plan see Manage billing.

Comparison

Plan	Monthly price	Included credits / month	Deploys	Publish (go live)
Free	$0	0	3 per day	Blocked (paid plan required)
Pro	$20	2 000	Unlimited	Allowed
Max	$100	12 000	Unlimited	Allowed

One credit equals $0.01 of value. The included credits reset at the start of each billing cycle for Pro and Max. Free has no monthly credit allowance.

Free

Free costs $0/month and includes 0 monthly credits. The plan is pay-as-you-go: you add credits through a top-up when you need them, and a one-time micro-trial covers a small first run so you can try a generation before paying. There is no recurring credit grant and no weekly refill.

You can build and iterate in the workspace on Free. The two limits that matter:

• Deploys: 3 per day. The fourth deploy in a 24-hour window is refused.
• Publishing is blocked. The first go-live (provisioning your own Supabase project and GitHub repo, then the first Netlify build) requires a paid plan.

Pro

Pro costs $20/month and includes 2 000 credits per month. Deploys are unlimited. Publishing is allowed, so a Pro account can take a project from generation to a live Netlify site.

The 2 000 credits refill at each billing cycle. If you exhaust them before the cycle ends, you keep working by adding a top-up; top-up credits do not expire with the cycle. Pro was 4 000 credits before the Pricing v4 change; it is 2 000 now.

Max

Max costs $100/month and includes 12 000 credits per month, six times the Pro allowance. Deploys are unlimited and publishing is allowed, same as Pro. Max suits heavy or parallel building where 2 000 credits a month runs out too fast. Max was 24 000 credits before Pricing v4; it is 12 000 now.

Where these numbers live

Plan rows are read from the subscription_plans table at runtime. The workspace fetches active plans ordered by sort_order; if that read returns nothing, it falls back to a static PLANS constant with the same values. The fields are:

• price_monthly in whole US dollars: 0 (Free), 20 (Pro), 100 (Max).
• credits_per_month: 0 (Free), 2000 (Pro), 12000 (Max).

In the static fallback, the price is stored in cents, so Pro reads price: 2000 and Max reads price: 10000; both resolve to the $20 and $100 above.

Deploy limits in detail

Every deploy reserves a slot against your plan before it runs. The rule is fixed in code:

• Free: 3 deploys per rolling 24-hour window. The limit is a constant of 3 over an interval of one day.
• Pro and Max: unlimited. The check returns allowed = true with remaining = null and never touches the counter.

When a Free account is over the limit, the deploy endpoint returns HTTP 402 with the message:

Limite de 3 déploiements par jour atteinte. Réessaie dans 24h ou passe à un plan supérieur.

The reset timestamp is the moment the window opened plus 24 hours. Deploying itself costs no credits on any plan, because the build ships to your own Netlify and your own Supabase using your OAuth tokens. The deploy quota is the only gate. See Deploy overview and Deploy to Netlify.

Project count

No per-plan project limit is enforced when you create a project. The normal create path checks that GitHub and Supabase are connected, but it does not count your existing projects or cap them by plan, so the "1 project" and "unlimited projects" labels on the plan cards are descriptive, not enforced. The one cap that exists in code is account-wide, not plan-based: duplicating or remixing a project is refused once you hold 50 non-deleted projects (configurable via the MAX_STORES_PER_USER environment variable), returning HTTP 402 with Quota atteint (50 projets max).

Privacy

Across every plan, your prompts and generated code are not sent to OpenAI or Anthropic.