BetaMaShop is in public beta. We improve it continuously, and your feedback shapes what comes next.
Bolt docs, 28 July 2026
A Bolt.new alternative for the part that takes orders
Bolt is fast at turning a chat into an app you can click. Selling is a different job. MaShop generates the catalog, the checkout, the order list and the admin your team works in, then commits the lot to a repository you connect.
Describe your shop. Watch it build.
Where the gap starts
Bolt hands you the parts. The shop is still yours to assemble.
Nothing on this page says Bolt cannot build a shop. It can. Bolt ships a database and a documented payments integration, and a developer who knows what they are doing will get there.
The question is how much of the shop arrives already generated. Take the payments integration. Bolt's own documentation says it creates checkout sessions, syncs products from your payment dashboard, handles the webhooks and manages the subscription lifecycle. Real work, done for you. It is also only the money moving.
No order list. No stock that comes down when someone buys. Nothing that tells whoever is doing the packing which parcels leave today. You prompt for those one at a time, and then you prompt again when a refund has to put the stock back.
MaShop generates the second half too, because shops are the only thing it builds.
Bolt's payments integrationtheir docs, 28 July 2026
Checkout sessionscreated server sideGenerated
Product syncfrom your payment dashboardGenerated
Webhooks and subscriptionslifecycle handledGenerated
Order listwho bought what, and whenNot documented
Stock levelswhat is left after a saleNot documented
Admin back officefor whoever handles the refundsNot documented
Left to youthe second half
Side by side
MaShop and Bolt, on the things a shop needs
Criterion
WithMaShop
WithBolt
What lands first
MaShopA shop, with catalog, checkout, orders and an admin
BoltAn app you can chat into shape, quickly
Commerce model
MaShopVariants, stock, coupons, delivery zones and order states, generated
BoltGeneral purpose. You describe the commerce model prompt by prompt
Payments
MaShopYour own checkout, wired to the provider you pick
BoltA documented integration for checkout sessions and webhooks
Back office
MaShopAn admin generated alongside the shop
BoltNot in the documentation. You build it
Where it goes live
MaShopYour own hosting account, from the first build
Bolt"All new projects created in Bolt are published using Bolt hosting by default." Netlify instead, if you have not published yet
Code in Git
MaShopCommitted to the repository you connect
Bolt"Bolt creates a commit for you." The repo starts private, on main
Published plans
MaShopFree, Pro and Max. The live figures are further down this page
BoltFree, Pro at $25 a month, Teams at $30 per member a month
Bolt figures and quotations were read on bolt.new/pricing and support.bolt.new on 28 July 2026. Capabilities move. Check bolt.new for what is true today. Bolt and bolt.new are trademarks of their owners.
Not for everyone
When Bolt is the better answer
Building something that is not a shop? Stay where you are. A dashboard, an internal tool, a landing page, a weekend prototype that will never take a payment: Bolt is quicker at every one of those, and the commerce model MaShop insists on would be weight you never pick up.
Same if what you want is the loop itself. Bolt's own pitch is that it does the heavy lifting, testing and refactoring as it goes so that you are not fighting errors, and on a general app that loop is hard to beat. MaShop is narrower than that. It is slower to a first screen and much further along by the time there is an order to fulfill.
And if you have already published to Bolt hosting and the thing works, there is no prize for moving.
Yes, up to a point. Bolt documents a payments integration and a database, so the money can move and the data has somewhere to live. The order list and the back office are not in that documentation, so those land on you. MaShop generates them with the shop.
Do I still get the code, the way I do with Bolt?
Yes. MaShop commits the application to a GitHub repository you connect. Bolt does the same automatically, on every change that does not break the project. This one is a tie.
Where does a MaShop shop actually run?
On your own hosting account and your own database, from the first build. Bolt publishes new projects to Bolt hosting by default and can point at Netlify instead, as long as the project has not been published yet.
Is a MaShop shop ready to take real orders?
It is a real application you deploy and run like any other site, rather than a preview sitting on our infrastructure. You connect your own payment provider and the orders arrive in your own database.
What are you selling?
Describe it once. MaShop builds the shop around it.