The real choice is who operates the platform. With SaaS ecommerce, a vendor hosts the software, applies platform updates and sells you access. With self-hosted ecommerce, you install the software on infrastructure you control and take responsibility for keeping it running.
Both models can sell products. They differ in who is on call, how customisation works, what happens when you want to leave, and where the costs sit. The right answer depends more on your team than on a feature checklist.
Editorial note: ShopKeeprr is our product, so we have a commercial interest in this subject. Competitor facts are taken from public documentation and linked where practical. Pricing and plan details can change; check the provider before you buy.
The definitions, without the marketing
SaaS means software as a service: the vendor operates the application and you pay a subscription. Shopify is a well-known example. You get an account, a hosted storefront and a platform-managed checkout. You configure within the product’s boundaries.
Self-hosted means you install the application on a server you control. ShopKeeprr, WooCommerce, Bagisto and Magento Open Source are self-hosted. You choose the host, manage the runtime and database, apply updates and keep backups. Some hosts offer managed hosting for a self-hosted application, which is a useful middle path: you still own the installation, but a provider handles more of the server work.
Open source is a licensing question, not an operating model. A self-hosted product can be proprietary; a SaaS product can be built on open-source code. Do not use the terms interchangeably.
The comparison that actually matters
| Question | SaaS | Self-hosted |
|---|---|---|
| Who hosts the platform? | The vendor | You or your managed host |
| Who applies platform updates? | The vendor | You, usually through the application updater |
| Who patches the server, PHP and database? | The vendor within its platform scope | You or your host |
| Who handles backups? | Platform tools plus your export discipline | You; test restores, not just backups |
| Upfront cost | Low; subscription starts quickly | Hosting, setup and possibly development |
| Ongoing cost | Predictable platform subscription plus apps and payment fees | Hosting, payment fees, extensions and maintenance labour |
| Customisation | Within the vendor’s extension and theme boundaries | Code and database access, subject to the license |
| Scaling | Platform handles capacity within plan limits | You size the server, cache, database and queue |
| Support | Vendor support and partner ecosystem | Documentation, community, host or paid help |
| Exit | Export tools and APIs; vendor-controlled account | Your database and code; you own the migration work |
The cost model, not the sticker price
A SaaS subscription looks simple because it bundles hosting, updates and support into one line. That convenience has a price, but it also removes work you would otherwise pay for in time or contractors. A self-hosted license can be free while the surrounding operation is not.
Build a three-year total cost model:
- SaaS: subscription × months, app subscriptions, theme purchases, payment processing, chargebacks, migration and staff time.
- Self-hosted: hosting, domain, TLS, payment processing, paid extensions, development, backups, monitoring, security work, upgrade labour and downtime risk.
Put a realistic hourly value on your time. If you would need to hire a developer for two days a month, that belongs in the comparison. If you already have the skills and infrastructure, self-hosting is much more attractive.
If the store lost checkout access for four hours, who would fix it? If the answer is “the vendor’s support team”, SaaS is aligned with your operating capacity. If the answer is “nobody”, self-hosting is not ready for launch.
Control, customisation and lock-in
Self-hosting gives you direct access to the application and database. You can add workflows, integrate internal systems, customise the checkout or change the data model, subject to the license and your ability to maintain those changes. That is valuable when your business logic is genuinely different.
SaaS gives you configuration and extensions inside a product boundary. That boundary is often a feature: upgrades are less likely to break your custom code, and the vendor handles the platform. The cost is that you may wait for a feature, pay for an app, or work around a limitation.
Lock-in is not binary. Ask how you export products, customers, orders and content; whether the export includes the fields you need; who owns payment tokens; and how redirects will work after a move. A self-hosted store can still be hard to migrate if nobody maintains its database.
Maintenance and security responsibilities
With SaaS, the vendor is responsible for the platform, but not for your store’s configuration. You still manage staff accounts, apps, content, discounts, tax settings and customer data. With self-hosting, the platform responsibility moves to you or your host as well.
| Task | SaaS responsibility | Self-hosted responsibility |
|---|---|---|
| Platform release | Vendor | You (application updater or manual) |
| PHP / database / web server | Vendor | You or managed host |
| Operating system patches | Vendor | You or managed host |
| TLS certificate | Vendor | You or host |
| Application backup | Platform tools; export is still your job | You |
| Restore test | Vendor’s platform plus your data checks | You |
| Payment webhooks | Platform integration, configured by you | Your integration and monitoring |
| Access control | Shared: platform controls plus your accounts | Your server and application configuration |
Security is not a product checkbox. In both models you need least-privilege access, strong authentication, monitoring and a response plan. Self-hosting adds patch cadence and server hardening to the list.
Scaling, performance and peak traffic
SaaS platforms are designed to absorb traffic within their plan limits. You may still hit rate limits, bandwidth fees or plan caps, but you are not configuring PHP-FPM workers during a launch. Self-hosted stores give you control over caching, database tuning, queue workers and object storage, and they make you responsible for capacity planning.
If you expect unpredictable viral traffic or a large international audience, a managed platform or a managed host with autoscaling is usually safer than a single VPS. If traffic is predictable and you know how to monitor it, self-hosting can be efficient and cost-effective.
Which model fits which team?
Choose SaaS if…
- You do not want to operate servers or patch software.
- You need support and a predictable platform upgrade path.
- Your differentiation is brand, product and marketing, not custom checkout code.
- You value speed to launch over infrastructure control.
Choose self-hosted if…
- You have PHP/Laravel hosting skills or a trusted managed host.
- You need direct access to data, code or internal integrations.
- You want to avoid a platform subscription and can absorb the maintenance.
- You need a store model the hosted product does not cover well.
There is also a middle path: run self-hosted software on a managed platform. You keep the application and data relationship while outsourcing some server work. Ask exactly what the host patches, backs up and monitors — “managed” is not a standard scope.
Where ShopKeeprr fits
ShopKeeprr is self-hosted software: a complete Laravel application with a storefront, admin, four store models, themes, a builder and signed updates. The core is free to download and run, but it is not open source. Hosting, payment processing and maintenance are yours.
It is a fit for a team that wants the self-hosted model and a complete application, not a framework to assemble. It is not a fit for a team that wants a vendor to operate the store, or one that requires an open-source license. Compare the two models with our ShopKeeprr vs Shopify guide, then decide which responsibilities you actually want.
Frequently asked questions
Is self-hosted ecommerce cheaper than SaaS?
It can be, but not automatically. A free license removes the platform subscription; hosting, payment fees, extensions and maintenance remain. If you need paid help or your time is expensive, SaaS can be cheaper overall. Build a three-year total cost model.
Is Shopify SaaS or self-hosted?
Shopify is SaaS. Shopify hosts the platform, applies platform updates and provides the checkout environment. You configure your store within its product boundaries and pay a subscription plus payment processing and apps.
Is self-hosted ecommerce more secure?
Not inherently. Self-hosting gives you control over hardening and patching, but it also makes those tasks your responsibility. SaaS shifts platform security to the vendor but does not remove your responsibility for accounts, apps, permissions and customer data. Both models need good operational discipline.
Can I move from SaaS to self-hosted later?
Yes, generally through exports and a rebuild. Products, customers and orders can often be migrated; themes, apps, payment tokens and subscriptions need more work. Plan URL redirects, test the checkout and keep the old store live until the new one is stable.
What is managed self-hosting?
It means a hosting provider runs the server layer for a self-hosted application: patching, backups, monitoring or scaling. The scope varies. Ask what is included, what you still own and whether the provider manages application upgrades or only the infrastructure.
Put it to work
Download the free ShopKeeprr core.
Install it on your own server, connect your database and start building. The core is free; hosting, payment processing and optional extensions are separate.