Your front end. Our engine.
Four ways to run commerce on Marzipan, from one script tag to a build of your own. The cart is live in every one of them.
Static pages, live commerce
The usual objection to a static site is that a shop cannot be static. Stock changes, prices change, carts are personal, and none of that survives being cached at the edge.
That is true of the page, and not true of what is on it. Our web components run in the browser and call the API directly, so the cart, the stock count, the price and the checkout are fetched live no matter how the page around them was built or where it is served from.
Which means the choice below is genuinely a choice about how you like to build, rather than a trade-off between a fast site and a working one.
Four ways in
Ordered by how much of the front end we run. The same API sits behind all four, so moving between them later is a change to your site and not to your data.
Components in the site you have
One script tag, then drop in elements for products, cart, checkout and the account area. Style them with your own CSS so they look like your site rather than ours.
Nothing is rebuilt and nothing moves. There is an official WordPress plugin that does the same thing as blocks, widgets or shortcodes.
Best when the site you have is worth keeping.
A static build, hosted by us
Build the site in Astro, or anything that outputs static files, and we deliver it from edge locations worldwide. Point your own domain at it and the certificate is issued and renewed for you.
Fast to serve, cheap to run, and the commerce on it is still live because the components do that work in the browser. See Marzipan Cloud.
Coming with Marzipan Cloud.
Server-rendered, hosted by us
The same arrangement for sites that need to render per request, for personalised landing pages, very large catalogues, or content that has to be right at the moment it is served.
Same domain handling, same certificates, same delivery network.
Following the static tier.
Fully headless, hosted wherever you like
Build against the documented REST API with scoped keys and take products, collections, orders, subscriptions and content straight into your own application, on your own infrastructure.
Use the components where they save you time and ignore them where they do not. Nothing here is all or nothing.
Best when the build is bespoke and you want full control.
What we run, and what stays yours
We run the parts that are tedious and consequential to get wrong: the catalogue, carts, checkout, payments, subscriptions and renewals, customer accounts, orders and the data behind all of it, on EU-based servers.
You keep the part your customers actually look at. No theme to work around, no page builder you did not choose, and no framework decision made on your behalf.
And because the split is a real one, moving your front end later is a job for your developers rather than a migration. The API and web components are the same whichever way in you take.
Frequently asked questions
Don't just take our word for it
“We made the switch from WooCommerce to a custom solution powered by Marzipan. Managing our orders is a breeze and the flexibility of the subscriptions API has allowed us to enhance our old vine adoptions offering.”
“Marzipan is incredibly easy to use, and extremely flexible and configurable. It makes recurring subscription wine clubs much easier than any other system I have used, and copes with pretty much everything we have thrown at it.”
