Ever Gauzy: a monolithic ERP/HRM platform with a headless API and desktop timers

What Ever Gauzy actually bundles

Ever Gauzy is not a single-purpose tool. The README lists five major modules: Enterprise Resource Planning, Customer Relationship Management, Human Resource Management, Applicant Tracking System, and Work and Project Management. On top of that it adds employee time tracking, activity monitoring, invoicing, inventory, supply chain, and production management. That is a wide surface. The intended audience is small to medium organizations, on-demand businesses, freelance operations, agencies, studios, and in-house teams that want one system instead of many. The project also positions itself as part of a larger Ever Platform for collaborative and sharing economies, but this repository is the core business platform. If you only need CRM or only need time tracking, this is overkill. The value is in the combination, not in any single module.

Architecture: a headless API with multiple front ends

The README describes Ever Gauzy as a platform with headless APIs, a web UI, and desktop apps. The API documentation lives at api.gauzy.co/docs. The desktop apps are separate: the Ever Gauzy Desktop App bundles the UI, the API, and a SQLite database into one local package, and a separate desktop timer app handles time tracking. The Server variant includes the API, SQLite or external PostgreSQL, and serves the frontend. This split matters. You can run the full stack locally for personal use, or you can run the Server on one machine and connect Desktop Apps to it in a client-server configuration. The web UI and the desktop timer are not the same application. The timer is a dedicated client for employees and contractors. The headless API is the interesting part for integrators, because it means you can build your own front end or connect Ever Teams, which the README mentions as a separate React-based product that uses Ever Gauzy APIs.

Getting it running: three paths with different trade-offs

The README gives three concrete ways to run Ever Gauzy. First, download the Platform, Server, or Desktop Apps from the official Downloads page at web.gauzy.co/downloads. Second, use the online demo at demo.gauzy.co, where the default super-admin login is [email protected] with password admin, and the database resets daily. Third, run the SaaS at app.gauzy.co, but the README explicitly warns it is in Alpha testing mode and should be used cautiously. For a self-hosted setup, the Server option is recommended for small to medium organizations. The Desktop App is recommended for quick personal use or for connecting to a Gauzy Server. For containers, the repository root carries docker-compose.yml, which runs the published ghcr.io/ever-co/gauzy-api and gauzy-webapp images.

The feature list is long, but depth is uneven

The README lists dozens of features: dashboards with income and expense metrics, employee onboarding, candidate interviews, sales pipelines, proposals, accounting, invoicing, estimates, billing, payments, time off, inventory, equipment sharing, multiple organizations, departments, teams, clients, vendors, help center, tags, reports, integrations with Upwork and HubStaff, email templates, data import and export, roles and permissions, multi-currency, multi-lingual, and multiple themes. That is impressive on paper. The staging environment exists to test releases before production, which suggests some features are still in flux. The demo database resets daily, so you cannot rely on persistent data there. For a platform this broad, you should expect some modules to be shallow. The integrations named are Upwork and HubStaff, followed by "etc.", so check the API documentation for anything else you need.

Licensing: AGPL-3.0 is the main constraint

Ever Gauzy is licensed under AGPL-3.0. That is a strong copyleft license. If you modify the code and offer it as a network service, you must release your modifications under the same license. For internal use, this is usually fine. For a commercial SaaS product, it is a serious consideration. The project also has a separate product Ever Works that is an open agentic runtime, but that is a different repository. The AGPL license is not a problem for every team, but it is a decision point. If your organization is not comfortable with AGPL, this is the wrong tool. Read LICENSES.md at the repository root before assuming the AGPL is the only licence that applies.

Maintenance and upgrade cost: high release cadence, unclear migration path

The repository shows recent releases v111.146.5, v111.146.4, and v111.146.3, all published within minutes of each other on 2026-11-02. That is a very active release schedule. Version numbers in the triple digits indicate frequent, possibly automated releases. For a user, that means constant updates. The staging environment is used to test releases before production, which is good practice, but it implies that the project team themselves do not trust every release to be stable. If you self-host, you will need to plan for regular upgrades. Pre-releases of the desktop and server apps are built from the staging environment, so a pre-release build may be less stable. The maintenance cost is not trivial. You are not deploying a static tool; you are deploying a living platform with daily commits.

Alternatives and where Ever Gauzy fits

The obvious alternative is Odoo, which is also an open source ERP/CRM suite, but Odoo uses a different architecture: it is Python-based, has a modular app store, and uses a proprietary license for some enterprise modules. Ever Gauzy is TypeScript throughout, which matters if your team is a JavaScript/Node.js shop. Ever Gauzy's differentiator is the desktop timer apps and the headless API. If that feature is critical, Ever Gauzy has a real edge. If you need a mature accounting module or a huge ecosystem of third-party apps, Odoo is more established. The README itself notes the SaaS is in Alpha. Choose based on your stack and your tolerance for a fast-moving project.

The desktop timer is the feature that justifies the complexity

The Desktop Timer App is the most concrete differentiator in the README. The README lists time tracking, activity tracking and timesheets among the features and shows separate Desktop Timer UI screens. That is a specific tool that web-only ERP systems do not provide. For a remote team that needs to verify work hours, this is a practical feature. But it also raises privacy concerns. If your organization values employee privacy, verify what the timer captures and whether that can be configured. The desktop app bundles the entire API and database, which means a single binary can run the whole platform. That is convenient for a small office.

Editorial conclusion

Adopt Ever Gauzy if you want a single open source system that covers ERP, CRM, HRM, ATS and time tracking without stitching together five separate tools, and you can accept AGPL-3.0. Do not adopt it if you need a lightweight module, if your team lacks TypeScript experience, or if you expect the SaaS at app.gauzy.co to be production-ready, since the README calls it Alpha. Before committing, verify the current state of the demo database reset cycle, test the Server against your own PostgreSQL instance, and check whether the headless API at api.gauzy.co/docs covers the exact entities you need for your invoicing or inventory flows.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes