What MaShop is

Get started

MaShop is an AI you put to work. You describe an outcome in plain words, and it does the job.

It does two kinds of job, and they carry equal weight. It writes and ships software: the code, the accounts that code runs on, the site online. And it takes on work that comes back — you brief an agent once, and it runs on its own from then on, waiting for your signature wherever that matters.

A switch above the message box carries the two: Code and Automations. Code builds and edits what you are making. Automations holds the agents. Neither is the main one. They share the project and the credit balance, and each keeps its own conversation — neither thread ever reads the other one's messages.

What MaShop creates on your accounts

Publishing a project creates three things, on your own accounts, with your own tokens.

• A private GitHub repository named mashop-<slug>. The first commit carries 712 files.
• A Supabase project in eu central 1, with 30 migrations applied. That schema creates 53 tables, row level security on every one of them, and 117 access rules.
• Two Netlify sites: your public site and its back office. Both build from the same repository.

The repository is a workspace of its own. apps/storefront holds the public site: home, product page, cart, checkout success, order page. apps/admin holds the back office: 43 pages across 15 sections, from orders and customers to blog, SEO and analytics. Money is stored in whole cents, never in decimals.

What the default scaffold gives you

The creation window suggests eight starting points, and one of them is simply other. They pick a scaffold, not a limit: whatever you choose, the assistant then writes against what you asked for. The examples that scroll in the empty message box come from the product itself. Booking site for my restaurant. Ticketing for my upcoming event. Booking page for my hair salon.

Every one of them receives the same schema, and that schema is built around a catalogue and orders. Products and variants, stock across locations, orders, customers, coupons, shipping zones, payments, blog, SEO, analytics, staff roles. There is no reservation table, no calendar of slots and no ticket. A product of type service carries a duration, a location and a buffer, and that is the whole of it.

So a restaurant gets a working ordering site on the first day. A salon or an event organiser gets a catalogue that sells a slot or a seat as a product, with no diary behind it. The assistant can run a migration and add the tables your trade needs, if you ask for them in the chat. The 43 back office pages are written for the schema above, so a new table needs its screens asked for too.

E-commerce, restaurant, booking, subscription and ticketing projects ship with the back office. Services, digital and other start without one, and the assistant adds it later if you ask.

Four kinds of activity are refused outright: pornographic content, illegal drugs, firearms, and dark web goods. The refusal happens before any model call and before any credit is reserved, so it costs nothing.

Work that comes back

In Automations you write agents. An agent is a role: a title, a trigger, a job description, a set of tools, a level of autonomy, a cadence. An automation is a recurring instruction handed to one agent. It becomes active the moment you create it.

What an agent prepares can wait for your signature. The Approvals screen shows one card per pending action and says what your signature triggers. Memory holds the rules every agent re reads before working: your tone, a constraint, a name that matters.

Two limits are worth knowing before you invest an evening here. MaShop runs two tools of its own: one reads your Supabase data, one saves an email draft. Tools coming from a server you branched over MCP also run, relayed to that server under the same permission gate. Everything else in the catalogue is a name, not a capability. The 118 tool names on screen describe intent, and an agent that needs one of them is suspended as needing a look, without trying and without charge. MaShop also ships no ready made agents and no ready made skills, so the catalogue is empty out of the box.

What MaShop never sees

Your deployed site and its back office talk straight to your Supabase project, using keys injected on your Netlify sites. No MaShop route reads your customers, your orders or your products.

MaShop keeps its own copy of what it needs to build: your Supabase URL and project reference, your public key in clear, your service key encrypted with AES 256 GCM, the workspace files, and a snapshot of the file tree produced by each generation.

What starting costs

Sending a message in the chat costs credits. One credit is one cent. Creating a project, connecting your services, deploying, restoring a version and inviting someone cost nothing.

Publishing for the first time requires a paid plan: Pro at 20 dollars a month, or Max at 100 dollars a month. A new account receives no welcome credits. An account with no credits gets a trial capped at 25 cents of real provider cost. The whole remaining budget is locked while one trial message runs, then reconciled down to what that message really cost. One demanding message can therefore use the 25 cents on its own.

Read next

• The words of the product defines project, mode, agent, automation, memory, connector and credit. Read it before the rest.
• Your first project walks from an empty account to a site online, with the cost of each action stated first.
• Your first automation does the same for the agents.
• How MaShop works explains what the model reads, what it never sees, and where a run stops.