22 projectsCommercial useMaintainedSetupCost
LMS3
- Commercial use
- Yes
- GPL-3.0. You can host it and charge for courses without restriction. If you distribute a modified version, it must stay under the GPL.
- Maintained
- Active
- Last push on 2026-10-03. The repository is not archived.
- Setup
- Moderate
- You set up the web server, PHP and a database (PostgreSQL, MySQL or MariaDB) yourself. The official guide has eight steps. The exact PHP version is in the release notes for each version.
- Cost
- Low
- The software is free. The stated minimum is a 1 GHz CPU and 512 MB of RAM; dual core and 1 GB or more is recommended. Plan for 5 GB of disk plus your course content. Moodle’s own hosting, MoodleCloud, is billed yearly: about $170 for 50 users, $500 for 200 (the first plan that can sell courses via Stripe), up to $2,110 for 750. It is charged in AUD, and you cannot install plugins.
- What to watch out for
- "Moodle" is a registered trademark. Without written permission you cannot use the name to sell hosting, training, support or customization; that permission usually goes to official partners only. Saying your own organization runs Moodle is fine.
- Commercial use
- Conditions
- AGPL-3.0. Running it unmodified adds no obligations. If you change the code and let learners use it over a network, you must offer those users your modified source.
- Maintained
- Slowing
- Last push on 2026-04-30. The repository is not archived.
- Setup
- Hard
- The official production guide has nineteen sections. You install Ruby 3.4.1 or later, Node 20, PostgreSQL 14 or later and Redis 6 or later, then configure Apache and Passenger. The guide is written for Ubuntu 22.04.
- Cost
- Moderate
- The software is free. The guide recommends at least 8 GB of RAM when everything runs on one server.
- What to watch out for
- The rich content editor is a separate service you deploy yourself, and the guide says the production branch requires it. The GitHub repository has had no pushes since late April 2026; the reason has not been checked here.
- 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-07. The repository is not archived.
- Setup
- Easy
- There are official installers for Windows, Debian/Ubuntu, Raspberry Pi, macOS and Android, and it can also be installed with pip.
- Cost
- Low
- The software is free. For the machine acting as server, the docs recommend 1 GB of RAM on Linux or 2 GB or more on Windows, and a 1 GHz CPU.
- What to watch out for
- It solves teaching without reliable internet; it is not a storefront for selling courses. Disk space depends on how much content you import.
- Commercial use
- Yes
- LGPL-3.0. You can host it for paid classes without restriction. If you modify its own code and distribute it, those changes must be open.
- Maintained
- Active
- Last push on 2026-10-08. The repository is not archived.
- Setup
- Hard
- It needs a clean, dedicated Ubuntu 22.04 server that does not share ports 80 and 443 with another site, a domain with a valid SSL certificate (browsers will not grant camera and microphone access without one), and UDP ports 16384 to 32768 open. Installation is through the official bbb-install.sh script.
- Cost
- High
- The software is free; the server is the cost. The stated production minimum is 8 cores, 16 GB RAM and 250 Mbps symmetrical bandwidth, with 500 GB of disk if you record sessions or 50 GB if you do not.
- What to watch out for
- What 250 Mbps of symmetrical bandwidth costs on a Chinese cloud has not been checked here; get a quote before deciding. The docs also ask for both an IPv4 and an IPv6 address.
- 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.
- Commercial use
- Yes
- BSD-3-Clause. Commercial use, modification and closed-source use are all allowed; keep the copyright notice.
- Maintained
- Active
- Last push on 2026-10-08. The repository is not archived.
- Setup
- Moderate
- It needs a Linux server, Python 3.10 or later, Node.js, a domain and a TLS certificate. The official Docker image contains only the Hub with no configuration; you set up login and how each student’s environment is started.
- Cost
- Per user
- The software is free. The small official distribution gives a formula: memory = concurrent users × memory limit per user + 128 MB, starting from 40% to 60% of class size as concurrent users. The server needs at least 1 GB of RAM to install.
- What to watch out for
- By default users log in with system accounts on the server, and allowing several users means running it with root privileges. Anything else takes more configuration.
- 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
- Conditions
- MIT terms with an addition: the footer signature carrying the version, commit hash and a link to opensourcepos.org must be kept, must be visible on every page and cannot be modified, and you cannot claim ownership of the software. Running it in your own shop is unrestricted. Reselling it under your own brand is ruled out by that clause.
- Maintained
- Active
- Last push on 2026-10-12. The repository is not archived.
- Setup
- Easy
- Download a release, create a MySQL database, upload the files, put the database credentials in .env, and open it in a browser; the schema is created on first access. It needs PHP 8.2 to 8.4, MySQL 5.7 or MariaDB 10.x, and Apache 2.4 (Nginx works too). For production you must list the allowed hostnames in .env or the app will not start. The bundled Docker Compose setup is described as not suited for production.
- Cost
- Low
- The software is free. The stated minimum is 512 MB of RAM with 1 GB or more recommended, plus 1 GB of disk for the application; Raspberry Pi 3 and 4 are supported. You also buy a barcode scanner and a receipt printer.
- What to watch out for
- The official hardware list says credit card readers are not supported. Cash drawers are out of scope and only open if your printer can trigger them, and scanning barcodes with a phone camera is not supported yet. Printing goes through the browser, so results depend on the browser and operating system.
- 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
- There is a setup wizard: upload the zip to your web root and open setup.php in a browser. It needs PHP 8.3 or later, MySQL 8.0 or MariaDB 10.6 or later, and Apache or Nginx. Afterwards you add one cron entry, and installing extensions later requires Composer.
- Cost
- Paid add-ons
- The core is free and includes online ordering, reservations and multiple locations; Stripe, PayPal, Mollie, Authorize.net and Square are described as supported out of the box. Marketplace prices in October 2026: Table Ordering $49 a year, Dine-In Management $49 a year, Star CloudPRNT printing $50 a year, DocketPrint automatic order printing $75 a year; Kitchen Display is free. The docs give no figure for server size.
- What to watch out for
- It handles customers ordering and booking online, not the till at your counter. The features page describes POS as an integration you add from the extension marketplace, and table ordering and dine-in management are paid extensions. For in-store checkout you need a separate system.
- Commercial use
- Yes
- MIT. Commercial use, modification and closed-source use are all allowed; keep the copyright notice. The exception is the code under the enterprise/ directory of the repository, which has its own Enterprise license: production use requires a paid subscription for the right number of seats. See the caveat below.
- Maintained
- Active
- Last push on 2026-10-13. The repository is not archived.
- Setup
- Easy
- There is an official install script, documented for Ubuntu 24.04: download it and run one install command. If you want a domain, point its A record at the server first and the script sets up Nginx and a Let’s Encrypt certificate. Docker Compose also works: download the official .env and compose templates, change the Postgres and Redis passwords, prepare the database and start. You bring your own SMTP server for notification emails.
- Cost
- Paid tiers
- The Community edition is free. The docs list a minimum of 2 cores, 4 GB of RAM and a 20 GB SSD, and recommend 4 or more cores, 8 GB or more and 50 GB or more for production, plus PostgreSQL 12 or later and Redis 6 or later. In November 2026, the official self-hosted prices were US$19 per agent per month for Premium Support and US$99 for Enterprise, both billed annually. Chatwoot Cloud is free for up to 2 agents, with paid plans at US$19, US$39 and US$99 per agent per month.
- What to watch out for
- The self-hosted pricing page lists what the Community edition leaves out: Captain AI, voice calls, custom branding, agent capacity, roles and permissions, SSO / SAML and SLA policies. The first five come with Premium Support; SSO and SLAs need Enterprise. The code for these sits in the enterprise/ directory of the repository under the Enterprise license. To run only the MIT-licensed part, the docs say to switch to the Docker image tags ending in -ce.
- Commercial use
- Conditions
- AGPL-3.0. Running it unmodified adds no obligations. If you change the code and let customers or staff use it over a network, you must offer those users your modified source. The README states that the code is owned by the Zammad Foundation, which is independent of the commercial provider Zammad GmbH.
- Maintained
- Active
- Last push on 2026-10-13. The repository is not archived.
- Setup
- Moderate
- You can install from packages (CentOS / RHEL 9 and 10, Debian 11 to 13, Ubuntu 22.04 to 26.04, openSUSE Leap / SLES 15 and 16), or use Docker Compose or Kubernetes. It needs PostgreSQL 15 or newer and Redis 7 or newer; the package install sets both up automatically. Docker Compose needs at least 4 GB of RAM, and you first raise the host’s vm.max_map_count to 262144 so Elasticsearch runs properly.
- Cost
- Moderate
- The software is free. The stated minimum is 2 cores and 6 GB of RAM, plus 4 GB if Elasticsearch runs on the same server; the example for up to 40 agents is 6 cores and 6 GB, plus 6 GB for Elasticsearch. The docs make no disk recommendation. If you would rather not self-host, the hosted plans in October 2026, billed annually and excluding VAT, are €7 per agent a month (up to 5 agents), €16 (up to 35) and €25 (unlimited).
- What to watch out for
- The docs call Elasticsearch “optional but strongly recommended”: Zammad runs without it, but search is slower and very limited, and features such as reports and searching inside email attachments rely on it. When you self-host, updates, backups and availability are yours; official support contracts for self-hosted installs start at €2,999 a year excluding VAT. If you deploy with Docker, support covers only the Zammad application, not Docker itself.
ERP1
- Commercial use
- Yes
- The Community edition is LGPL-3.0. You can host it and use it commercially without restriction; if you modify its own code and distribute it, those changes must be open. Enterprise is under a separate license: it can only be used with a valid Enterprise subscription for the correct number of users, and cannot be redistributed.
- Maintained
- Active
- Last push on 2026-10-13. The repository is not archived.
- Setup
- Moderate
- There are official packages: the Odoo 20 deb package currently supports Ubuntu 24.04 and the rpm package supports Fedora 42, with PostgreSQL installed first; a source install is also documented. The Windows installer is described as suitable for testing or single-user local use, and production deployment on Windows is discouraged. For production the docs call for the multi-processing server behind a reverse proxy with HTTPS.
- Cost
- Paid tiers
- The Community edition is free. For server size the docs give a formula: one worker handles about 6 concurrent users, and the maximum number of workers is CPUs × 2 + 1. Their example is 60 concurrent users on 4 CPUs with 8 threads, needing about 3 GB of RAM for Odoo itself. Enterprise list prices in US dollars in October 2026, billed yearly: Standard at $31.10 per user a month, on Odoo’s own hosting only; Custom at $61.00 per user a month, the plan required to run Enterprise on your own server. New orders get a 12-month discount, to $24.90 and $49.00. Light Users are $8.90 per user a month and limited to self-service (time off, expenses, attendance, planning) plus point of sale, shop floor and barcode operations. Every active employee record in the HR app that is not linked to a full user account also counts as a Light User, and the license is quoted through an Odoo advisor. Using a single app on Odoo’s hosting is free for unlimited users.
- What to watch out for
- In the official editions comparison, Community includes Inventory, Purchase, Manufacturing (MRP) and Maintenance, but these are marked as not included: full accounting (Community has invoicing only), barcode, shop floor, control panel and scheduling, PLM, Quality, the mobile apps and Studio. Version upgrades are also an Enterprise service: the docs say upgrading a database to the latest version is free with Odoo Enterprise.
CRM1
- Commercial use
- Conditions
- The core is AGPL-3.0, while files marked @license Enterprise fall under Twenty’s commercial license (requiring a paid subscription) and SDK/UI packages are MIT. An explicit Twenty Application Exception under AGPLv3 Section 7 lets you build proprietary apps and integrations over Twenty’s REST/GraphQL APIs, webhooks and SDKs without triggering copyleft; modifying Twenty itself and serving users over a network still requires offering your modified source.
- Maintained
- Active
- Last push on 2026-11-04. The repository is not archived.
- Setup
- Moderate
- There is a one-line install script as well as an official Docker Compose stack running four services: server, worker, PostgreSQL and Redis. The docs state a hard minimum of 2 GB of RAM (processes crash below that). Before going live you set SERVER_URL, generate a random ENCRYPTION_KEY, and keep special URL characters (@, /, #, %) out of PG_DATABASE_PASSWORD so the unencoded database URL parses cleanly.
- Cost
- Paid tiers
- Self-hosting the Pro tier is free for unlimited users, objects and records (up to 5 workspaces, with field-level custom roles); you only pay for a 2 GB+ RAM server. List prices in November 2026: adding row-level permissions and SSO on a self-hosted install requires the Organization plan at $19 per user a month billed yearly ($25 monthly), with Enterprise starting at $50,000 a year. Official Twenty Cloud hosting is $9 per user a month billed yearly ($12 monthly) for Pro and $39 per user a month billed yearly ($51 monthly) for Organization.
- What to watch out for
- The free self-hosted tier stops at field-level permissions: hiding specific deals or contacts between sales reps requires row-level permissions, which — along with SAML / OIDC SSO and custom AI models — sits in the paid $19/user/month Organization plan. Back up your ENCRYPTION_KEY safely as well: losing it permanently breaks encrypted OAuth tokens and secrets stored in the database.
- Commercial use
- No SaaS
- Licensed under Elastic License 2.0 (ELv2, source-available rather than OSI open source). Running and modifying it for your own business is free, and the official license FAQ explicitly allows web hosts and IT providers to install isolated instances for clients. You cannot offer it as a managed SaaS, bundle it into a commercial SaaS product, circumvent license-key checks, or strip Invoice Ninja branding without a white-label license.
- Maintained
- Active
- Last push on 2026-11-02. The repository is not archived.
- Setup
- Moderate
- Official Dockerfiles and a Docker Compose stack (app, Nginx and MySQL / MariaDB) are maintained alongside the INmanage CLI installer. Bare-metal setup needs PHP 8.2, MySQL 5.7+ or MariaDB 10.3+, Nginx or Apache, and a per-minute Laravel cron job (schedule:run) for recurring invoices and reminders. Watch two install traps: it must sit at the root of a domain or subdomain (subdirectories like /ninja are unsupported), and git clone lacks the prebuilt React admin UI — use the release tarball or Docker image instead.
- Cost
- $40/yr logo
- Self-hosting unlocks all Pro and Enterprise features for $0, with unlimited clients, invoices and team users. The one paid add-on is a $40-a-year White-Label license per self-hosted install (raised from $30 on January 1, 2026) to remove “Created by Invoice Ninja” from client-facing PDFs and payment portals. Official hosted plans are free up to 5 clients, $14 a month ($140 a year) for 1-user Ninja Pro with unlimited clients, and $18 to $300 a month ($180 to $3,000 a year) for multi-user Enterprise tiers.
- What to watch out for
- The official white-label docs note that the $40/year license only removes branding on client-facing PDFs, client emails and the payment portal — the staff admin interface and admin notification emails still carry Invoice Ninja branding by design. Also note that v5 is a ground-up rewrite and cannot be upgraded in place from v4.x.
- Commercial use
- Internal only
- The Sustainable Use License 1.0 covers the core, with a separate Enterprise license for .ee code. An agency may build and run workflows on its own instance for clients. Clients can receive outputs or connect their accounts while the agency alone edits the workflow logic. A commercial license is required when external clients can configure workflows through any interface, API, or agent, or when the agency offers hosting or white-labels n8n. Keep copyright notices intact.
- Maintained
- Active
- Last push on 2026-11-04. The repository is not archived.
- Setup
- Moderate
- A single Docker command starts n8nio/n8n on port 5678 using SQLite by default. For production, official Docker Compose templates pair it with PostgreSQL behind a reverse proxy and HTTPS. The official Docker Compose guide requires at least 2 vCPUs and 4 GB of RAM.
- Cost
- Paid tiers
- Self-hosting Community is free with unlimited workflows, executions and users. The server needs at least 2 vCPUs and 4 GB of RAM. The official euro prices checked in November 2026 were €667 per month for self-hosted Business (under 100 employees, 40,000 monthly workflow executions), and €20 or €50 per month for Cloud Starter and Pro (2,500 or 10,000 monthly executions). Those rates are billed annually. Enterprise is quoted separately.
- What to watch out for
- According to the official Community edition feature list, Community leaves out Projects and workflow or credential sharing: only the instance owner and the person who created a workflow or credential can access it. SSO (SAML / LDAP), environments, Git version control, custom variables, external secrets, log streaming and multi-main high availability are also paid-only (queue mode with workers is included). Folders, debug data pinning and custom execution data are free, but require registering an email address for a free Community license key.
- Commercial use
- Conditions
- Apache-2.0, so commercial use and modification are allowed. The README adds a statement: videos made with it and published on platforms such as Bilibili, WeChat Channels or Douyin must carry the LiveTalking watermark and logo.
- Maintained
- Active
- Last push on 2026-10-09. The repository is not archived.
- Setup
- Moderate
- Tested by the authors on Ubuntu 22.04, Python 3.12 and CUDA 12.8. You install dependencies, download models from a cloud drive, and start it with one command. The official FAQ lists twelve install errors, mostly dependency version conflicts. A Windows bundle and ready-made cloud images also exist.
- Cost
- Needs a GPU
- The software is free; the GPU is the cost. The authors recommend an RTX 3060 or better for the wav2lip model and an RTX 3080 Ti or better for musetalk. How many avatars can speak at once depends on the GPU; idle sessions depend on the CPU.
- What else you need
- A GPU is required. For speech you can use the free EdgeTTS, host GPT-SoVITS or CosyVoice yourself, or call Tencent Cloud (needs an API key). For it to hold a conversation, add an LLM: Qwen and OpenAI-compatible endpoints are supported (needs an API key). For spoken questions you also need a FunASR recognition service, or the browser’s built-in recognition. The server must expose TCP port 8010 and UDP ports.
- What to watch out for
- The open edition ships a voice-input page, but recognition is on you: run a FunASR service, or use the browser’s built-in speech recognition. Wake-word interruption, full-duplex conversation and ready-made cloud speech recognition are in the paid commercial edition; the docs give no price and say to contact the author.
- Commercial use
- Conditions
- The project itself is Apache-2.0. Of the models it uses, LiteAvatar is MIT, LAM and CosyVoice are Apache-2.0, and MuseTalk has MIT code with a README stating that the trained model may be used commercially. Two need care. SenseVoice, used for speech recognition, ships its weights under the FunASR model license, which requires attribution and keeping the model name. Its section 3 (Responsibility and Risk) says the model is “provided for reference and learning purposes only” and does not say whether that limits commercial use. An issue asks exactly that: a maintainer answered that section 3 is a disclaimer and commercial use is permitted, and in September 2026 that answer was marked as not yet the license owner’s final confirmation. The issue was still open on 2026-10-13. The FlashHead model archive includes one component under Open-RAIL-M; with the Pro variant alone, the whole workflow is Apache-2.0.
- Maintained
- Active
- Last push on 2026-07-31. The repository is not archived.
- Setup
- Moderate
- It needs Python 3.11 and an NVIDIA driver that supports CUDA 12.8. With uv it is three steps: install dependencies, download models, start. Docker also works once the NVIDIA Container Toolkit is installed; the app is then served at https://localhost:8282.
- Cost
- Depends
- The software is free. The docs say the 2D avatar is light on hardware and that avatar inference reaches 30 FPS on an i9-13980HX CPU. Moving speech recognition, the LLM and text-to-speech to cloud APIs lowers the hardware needs a lot, in exchange for paying per call. The docs give no figure for GPU memory.
- What else you need
- The default preset uses Alibaba Cloud Bailian for the LLM and text-to-speech, which needs a DASHSCOPE_API_KEY; speech recognition runs locally with SenseVoice. If you would rather stay off the cloud, the docs say local multimodal models are supported too. For remote access, the bundled coturn can be started alongside it.
- What to watch out for
- The release notes in the README say LiteAvatar supports multiple sessions on one machine, while the FAQ says it does not support concurrency; test it to find out. The stated average response time is 2.2 seconds. The FAQ also notes that personal AutoDL accounts cannot open custom ports, so remote access does not work there.
Your industry is not here?
Tell me the industry and what you need solved. I will look at it next.