Glossary

Reference: the exact meaning of each MaShop term.

This page defines the words you see in the MaShop workspace, billing screens, and docs. Each entry is one sentence, grounded in how MaShop uses the term. For deeper coverage, follow the linked page.

Core objects

Project

A single site you build in MaShop, holding its own chat history, generated files, and links to your GitHub, Supabase, and Netlify accounts. You create one from the New project modal, which asks for a name, a slug, an optional description, and a default language and currency. See Projects.

Storefront

The public, customer-facing part of the generated site, where visitors browse and buy. MaShop generates it as server-rendered pages so it is indexable by search engines, and only published rows are world-readable. See Your code.

Backoffice

The private admin area MaShop generates alongside the storefront, where you manage products, orders, customers, payments, analytics, and blog content. It ships as a Next.js 15 app you own and can edit or delete like the rest of your code. See Code structure.

Workspace

The three-part studio for a project: the chat on one side, the live preview in the center, and your generated files on the other side. This is where you talk to the AI, review changes, and deploy. See The workspace.

Billing terms

Credit

The unit MaShop bills AI work in, priced at 0.01 USD per credit. Your prompts and generated code are not sent to OpenAI or Anthropic. See Credits.

Top-up

A one-time purchase that adds credits to your balance outside your monthly plan, in a chosen amount between 10 and 1000 USD. Larger amounts earn a bonus percentage on the base credits, stepping up at fixed thresholds. See Top-ups.

Amount (USD)	Bonus on base credits
10 to 49	0%
50 to 99	5%
100 to 249	10%
250 to 499	15%
500 to 999	20%
1000	25%

Trial

A small one-time credit budget MaShop grants a new, unpaid account so you can try generation before you pay; it is a spendable pool that draws down as you build, not a fixed number of runs. Publishing your site requires a paid plan. See Plans.

Shipping your site

Provisioning

The one-time setup that turns a project into real, running infrastructure: MaShop creates a Supabase project named mashop-{slug} on your account, applies the backend migrations, creates a GitHub repository, pushes the code, and triggers the first Netlify build. It runs as a resumable state machine, so a timeout mid-way resumes from the recorded stage instead of starting over. You start it from the Publier action; provisioning requires a paid plan. See Deploy overview.

Deploy and redeploy

Deploying ships your code to your own Netlify account, the only deployment target MaShop supports; Vercel is not a target for the generated site. The first go-live runs through provisioning (the Publier flow); after that, the Déployer button redeploys an already-provisioned project by triggering a new Netlify build from your linked GitHub repo. On the Free plan, deploys are limited to 3 per 30 days (Pro and Max are unlimited). See Deploy to Netlify.

Snapshot and restore

A snapshot is a saved copy of all your project files captured at a meaningful change, listed newest-first in the version timeline with a message, a file count, and a relative time. Restoring one replaces your current files with that snapshot's contents; before it does, MaShop captures a fresh snapshot of the current state (labelled from the target's message) so the state you are leaving is itself recoverable. You trigger it with the Restaurer action on a version row. See Versions.

Integrations

MCP

MCP (Model Context Protocol) lets an external assistant or editor act on your MaShop account through the chat you already use. You connect from an MCP client such as Claude Desktop or Cursor, and you review or revoke authorized clients in Settings under Connected apps. See MCP and API.