According to Matt Miller's guide published on Unilog's blog, every B2B company evaluating a commerce platform eventually faces the same decision: build on open-source software it controls completely, or run on a SaaS platform someone else maintains. Both models can support a serious online business, but they ask very different things of the team behind it. Miller argues that the decision is usually framed as a cost question first — open source is 'free,' SaaS has a subscription fee — but that framing misses most of what determines whether a platform helps a business grow or quietly becomes a drag on it.
What SaaS eCommerce Delivers
According to Miller, SaaS eCommerce means the software, hosting, security, and infrastructure are all provided and managed by the platform vendor. The merchant logs in, configures the store, and runs the business, while the vendor handles servers, uptime, security patches, and version upgrades. Platforms like Shopify and BigCommerce popularized this model for B2C; in B2B, it now extends to complex catalogs, contract pricing, and ERP-connected order workflows. The merchant does not own the underlying code and generally cannot rebuild the platform from the ground up. In exchange, the merchant gets a working commerce operation from day one, ongoing improvements without a development project, and a vendor whose job is keeping the platform secure and running.
What Open-Source eCommerce Requires
Open-source eCommerce means the platform's source code is freely available, and the merchant or a development partner installs it, hosts it, and customizes it, according to Miller. Magento (now Adobe Commerce) and WooCommerce are the most recognized names in this category. There is no license fee for the core software, and in principle anything can be modified. In practice, 'free' software still requires hosting, a development team or agency, security monitoring, and someone accountable for keeping it patched and running. As Miller wrote:
The code is yours to shape into anything you want. Whether you have the time, budget, and technical depth to do that well is the real question.
Total Cost of Ownership
Open-source software has no license fee, but that is rarely where the money goes, Miller reported. Hosting, security monitoring, a development team for customization and maintenance, plugin and extension licenses, and emergency fixes that come with running your own infrastructure all add up. Many businesses that choose open source to save money end up spending more once development and hosting costs are counted honestly. SaaS eCommerce bundles hosting, security, and platform maintenance into a predictable subscription. You know your platform cost going into the year. That predictability matters as much as the raw number, especially for a mid-market business trying to plan a marketing or growth budget without an open-ended technology line item.
Security and Compliance
With open-source eCommerce, your business is responsible for every security patch, every plugin vulnerability, and every compliance requirement, including PCI compliance for payment data, according to Miller. That is a real, ongoing job, not a one-time setup task, and it requires people who are watching for it. SaaS vendors build security and compliance into the platform because it protects every customer running on it, not just yours. Patches roll out automatically. Compliance requirements are handled at the platform level. For a business without a dedicated security team, that shift in responsibility is one of the most concrete advantages SaaS offers.
Maintenance and Updates
The guide's third key difference is maintenance and updates, with the heading 'Automatic vs. Manual.' The source frames the comparison as automatic updates from SaaS vendors versus manual update processes for open-source platforms.
Comparative Snapshot
| Factor | SaaS eCommerce | Open-Source eCommerce |
|---|---|---|
| Core software license | Subscription fee | No license fee |
| Hosting & infrastructure | Included, vendor-managed | Merchant or partner must arrange |
| Security patching | Automatic, handled by vendor | Merchant responsible for every patch |
| PCI compliance | Handled at platform level | Merchant responsibility |
| Customization | Cannot rebuild from ground up | Source code freely modifiable |
| Representative platforms | Shopify, BigCommerce | Magento/Adobe Commerce, WooCommerce |
Miller's guide ultimately argues that the two models trade off in these areas in ways that matter more than which is technically 'better.' The right choice depends on a team's ability to absorb the time, risk, and control each model demands.
Sources:
