--- title: "E-commerce SaaS: hosted platforms vs open source vs headless" description: "Three ways to run an online store: a hosted SaaS platform, self-hosted open source or headless. What each costs in money and work, with a decision table by store size." canonical: "https://saascron.com/ecommerce-saas/" language: "en-US" author: "Ricardo Machado" author_url: "https://saascron.com/author/ricardo-machado/" published: "2026-10-23T17:00:00-04:00" updated: "2026-10-23T17:00:00-04:00" category: "Business Software" tags: ["Ecommerce", "Business software", "SaaS products", "Headless commerce"] --- # E-commerce SaaS: hosted platforms vs open source vs headless > Three ways to run an online store: a hosted SaaS platform, self-hosted open source or headless. What each costs in money and work, with a decision table by store size. You want to sell online, or your current store has outgrown its setup, and every agency you ask recommends a different platform. You need to know what you are really choosing between and what each choice costs once the work is counted. There are three models: a hosted e-commerce SaaS platform, self-hosted open-source software, or headless commerce, where a separate front end sits on top of a commerce back end. The choice decides who keeps the store running at 2 a.m. on a sale day, and that cost can be larger than the license fee. This guide explains the three models, works through a three-year cost comparison and ends with a decision table by store size. If SaaS is new to you, start with [What is SaaS?](https://saascron.com/what-is-saas/). ## The three models in plain terms Think of it like opening a shop. You can rent a unit in a shopping mall: the mall handles security, cleaning and the electricity, and you follow its rules on signs and opening hours. You can buy a building and run it yourself: no landlord, but the roof is your problem. Or you can rent the mall's stockroom and checkout and build your own storefront next door, designed exactly as you want. - **Hosted e-commerce SaaS** is the mall unit. The vendor runs the software, the servers, security updates and checkout. You pick a theme, add products and pay a monthly fee. Shopify is one example. - **Self-hosted open source** is the building you own. The software is free to download and change, and you or your developer run the hosting, updates and security. WooCommerce describes itself as "the world's top open-source platform", "powered by WordPress", with no "monthly platform fees" ([WooCommerce](https://woocommerce.com/woocommerce/)). Hosting is a separate bill. - **Headless commerce** is the custom storefront. Shopify's developer documentation puts it in one line: "Headless commerce separates your storefront's frontend from its backend" ([Shopify, headless](https://shopify.dev/docs/storefronts/headless)). The back end still handles products, cart and checkout; your developers build everything the customer sees. ## How each model works in practice **Hosted SaaS.** You pay a subscription, usually in tiers, and buy extra functions as apps from the vendor's marketplace. Payment processing is charged per transaction. The vendor ships new features to every store at once. You cannot change the core code, so anything the platform and its apps do not support is hard to add. That marketplace model is what makes a product a platform, as [What is a SaaS platform?](https://saascron.com/saas-platform/) explains. **Self-hosted open source.** The license costs nothing, but nothing else is free. You choose a host, install the software, add extensions, apply security updates and fix what breaks. You can change anything, because you hold the code. The real cost is developer time, every month, for as long as the store runs. **Headless.** The commerce engine can be a SaaS back end or an open-source one. On Shopify, the Storefront API "serves products, collections, search, and the cart, and hands customers off to checkout". Hydrogen is "Shopify's headless toolkit" and Oxygen is "Shopify's hosting for Hydrogen storefronts". Shopify's own page states that a headless storefront "costs more to build and run than a theme". You get full control of speed and design, and a front end that needs a development team. ## Worked example: three years of running costs Platform prices change often and differ by region, so this example uses labeled assumptions, not any vendor's price list. Replace each line with the quotes you receive. **Example:** a labeled hypothetical. A store with about 2,000 products and steady sales compares three years of costs. Payment processing is left out, because it applies to all three models at similar rates. Developer time is priced at $75 an hour. | Cost line (assumed) | Hosted SaaS | Self-hosted open source | Headless | |---|---|---|---| | Platform or license fee | $100 a month | $0 | $100 a month (SaaS back end) | | Hosting | included | $80 a month | $50 a month | | Apps or extensions | $150 a month | $100 a month | $150 a month | | Developer upkeep | none | 8 hours x $75 = $600 a month | 20 hours x $75 = $1,500 a month | | Monthly running cost | $250 | $780 | $1,800 | | Three years of running | $250 x 36 = $9,000 | $780 x 36 = $28,080 | $1,800 x 36 = $64,800 | | One-time build (assumed) | $3,000 | $8,000 | $40,000 | | Three-year total | $12,000 | $36,080 | $104,800 | Read the developer row first. The license fee is the smallest line in the self-hosted column, and labor is 77% of its running cost ($600 / $780). In the headless column, labor is 83% ($1,500 / $1,800). The hosted platform looks expensive only if you compare license fees and ignore people. The comparison turns when the store needs something the hosted platform cannot do. If a custom checkout step or a product configurator would add sales worth more than the extra cost, the open or headless model pays for itself. Put that number on paper too, before you switch. ## Decision table by store size The table is a starting point, built from the trade-offs above. Your catalog, your team and your sales plan decide the final answer. | Store stage | Usually fits | Why | Watch for | |---|---|---|---| | First store, one or two people | Hosted SaaS | No servers, no developer, fast launch | App fees that add up month by month | | Growing store, small team, standard needs | Hosted SaaS on a higher tier | Same platform, more staff accounts and reports | Features you cannot add without code | | Unusual products or processes, a developer on hand | Self-hosted open source | Full control of the code and the data | Security updates and downtime are yours | | Large brand, in-house developers, design and speed matter | Headless | Custom front end, any framework | Two systems to run and a team to keep | Moving between rows is possible but slow. A store migration touches products, customers, order history, URLs and search rankings. Choose the row you expect to be in for the next three years, not the one you are in today. ## Common mistakes 1. **Comparing license fees instead of total cost.** The free license looks cheapest until developer hours are added; in the example, they are 77% of the open-source running cost. Why it happens: the license is the only number on the download page. Instead: price three years, including people, as in the table. 2. **Going headless for speed alone.** A custom front end can be fast, but so can a light theme on a hosted platform. Why it happens: headless is sold on performance. Instead: go headless when you need a design or experience a theme cannot deliver, and have the team to run it. 3. **Installing apps without a budget.** Each app adds a monthly fee and code that runs on your pages. Why it happens: apps fix problems in minutes. Instead: list every app with its monthly cost, and review the list every quarter. 4. **Ignoring the exit.** Product data, customer accounts and order history must move with you if you change platforms. Why it happens: nobody plans a move on day one. Instead: test a full export from the platform before you commit, and keep URL redirects in the migration plan. For how monthly fees, tiers and usage charges are built, see [SaaS pricing models](https://saascron.com/saas-pricing-models/). ## Sources - WooCommerce, [product page](https://woocommerce.com/woocommerce/), checked October 2026. - Shopify, [Headless commerce developer documentation](https://shopify.dev/docs/storefronts/headless), checked October 2026. ## In three sentences You can run an online store on a hosted e-commerce SaaS platform, on self-hosted open-source software or on a headless setup with a custom front end over a commerce back end. In the labeled example, three years cost $12,000 hosted, $36,080 self-hosted and $104,800 headless, and developer time is most of the difference. Start hosted unless you need something the platform cannot do, and price people, apps and the exit before you choose. --- Canonical: