Answer in brief: Ever Gauzy is an actively developed, open-source business management platform written in TypeScript. It combines ERP, CRM, HRM, applicant tracking, project management, and employee time tracking in one codebase. As of 6 August 2026, it is a credible candidate for organizations with engineering and operations capacity that want a self-hosted, extensible suite. It is not a turnkey product: the most recent release entries observed are tagged as prereleases, the repository default branch is develop, production deployment assumes Kubernetes and several supporting services, and you should verify edition licensing and data-export capabilities before committing. This is a source and documentation review; no local installation or runtime testing was performed.

Key facts at a glance

What Ever Gauzy actually is

According to the repository README, Ever Gauzy is an open business management platform for collaborative, on-demand, and sharing economies. It covers enterprise resource planning (ERP), customer relationship management (CRM), human resource management (HRM), applicant tracking (ATS), work and project management, and employee time, activity, and productivity tracking. The README also lists accounting, invoicing, billing, payments, inventory, multi-organization management, multi-currency, multi-language, roles and permissions, reports, data import/export, and integrations with services such as Upwork and HubStaff.

The technical stack is a TypeScript monorepo built with Node.js, NestJS, Angular, Nx, and Lerna, with TypeORM, MikroORM, and Knex for data access. The maintainers also describe headless APIs and point to a separate project, Ever Teams, that connects to Gauzy APIs. Gauzy is a platform to build on, not just an application to log into.

What the latest releases signal

The most recent release in the review data is v111.19.7, published on 5 August 2026 and tagged as a prerelease. Its notes describe timesheet fixes for timezone handling, daylight-saving rollover, and midnight crossing, plus an end-to-end test that sweeps IANA timezones. The same-day entries v111.19.3 through v111.19.6 cover AI chat defaults, OpenRouter free-tier fallback fixes, a UI click-blocking fix, and CI runner changes.

Two takeaways for operators. First, the project is actively maintained, with several releases in a single day and changelogs specific enough to review before upgrading. Second, the five most recent release entries observed are all tagged as prereleases, and the repository default branch is develop, so you should pin releases and test upgrades rather than assume stable release discipline.

Who should consider Ever Gauzy

Gauzy is a reasonable candidate if your organization wants one extensible codebase covering time tracking, HR, projects, CRM, and invoicing, and if you have developers or a trusted technical partner to run it. The maintainers position it for companies, on-demand businesses, freelance businesses, agencies, studios, and in-house teams.

If you have no engineering capacity and need a supported, turnkey system, Gauzy is currently a weak fit: the README describes the hosted SaaS at app.gauzy.co as in alpha testing mode, and the production path assumes self-hosting with significant infrastructure. Plan on either in-house operations or outside help.

Maintenance signals to weigh

The repository’s public GitHub data as of 6 August 2026 shows 4,258 stars, 850 forks, and 454 open issues, with the last push on 5 August 2026 and multiple releases published that day. By these signals, the project is alive and actively maintained.

Long-lived open issues are worth reading before you commit: an import/export epic has been open since 2019, appointment scheduling and seeds-and-demos epics since 2020, and an open enhancement from January 2026 proposes replacing the icon pack. These do not mean the product is broken, but they indicate which areas are still maturing and should be checked against your own needs.

Deployment concerns

The README recommends PostgreSQL or MySQL for production, with PostgreSQL 16.x suggested, and Kubernetes rather than Docker Compose. A full compose setup includes OpenSearch, MinIO or S3-compatible storage, Redis, Jitsu, and Cube, although the README states the platform works without some of these for demo and testing purposes, with advanced reporting or data-ingestion capabilities disabled. Confirm which services your reporting and analytics actually need before sizing infrastructure.

Known friction points: building the full platform locally is described by maintainers as an extremely long process; demo images ship with documented default admin credentials that should be changed immediately in any real environment; and a seed command is explicitly described as unsafe for production. A public issue also documents a user who could not stop the web app from calling localhost for the API despite environment configuration, which makes API base URL and host configuration a specific thing to test in your own deployment.

Given the prerelease tagging and develop default branch, operators should pin to a specific tag, exercise the upgrade path in staging, and back up the database before applying any release.

Licensing and data-portability caveats

GitHub lists the repository license as AGPL-3.0, but the README describes a layered model: a Community Edition license by default, plus Small Business and Enterprise edition licenses, with a free license and hosting option for qualifying non-profit and open-source projects at the maintainers’ discretion. Confirm in writing which edition applies to your organization and your revenue model before production.

On data portability, the README lists data import/export as a feature, but a dedicated full export-and-import epic has remained open since 2019. Test export and restore for the specific entities you depend on before loading real data.

Alternatives and evaluation questions

Compare Gauzy against more established self-hosted business suites such as Odoo or ERPNext, and against narrower tools if you mainly need one function such as time tracking or CRM. The deciding factor is usually which system you can operate and upgrade for years, not which has the longest feature list.

Questions to answer before production:

• Does your team have TypeScript, NestJS, or Angular experience for debugging and extending a large monorepo?
• Can you operate PostgreSQL plus the supporting services, or is managed hosting a hard requirement?
• What is your upgrade policy when multiple prerelease tags arrive in a single day?
• Have you validated the timesheet and payroll-related flows for your tax, currency, and timezone rules?
• Does the applicable edition license cover your user count and revenue model?
• Can you export the data you care about, and does a restore actually work?

Verdict

Ever Gauzy is a serious, actively maintained open-source platform with an unusually broad feature surface, and it deserves a pilot for teams that can handle a large TypeScript codebase and a Kubernetes-class deployment. It is not the right choice if you need a turnkey system today: treat the hosted SaaS as alpha per the README, expect custom development or integration work, and verify licensing, upgrades, and data export before making it your system of record. This review is based on the repository, releases, and issues, not on runtime testing, so validate the platform in your own environment before production.

Sources

• Ever Gauzy repository and README
• Ever Gauzy release v111.19.7
• Ever Gauzy release v111.19.3
• Open issue: Import / Export of Data
• Open issue: Web app API connection question
• Gauzy platform documentation

If you are weighing Gauzy against your actual workflows, I can help: at XP812 I work on custom business software and legacy system modernization, which includes evaluating open-source platforms, planning self-hosted deployments, and setting up the maintenance and upgrade process around them. I can review your requirements against Gauzy’s current state before you invest in infrastructure.