# WebVella ERP Architecture, Extensions, and Adoption Constraints > WebVella ERP is an ASP.NET Core 9 ERP and CRM platform designed around pluggable business functionality and PostgreSQL. The repository offers useful architectural separation, but its documented deployment evidence remains Windows-only and its custom licence requires direct review. **WebVella/WebVella-ERP** — Free and open-source pluggable ERP and CRM software based on ASP.NET Core 9, RazorPages and PostgreSQL . Targets Linux or Windows as host OS. - Repository: https://github.com/WebVella/WebVella-ERP - Website: https://webvella.com/documents/developer/introduction/overview - Stars: 1,495 · Forks: 540 - Language: C# - License: NOASSERTION - Published: 2026-10-16 · Updated: 2026-10-16 · Language: en - Canonical page: https://hysenlabs.com/projects/webvella-webvella-erp ## What WebVella ERP Targets WebVella ERP addresses business data management through an ERP and CRM application that developers are expected to extend. Its stated design goal is "extreme customization and plugability," which distinguishes it from an application intended to run unchanged after installation. The intended audience is therefore software teams that need to model or modify business workflows rather than users looking only for a packaged accounting or sales interface. The technical baseline is specific. The project targets ASP.NET Core 9 and uses Razor Pages, while PostgreSQL 16 is its preferred database. Linux and Windows are named as possible host operating systems. However, the README also says the project is currently tested only on Windows. That qualification matters because platform support and platform validation are different claims. A Linux deployment target is stated, but the repository does not claim equivalent Linux testing. The repository is not archived, and its last push was on 2026-10-03. This supports describing the code base as recently changed, but it does not by itself establish a release schedule. There are no GitHub releases, so the README and repository entries provide no versioned upgrade trail through GitHub Releases. ## The Plugin and Site Project Structure The repository layout exposes the main extension mechanism more clearly than the short README. A core solution named `WebVella.ERP3.sln` sits alongside a console application, shared ERP code, a web project, and a WebAssembly project. Plugin assemblies include CRM, mail, MicrosoftCDM, Next, and Project. Each named plug-in has a corresponding site project, such as `WebVella.Erp.Plugins.Crm/` and `WebVella.Erp.Site.Crm/`. This pairing suggests a separation between reusable plugin code and the site layer that exposes or integrates it. The repository also contains `WebVella.Erp.Plugins.SDK/`, `WebVella.Erp.Plugins.Mail/`, and `WebVella.Erp.Plugins.MicrosoftCDM/`, indicating that the project treats extension work as part of the solution rather than as an afterthought. The related `WebVella-ERP-StencilJs` repository may matter to front-end work, but the repository description does not explain how it is connected, so its runtime role should not be assumed. The actual request path, database access pattern, plugin discovery mechanism, and authentication flow are not documented in the README. The directory names establish an architectural direction, but they do not prove whether plugins are loaded through dependency injection, reflection, configuration, or another mechanism. ## ERP and CRM Boundaries in the Solution The solution includes both general ERP code and CRM-specific boundaries. `WebVella.Erp/` appears to be the main library area, while `WebVella.Erp.Plugins.Crm/` and `WebVella.Erp.Site.Crm/` isolate CRM functionality. Separate mail, project, MicrosoftCDM, and Next plugin projects follow the same pattern. For an engineering team, this can reduce the need to place every business capability in one application project, provided the build and deployment process keeps the paired plugin and site projects aligned. That structure also creates a maintenance obligation. A change to a CRM plugin may need corresponding attention in the CRM site project, and the repository does not explain versioning or compatibility rules between them. There is no documented list of stable extension contracts in the README. Consequently, the layout should be treated as evidence of modular organization, not as proof of a supported public plugin API. The SDK project may be relevant to teams writing additional modules, but the README does not document its public interfaces, packaging procedure, or compatibility policy. Engineers evaluating the project for extension work would need to inspect that project and the documentation before estimating integration effort. ## Getting WebVella ERP and Performing a First Check The README does not provide a complete installation or first-run tutorial. It links the project to its developer documentation and identifies `WebVella.ERP` as a NuGet package, but it does not give an exact installation command, database creation command, configuration file, startup command, or port. Because those details are absent, this article does not invent a setup sequence. A first practical check would begin with the linked developer documentation, followed by inspection of `Config.json` and `global.json` in the repository. Those are concrete project files, but their contents are not shown here, so no configuration claim can be made from their names alone. The PostgreSQL version requirement is documented as PostgreSQL 16. The README identifies Linux and Windows as host targets but explicitly says only Windows has been tested. The absence of a short setup path is itself relevant. A team cannot assume that installing the NuGet package is equivalent to deploying the full ERP site, nor can it infer a connection string format from the repository name. Confirming the supported startup path is a prerequisite for adoption. ## Testing Scope and Platform Boundaries The clearest limitation in the README is its statement that WebVella ERP is currently tested only on Windows. Linux is named as a supported host target, but the project does not document Linux CI results, Linux-specific instructions, or a Linux validation matrix. Teams that operate primarily on Linux should treat this as a documented validation gap rather than assuming parity with Windows. The repository has no GitHub releases. That means the repository does not identify a sequence of tagged releases that would let an adopter correlate deployed code with a published upgrade milestone. The solution contains many projects and plugins, so an upgrade could affect multiple assemblies even though the README does not document their versioning policy. This is not a claim that Linux deployment will fail. It is a narrower point: the project states Linux as a target while naming Windows as the only tested platform. That distinction should shape deployment review, especially where Linux is the required production environment. ## Licence and Dependency Review The repository identifies `LICENSE.txt` as the authoritative licence file and describes the licence as custom rather than using a standard GitHub classification. The README does not reproduce the permissions, restrictions, attribution requirements, redistribution conditions, or commercial-use terms. Those details cannot be inferred from the statement that the software is free and open source. Anyone considering redistribution, modification, hosting, or incorporation into another product must read `LICENSE.txt` directly. The README also points to `LIBRARIES.md` for third-party libraries. That is the relevant file for reviewing bundled dependencies and their licence information. The available repository description does not list the individual libraries or their terms, so dependency obligations cannot be assessed from the README alone. The `WebVella ERP Document Templates License` badge points to a licence file, but the repository description still states that the project uses a custom licence. The badge should not be read as a substitute for reviewing the complete `LICENSE.txt` text. ## A Different Approach to ERP Extension WebVella ERP can be compared conceptually with a conventional packaged ERP application. A packaged application generally provides a fixed set of modules, screens, and configuration options, while WebVella ERP exposes plugin and site projects for custom business capabilities. Its approach is therefore closer to an extensible application foundation than to a fixed feature bundle. The practical trade-off is control versus initial simplicity. Developers gain direct access to C# projects and can organize CRM, mail, project, and integration concerns separately. They also inherit responsibility for understanding how the plugin and site projects are built, packaged, deployed, and kept compatible. The README does not document a formal plugin marketplace, extension lifecycle, or compatibility guarantee, so those benefits should not be converted into assumptions about vendor support. This distinction is most useful for teams that already have application-development capacity and specific business requirements. A team seeking a ready-made ERP with predictable configuration surfaces may find the pluggable model less direct. ## Conclusion WebVella ERP fits developers who want to extend an ERP or CRM through separate plugin and site projects and accept PostgreSQL as the database. It is a poor fit for teams requiring documented Linux validation or expecting a conventional, fully identified open-source licence without reviewing LICENSE.txt first. Before adoption, verify the custom licence terms, the intended plugin integration path, PostgreSQL deployment requirements, and whether your Linux workflow is covered by the project's Windows-only testing statement. ## FAQ ### What technology stack does WebVella ERP use? WebVella ERP targets ASP.NET Core 9 and uses Razor Pages. Its preferred database is PostgreSQL 16. ### Does WebVella ERP support Linux deployment? The README identifies Linux and Windows as possible host operating systems, but it says that the project is currently tested only on Windows. The repository does not document Linux validation results. ### How does WebVella ERP support customization? The repository contains separate plugin projects for CRM, mail, MicrosoftCDM, Next, and Project, along with corresponding site projects and an SDK project. The README does not document the plugin loading or compatibility mechanism. ## Sources - [Issues](https://github.com/WebVella/WebVella-ERP/issues) - [Project website](https://webvella.com/documents/developer/introduction/overview) - [README](https://github.com/WebVella/WebVella-ERP/blob/master/README.md) - [WebVella/WebVella-ERP on GitHub](https://github.com/WebVella/WebVella-ERP) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/webvella-webvella-erp