The short version
Ever Gauzy is an ambitious attempt to put most of a company's operational software behind one roof. Its stated scope spans ERP, CRM, HR, applicant tracking, project management, time tracking, employee activity monitoring, accounting, and inventory. Many open-source systems manage business records, and many track time, but Gauzy explicitly connects work, people, customers, costs, and productivity.
The tradeoff is clear: this is a very large system. It is best approached as business infrastructure, not as an app somebody casually runs on a spare server. The AGPL-3.0 license also deserves review before customization or network deployment, especially in a commercial setting.
What it actually covers
The README describes a broad product surface. HR features include employees and contractors, onboarding, rates, time off, approvals, schedules, performance monitoring, and candidate interviews. Work management covers projects, tasks, goals, KPIs, objectives, and key results. Customer and revenue operations extend through contacts, leads, sales pipelines, proposals, billing, payments, estimates, invoices, income, and expenses. Inventory, equipment sharing, departments, teams, vendors, knowledge-base content, reporting, public pages, roles, permissions, multiple currencies, multiple languages, and themes fill out the suite.
There are several ways to use it. The project advertises headless APIs, a browser platform, a packaged server, a full desktop app, and a smaller desktop timer. The server can use SQLite or connect to PostgreSQL, according to the README. The full desktop package combines the interface, API, and database, while the timer focuses on time and activity tracking, including screenshots and employee monitoring. That range could suit organizations where office staff need the full system but contractors need only a timer.
The project provides a public demo, downloads, API documentation, a wiki, staging builds, and a hosted service. However, the README explicitly calls its documentation a work in progress and its SaaS offering alpha software that should be used cautiously.
What happened when we ran it
We cloned commit cb18696 and tested it in a fresh Debian container with 3 CPUs, 8 GB of RAM, Node 22, no secrets, and no elevated privileges. The checkout was 115.3 MB and contained 13,225 files with roughly 876,052 lines of source. It uses Yarn workspaces and is organized as a monorepo.
The dependency installation did not finish within the 900-second limit. The tail of the log repeatedly said that workspaces can only be enabled in private projects. That is the only concrete diagnostic the captured tail provides, so it would be speculation to blame a package, registry, or system dependency. Because installation did not complete, we did not reach a build or test run. We therefore cannot claim that the checked-out commit builds or passes tests in our environment.
Repository signals show substantial automation: we detected 70 CI workflow files. We also found a Compose file, but no Dockerfile, and no top-level tests directory. The absence of that directory does not prove the absence of tests in a monorepo; it only describes our scan. The evidence says source deployment needs more investigation than the polished downloads section might suggest.
Where Gauzy is strong
Its strongest argument is operational continuity. A project task can sit near a timesheet; labor cost can sit near invoicing; employees, candidates, teams, clients, and vendors can share one permission model. If those connections fit your processes, consolidation can be more valuable than choosing the best isolated application in every category. Headless APIs also make Gauzy relevant as a back-office system behind another interface, and the README points to Ever Teams as one client of those APIs.
Deployment choices are another practical strength. The packaged server targets small to midsize organizations, while desktop applications support local or client-server arrangements. SQLite offers a plausible evaluation path, and PostgreSQL is available for an external database setup. The demo resetting regularly is useful for exploration, although its published default administrator credentials make it a disposable demo, not a deployment model.
Rough edges and risks
Breadth creates implementation risk. A company adopting Gauzy is not configuring one workflow; it may be deciding how HR, surveillance-sensitive activity data, finance, sales, and permissions interact. Screenshot and activity monitoring require a clear employee policy, restricted access, retention decisions, and legal review appropriate to the jurisdictions involved. The feature list is not a substitute for that governance.
The setup result is the immediate technical warning. Fifteen minutes without a completed install is a poor first-run experience, though it is not proof that supported download packages fail. The huge monorepo also raises the cost of debugging, upgrading, and contributing. A Compose file without a detected Dockerfile leaves questions that evaluators should answer through the current deployment documentation rather than repository guesswork.
Community and release health
The repository has 4,571 stars and 455 open issues. Those numbers show meaningful visibility and a sizable unresolved queue, but they do not reveal response time, maintainer capacity, or issue quality. The latest listed release is v111.0.11 from July 4, 2026, and the repository was pushed on September 13, 2026. That is evidence of current development. One release date is not enough to calculate a release cadence or promise timely fixes.
Where it fits in a real stack
Treat Gauzy as a potential system of record for internal operations, backed by deliberate database, backup, identity, mail, and observability choices. Test the headless API if a custom employee or customer experience is required. Pilot one bounded workflow, such as projects plus time and invoicing, before importing every HR and financial record.
Compare ERPNext or Odoo when classic ERP depth and ecosystem are the priority. Compare Kimai when the actual requirement is time tracking and billing. Gauzy earns its place when its employee-monitoring, desktop, project, and business-management combination is specifically valuable. For that buyer it is unusually complete on paper, but our install result makes a hands-on deployment rehearsal a non-negotiable purchasing step.