A store per seller, with approval
The seller signs up, goes through your approval and gets a store with a name, logo, description and its own page. Their products appear in the main window and in their store.
What gets built
Four things you could have working this week
Not a feature list. These are the apps people actually describe, and what the platform hands back when they do.
An order split by seller
A cart with items from three stores becomes three orders, one per seller, each with its own status of packed, shipped and delivered.
Commission recorded on every sale
The marketplace's percentage and the seller's net amount are recorded on the order, and the seller sees a statement of what they are owed and what has already been paid out.
Reviews from people who bought
Only buyers review the store and the product, with a rating and comment. The average shows on the store, which is what makes a buyer trust someone they have never met.
Included
The parts nobody wants to build twice
Database, login, payments and publishing are part of the platform, not a list of services you go and wire up afterwards.
A real database, not a form dump
Every screen reads and writes models you can open, query and export. The data is a database of yours from the first minute, not a spreadsheet the app pretends to read.
Login for your own users
Email, magic link and Google sign-in, with roles and per-record ownership enforced by Postgres itself. A badly written screen cannot become a leak, because the database answers empty.
Payments that land in your account
Stripe, Pagar.me and Mercado Pago connect once. Card, Pix, boleto and subscriptions, with the card fields rendered by a hosted vault your app never touches.
Web, installable, and in the stores
One project published three ways: your own domain, an icon on the phone straight from the browser, and a signed binary submitted under your own store account.
Found in search, and by the models
Titles, metadata, sitemap, structured data and social images are generated with the app. Pages get found instead of only being linked.
React code you can take with you
Real React, edited line by line or by clicking the element on screen, exported as a ZIP or pushed to your GitHub. No lock-in you have to negotiate your way out of.
How it works
From a paragraph to a published app
Three steps, and the second one is the one people do not believe until they watch it.
Start here
A prompt you can paste right now
This is a complete first message, not a slogan. Paste it, change the nouns to yours, and you have an app to react to instead of a blank page.
Build a marketplace for handmade products from my region. Three roles: buyer, seller and admin; the seller signs up with store details, ID and payout details, and only starts selling after my approval; each store has a name, logo, description and its own page; the seller adds products with photos, price, stock and category, and sees only their own products, orders and statement; the main window has search and filters by category and by store, and each product has a page built for search engines; the buyer fills a cart with items from several stores and pays once by card, and the purchase splits into one order per seller, each with the statuses paid, packed, shipped and delivered; each order records my twelve percent commission and the seller's net amount; the seller sees the balance owed to them and I record the payouts made; only buyers review the store and the product; and an admin dashboard only I can see, with sellers awaiting approval, sales per store, the month's commission and outstanding payouts.
Ready to start from
Templates in this category
A template is a working app with data already in it. Open one, make it yours, publish it under your own account.
Questions
Frequently asked questions
Describe it. See it running. Publish it to the store.
Free to start, no credit card. You subscribe when you want your own domain without the badge or your app in the stores, and on the Builder plan you take the code with you if you ever want to.