Answer in brief: ModernWMS (fjykTec/ModernWMS) is a free, open-source warehouse management system that its maintainers say was derived from their commercial ERP work and released for small and medium-sized enterprises. As of the August 15, 2026 snapshot, it is worth evaluating as a low-cost starting point for a small warehouse or as a base for custom inventory development, but only if your team can accept a repository with no pushes since June 22, 2025, no published GitHub releases, and a license mismatch between GitHub metadata (Apache-2.0) and the README (MIT).

This is a source and documentation review based on the public GitHub repository, README, and issue tracker as of August 15, 2026. No local installation, runtime testing, or benchmarking was performed, and claims from the README are attributed to the maintainers rather than verified here.

Key facts at a glance

What ModernWMS is and what it is not

The repository describes ModernWMS as a ‘simple and complete’ open-source warehouse management system derived from the maintainers’ years of ERP project implementation, with commercial WMS functionality stripped out and released free to help small and medium-sized enterprises. The maintainers state the system supports cross-platform deployment.

Per the README, the stack is a Vue 3.2.45 frontend with TypeScript 4.1.2, Vite 4.0.0, and Vuetify, backed by .NET 7.0.0 and built with Node.js 16.13.1. The README also advertises Docker support, QR code support, internationalization, and database support badges for MySQL 8.0+, SQL Server 2017+, and PostgreSQL 12.

This is not a hosted SaaS product with a support team, and it is not a full ERP. It is a self-hosted application you compile and run yourself, with the implied duty to secure, back up, and maintain it.

Maintenance signals you should weigh

The repository is not archived, but its activity points to slow upstream maintenance. GitHub shows the last push on June 22, 2025, about 14 months before this review, and the repository has no published GitHub releases. The README references a Docker image tag (modernwms/modernwms:1.0), but there is no tagged release history on GitHub to anchor versions or changelogs.

Multiple issues opened in 2023 remain open, including reports of login timeouts after Docker deployment, ‘undistributed menu access’ errors when logging in with the default account, API 400 errors, and base-data dropdowns that cannot be selected. A maintainer-created next-version planning issue opened in May 2023 saw activity into May 2025 but remains open. Open issues do not prove the software is defective, but they show that bug fixes move slowly, which matters if you depend on this system in production.

License: resolve the contradiction

GitHub metadata lists Apache-2.0 as the repository license, while the README states the project is distributed under the MIT license and links to a LICENSE.txt file. That difference matters for adoption: permissive either way, but not interchangeable when you build commercial products or ship code to customers. Read the LICENSE file in the code you actually deploy and, if needed, ask the maintainers which license governs it.

Deployment concerns from the README

The documented path is build-from-source: install .NET SDK 7 and Node.js 16, compile the frontend and backend with yarn and dotnet publish, serve the frontend through Nginx, and run the backend on port 20011. The README also offers a Docker path using modernwms/modernwms:1.0 with ports 20011 and 80 exposed.

Two patterns stand out as risks. First, the Docker instructions require editing files inside the running container, replacing 127.0.0.1:20011 with the deployment IP address; that is fragile and a sign that configuration is not fully externalized. Second, the install walkthrough copies a local wms.db file into the backend folder, while the README separately advertises MySQL 8.0+, SQL Server 2017+, and PostgreSQL 12 support; the documented path does not show how to configure those external databases.

The README also documents default credentials of admin with password 1. Combined with a pinned toolchain (.NET 7 and Node.js 16, both past their official support windows as of this review), production evaluation should include a security review: change or disable the default account, verify authentication and menu-permission behavior given the open issues, and control access to the backend port.

Who should consider ModernWMS

Consider ModernWMS if you run a small or mid-sized warehouse, have a limited IT budget, and have someone who can own a Vue and .NET codebase. That is the profile the maintainers describe: SMBs with real warehouse and inventory needs but no budget for commercial WMS or ERP licensing.

Consider it as a scaffold if you evaluate open-source inventory software as the foundation for custom business workflow development. The project is small enough to read and modify, and permissive licensing (once confirmed) supports that kind of use, provided you are prepared to maintain your fork, because upstream activity is slow.

Do not treat it as the safe default if you need a supported, actively patched system, multi-site orchestration, or ready-made e-commerce and accounting integrations. In those cases, pick a maintained alternative or budget for custom development to close the gap.

Checklist before production

• Confirm the governing license from the LICENSE file in the code you deploy; GitHub metadata and the README disagree.
• Run a security review of the default admin/1 credentials, authentication, menu permissions, and backend port exposure.
• Test the flows behind the open issues: Docker deployment login behavior, menu assignment for new accounts, and base-data entry.
• Decide your database path early and verify the advertised MySQL, SQL Server, or PostgreSQL support, since the install guide centers on a copied wms.db file.
• Plan for the toolchain: .NET 7 and Node.js 16 are past official support, so budget for runtime upgrades or container isolation.
• Create your own release, backup, and rollback process, because the project publishes no GitHub releases and the Docker path relies on a fixed image tag plus manual container edits.

Alternatives and questions to ask before committing

Compare ModernWMS against commercial WMS/ERP options and other open-source inventory systems you can actually run. Judge it by whether the process coverage and integration surface match your operation and whether you can maintain it, not by how popular the repository is.

Questions worth asking: How many SKUs and locations do you manage? Do you need QR or barcode scanning at receiving, picking, or shipping, and does the README’s advertised QR support fit your hardware? Do you need integrations with e-commerce, accounting, or ERP systems? Who on your team can maintain a Vue and .NET codebase and handle upgrades? How long can you tolerate an unresolved open issue, given the history here?

Verdict

Conditional recommendation. If you have development capacity, a modest warehouse operation, and a willingness to own security and maintenance, ModernWMS can be a low-cost foundation for a warehouse management rollout, with custom development filling the gaps. If you need a maintained, documented, and supported system with a clear upgrade path, it is not that today.

Nothing in this review verifies runtime behavior. Treat the demo, screenshots, and feature claims as maintainer assertions and validate them in your own environment before committing data or users.

Sources

• fjykTec/ModernWMS repository
• ModernWMS README
• Issue #45: login timeout after deployment
• Issue #27: undistributed menu access with the default account
• Issue #28: base data cannot be added
• Issue #19: next version planning
• ModernWMS homepage

I am Xiang Peng at XP812, and I work on custom inventory, ERP, and business workflow development. If ModernWMS looks close to your needs but not quite there, that gap is where I usually start: planning the evaluation, checking licensing and deployment risk, then building the integrations and owning the upkeep. A short conversation about your warehouse processes is enough to tell whether it is worth pursuing.