What you need
7 projectsCommercial useMaintainedSetupCost
- Commercial use
- Yes
- GPL. The repository license file says GPL version 2 or later, while the plugin readme lists GPLv3. Running your own store adds no obligations. If you distribute a modified version, it must stay under the GPL.
- Maintained
- Active
- Last push on 2026-10-13. The repository is not archived.
- Setup
- Easy
- You need a WordPress site first. In its admin, search for WooCommerce on the plugins page, install and activate it, then follow the setup wizard. The stated requirements are PHP 8.3 or later, MySQL 8.0 or MariaDB 10.6 or later, HTTPS, and a WordPress memory limit of 256 MB or more. The requirements page says WordPress 6.9 or later while the plugin readme says 7.0 or later; go by the plugin readme.
- Cost
- Paid add-ons
- The plugin is free, with no platform fee and no revenue share. Woo’s own pricing page estimates hosting at $25 to $350 a month for most stores and extensions at $29 to $299 a year each. Marketplace prices in October 2026: Subscriptions for recurring billing $279 a year, Bookings $249 a year. Card processing fees are charged by whichever payment provider you choose.
- What to watch out for
- Running it means maintaining WordPress, your theme and every plugin you add. Features such as recurring billing and bookings are not in the free core; you buy them as yearly extensions from the official marketplace. The README says the GitHub repository does not handle support requests: extension customers use the paid support portal, everyone else the community forum on WordPress.org.
- Commercial use
- Conditions
- The core is OSL-3.0; the bundled modules and default theme are AFL-3.0. Running a store on unmodified code adds no obligations. Section 5 of the OSL treats making the software available as a network application as distribution, so if you modify the core and run a public store on it, your modified version must be licensed under OSL-3.0 as well. The license grants no trademark rights: you cannot use the PrestaShop name to promote a product derived from it.
- Maintained
- Active
- Last push on 2026-10-12. The repository is not archived.
- Setup
- Easy
- Download the zip from the official releases page, upload it, create a database and follow the installer in your browser; the version 8 user guide says most people can start configuring about five minutes after the upload. The README states that the source in the GitHub repository is for development and preview only, and a production shop should use the release package. It needs Apache 2.4 or Nginx, PHP 8.1 or later, and MySQL 5.7 or MariaDB 10.2 or later. Windows “might work” but is not actively supported.
- Cost
- Low
- The software is free. On server RAM the docs only say “the more the merrier” and give no figure; they recommend a per-script memory limit of at least 512M. If you would rather not self-host, PrestaShop SA sells a hosted plan: €24 a month billed annually or €29 month to month, both excluding VAT. The page says the hosted plan is based on PrestaShop 8, while the open-source release is already at 9.
- What to watch out for
- Within one major version (9.0 to 9.1, say) you update with the official Update Assistant module, and your theme and modules keep working. Across major versions the recommended route is migration: install a new store, move products, customers and orders over, recreate employee accounts and permissions by hand, and treat every module as incompatible until checked, then reinstall and reconfigure it.
- Commercial use
- Yes
- MIT. Commercial use, modification and closed-source use are all allowed; keep the copyright notice.
- Maintained
- Active
- Last push on 2026-10-12. The repository is not archived.
- Setup
- Easy
- Two routes. A single Docker command starts a fully installed store, with the database and seed data baked into the official image; or create the project with Composer and run one install command that asks for the store URL, database and admin account. Version 2.5 needs PHP 8.4 and Composer 2, with MySQL 8.0, MariaDB 10.11 or PostgreSQL 16. The download page still says PHP 8.3; go by the docs and the code.
- Cost
- Low
- The software is free. The download page lists 4 GB of RAM or more; the developer docs set no RAM requirement and only show the PHP settings shipped in the official image, with a 512M memory limit. If you would rather not self-host, the official cloud hosting starts at $25 a month.
- What to watch out for
- The README introduces it as an “eCommerce and multi-vendor marketplace platform”, but multi-vendor is an extension sold separately by Webkul, the company behind it: $449 in the official store in October 2026, with three months of support and longer support at extra cost. The repository’s package directory does not contain it. The POS, multi-tenant and other items in the README also link to product pages; whether each is paid has not been checked.
- Commercial use
- Conditions
- The code is MIT. Since March 2025 a Fair Usage Policy applies on top: Community Edition merchants with more than €1 million in annual gross merchandise value must take a paid plan to keep access to the Shopware Account and Store; without it they cannot buy new extensions or receive updates for existing ones. Shopware says the MIT license itself is unaffected.
- Maintained
- Active
- Last push on 2026-10-12. The repository is not archived.
- Setup
- Moderate
- The recommended install is Docker-based and only Unix-like systems are supported (Windows via WSL 2 or Docker Desktop). It needs PHP 8.2 or later (8.4 recommended) with a memory limit of at least 512M, plus MariaDB or MySQL. The README also mentions a web-based installer and hosting partners offering it pre-installed.
- Cost
- Higher
- The Community Edition is free. The system requirements page lists a quad-core CPU, 8 GB of RAM minimum with 16 GB recommended, and about 10 GB of disk. Paid plans start at €600 a month for Rise and €2,400 a month for Evolve, excluding VAT, priced on gross merchandise value. The free edition is not offered on Shopware Cloud, so setup and maintenance are yours.
- What to watch out for
- The Fair Usage Policy requires every Community Edition user to report gross merchandise value, including those under €1 million: install the official reporting extension, or submit a form at least once a year. The figure is net of tax, includes shipping, subtracts discounts and does not subtract returns.
- Commercial use
- Yes
- MIT. Commercial use, modification and closed-source use are all allowed; keep the copyright notice. The exception is the Enterprise Edition material identified in the repository (role-based access control and single sign-on), which is not under MIT; see the caveat below.
- Maintained
- Active
- Last push on 2026-10-10. The repository is not archived.
- Setup
- Moderate
- You scaffold a project with the create-medusa-app command, which can also install the official Next.js storefront starter. Locally it needs an LTS Node.js at 20.19 or 22.12 or later, Git and a running PostgreSQL. In production you deploy four things: PostgreSQL, Redis, the application in server mode and the application in worker mode.
- Cost
- Low
- The software is free. The deployment guide asks for a host with at least 2 GB of RAM, plus PostgreSQL and Redis. The managed Medusa Cloud has plans from $29, $99 and $299 a month, with no fee on sales volume.
- What to watch out for
- The project is open core: the code for role-based access control (RBAC) and single sign-on (SSO) sits in the same repository but under a separate Enterprise license, and cannot be used without a commercial agreement with MedusaJS, Inc. The license states that enabling an Enterprise feature flag is a representation that you hold such an agreement. On the pricing page both appear only in the Enterprise tier, priced on request. It is also a developer’s engine: the storefront is yours to build.
- Commercial use
- Yes
- BSD-3-Clause. Commercial use, modification and closed-source use are all allowed; keep the copyright notice, and do not use the project’s or contributors’ names to endorse your product. The README says there is a single version, with no feature fragmentation or commercial limitations.
- Maintained
- Active
- Last push on 2026-10-12. The repository is not archived.
- Setup
- Hard
- To try it locally you clone saleor-platform and start everything with Docker Compose, giving Docker at least 5 GB of memory; that repository is stated to be for local development only, not for production. For production the recommended route is the official Docker image, and you assemble the API service, background workers, a task scheduler, PostgreSQL, Redis and object storage yourself, then deploy the dashboard and storefront separately. Installing on Linux without Docker relies on community-maintained scripts that Saleor does not vouch for.
- Cost
- Depends
- The software is free. The docs give no server sizing for production; the only figure is the 5 GB of memory Docker needs to run the full stack locally. On the managed Saleor Cloud, sandboxes are free but for non-commercial use only; the lowest commercial plan is $1,599 a month covering $200,000 in monthly sales, with 0.8% on orders beyond that, and the next plan is $3,999 a month.
- What to watch out for
- The README has a section on tradeoffs: if you are a single developer working with a small business without high traffic or a need for round-the-clock availability, this service-oriented approach may feel more complex than the WordPress style. It is API-only, so you extend it with separately deployed apps and webhooks rather than plugins. Self-hosted instances also send anonymous usage telemetry by default (version, counts of products and similar entities, configured currencies); set SEND_USAGE_TELEMETRY=false to turn it off.
- Commercial use
- Yes
- LiveKit Server, Egress and the Agents framework for voice AI are all Apache-2.0: commercial use and modification are allowed, and you do not have to publish your changes.
- Maintained
- Active
- Last push on 2026-10-15. The repository is not archived.
- Setup
- Moderate
- LiveKit Server: an official config generator (the livekit/generate image) produces Caddy, Redis, docker compose and a startup script in one go; run the script on a Linux VM and it is up. You need your own domain: the main domain and the TURN domain must both point at the machine, and self-signed certificates do not work (Caddy obtains them automatically). Open ports 80, 443, 7881 (TCP), 3478 (UDP) and the whole UDP range 50000 to 60000. Egress: the generator does not cover it. Run it as a separate Docker service (livekit/egress) with the server’s URL and API key, connected to the same Redis as the server. Full-room recording runs Chrome inside the container, which needs the SYS_ADMIN capability or Chrome fails to start. Recordings go to S3, Azure or Google Cloud Storage. Both have official Helm charts for Kubernetes.
- Cost
- Varies
- Self-hosting is free; the money goes on two kinds of machines. LiveKit Server is bound by CPU and bandwidth: in the official benchmark, one 16-core Google Cloud c2-standard-16 handled a 150-person video meeting where everyone sees everyone, at 85% CPU, and the docs recommend compute-optimized machines and 10 Gbps networking for production. Each Egress instance should have at least 4 CPUs and 4 GB; a full-room recording takes 2 to 6 CPUs, and one instance records one room at a time, so you need as many instances as rooms you record at once. If you would rather not run it all, LiveKit Cloud has a free tier with 5,000 participant minutes and 50 GB of transfer a month; paid plans start at $50 a month, with overage at $0.0005 per participant minute and $0.12 per GB.
- What else you need
- LiveKit Server is required: it runs the rooms and routes the media. Redis is recommended for production and required once you add Egress; both must use the same one. Egress records meetings to MP4 or HLS, or live-streams them over RTMP to platforms like YouTube Live and Twitch; recordings need an S3, Azure or Google Cloud bucket. You also need a domain of your own. Ingress (bringing outside RTMP streams into a room) and Agents (voice AI) are optional and not needed for meetings alone.
- What to watch out for
- The meeting interface, login and permissions are for your own developers to build. The official sample app, LiveKit Meet, is open source, but its README only covers local development, not production. The Chrome inside Egress runs with its sandbox off by default; turning it on takes an extra setting and a seccomp profile.
Your industry is not here?
Tell me the industry and what you need solved. I will look at it next.