EmpCloud Emp-Exit
github.com
- Free trial
- Web
- API
- Self-hosted
What EmpCloud Emp-Exit is
EmpCloud Emp-Exit is an employee offboarding module for managing departures such as resignations, terminations, retirements, and contract endings. Configurable notice periods and clearance workflows support sign-off by teams including IT, Finance, HR, Admin, and managers. Settlement calculations cover pending salary, leave encashment, gratuity, deductions, and notice recovery, with manual adjustments and approval; EMP Payroll is an optional salary-data source. Employees can submit resignations, check their exit status and checklist, complete interviews, and send an exit NPS survey. Other described workflows include asset returns, knowledge transfer, PDF exit letters, background verification, an alumni directory, and rehire. Analytics include 0–100 flight-risk scores, risk-factor analysis, department heatmaps, attrition trends, and exit data. Six branded email templates can be previewed and customized, with delivery logging. Authentication uses OAuth2/OIDC through EMP Cloud, which must be running. The project documents an OpenAPI 3.0 specification through Swagger UI at /api/docs and is licensed under AGPL-3.0. Setup instructions list Docker Compose, Node.js 20+, pnpm 9+, MySQL 8+, and Redis 7+ as requirements.
Who it suits
Emp-Exit suits organizations that need structured departure, clearance, settlement, and employee self-service workflows. Its setup is aimed at teams able to run EMP Cloud and meet the listed software prerequisites.
Good to know, and what to watch
- Supports configurable notice periods and departmental clearance.
- Settlement calculations include several pay and deduction categories.
- Employees can track exit status and complete interviews.
- Includes asset return, knowledge transfer, and rehire workflows.
- Documents an OpenAPI 3.0 specification.
- EMP Cloud must be running for authentication.
- Setup lists Node.js, pnpm, MySQL, and Redis prerequisites.
- EMP Payroll is only an optional salary-data source.
Plans
Every plan and priceEnterprise / Diamond
Essentials / Bronze
Standard / Silver
Premium / Gold
Open source
Getting started
- Open the EmpCloud Emp-Exit repository
- Run EMP Cloud for OAuth2/OIDC authentication
- Install Node.js 20 or newer, pnpm 9 or newer, MySQL 8 or newer, and Redis 7 or newer
- Start the project with Docker Compose
- Use Swagger UI at /api/docs for the documented API
Limits to check
EmpCloud advertises a 15-day free plan. Listed paid tiers cover 1–10, 11–50, and 51–200 users; organizations above 200 users receive a personalized quote.
The Club's review
EmpCloud Emp-Exit is an employee departure management module for organizations handling exits across HR, IT, Finance, and payroll. It is most compelling for teams already using EMP Cloud that want offboarding and attrition analysis in one workflow. The broad scope comes with a practical cost: setup depends on a running EMP Cloud environment and a self-hosted technical stack.
Overview
Emp-Exit covers resignations, terminations, retirements, and contract endings, with configurable notice periods. It combines clearance, settlement, employee self-service, and attrition analysis, giving HR a way to coordinate operational tasks and examine departure patterns in the same product.
That breadth is useful when departures involve multiple departments and formal sign-offs. It is less suited to organizations seeking an independent, ready-to-run service: authentication runs through EMP Cloud, which must be running, and deployment calls for Node.js 20+, pnpm 9+, MySQL 8+, and Redis 7+. Docker Compose is part of the quick-start instructions.
Key features
Clearance and final settlement
Clearance workflows can route sign-off to IT, Finance, HR, Admin, and managers. Exit checklists, asset recovery, access removal, and final documentation address the handoffs that can otherwise be scattered across teams. Full and final settlement calculations cover pending salary, leave encashment, gratuity, deductions, and notice recovery, with manual adjustments and approval. EMP Payroll is optional as a salary-data source, so teams should consider how they will supply payroll information if they do not use that product.
Employee self-service and follow-through
Employees can submit resignations, check status and checklist items, complete exit interviews, and submit an exit NPS survey. The repository also describes knowledge transfer, PDF exit letters, background verification, an opt-in alumni directory, and a rehire workflow. These features make the module broader than a clearance checklist, though organizations will need to decide which parts fit their own departure process.
Attrition insight and communications
Flight-risk scoring on a 0–100 scale, risk-factor analysis, department heatmaps, attrition trends, and exit analytics give teams several views of workforce departures. Six branded email templates cover exit milestones and support preview, customization, and delivery logging. This combination is useful for teams that want to pair routine exit communications with attrition monitoring.
API and licensing
A Swagger UI at /api/docs documents an OpenAPI 3.0 specification, which can help technical teams understand the API surface. The project uses OAuth2/OIDC authentication through EMP Cloud and is licensed under AGPL-3.0. Organizations considering deployment or modification should account for that license and the EMP Cloud dependency.
Pricing
EmpCloud’s pricing page advertises a 15 day free plan, but does not identify it separately as an EMP Exit trial. The listed tiers are billed per user per year: Essentials / Bronze is $22 a year for organizations with 1–10 users; Standard / Silver is $44 a year for 11–50 users; and Premium / Gold is $66 a year for 51–200 users. Enterprise / Diamond has custom pricing for organizations above 200 users.
The per-user annual structure makes the smaller tiers straightforward to compare by organization size, while Enterprise requires a personalized quote. The plan descriptions do not distinguish feature access among tiers, so the listed prices establish audience bands rather than feature trade-offs. The product is described as open source and free, but those plan prices and the 15 day free plan are also part of EmpCloud’s pricing offer; teams should clarify which applies to their intended EMP Exit deployment.
Platforms
Emp-Exit is offered as an API, web application, and self-hosted software. Self-hosting gives technical teams deployment control, but the prerequisites and EMP Cloud requirement make it a more involved choice than a hosted web-only tool.
Who it's for
Emp-Exit suits organizations that already operate EMP Cloud and need coordinated employee departures, settlement calculations, and attrition reporting. It is a particularly relevant option where several departments share clearance responsibilities and employees should be able to track their own exit steps. Teams without EMP Cloud, or without the technical capacity to manage the stated deployment stack, should consider a less dependent alternative.
Pros and cons
Pros
- Wide departure coverage: Clearance, settlement, self-service, documentation, and follow-up workflows sit within one module.
- Cross-team coordination: Sign-offs can involve IT, Finance, HR, Admin, and managers, while checklists address assets and access removal.
- Operational and analytical scope: Exit NPS, flight-risk scoring, heatmaps, and attrition trends extend beyond processing individual departures.
- Documented API: Swagger UI and an OpenAPI 3.0 specification provide a defined reference for technical integration work.
Cons
- EMP Cloud is a prerequisite: OAuth2/OIDC authentication depends on EMP Cloud running, limiting its appeal as a standalone product.
- Technical deployment burden: Node.js, pnpm, MySQL, and Redis requirements call for technical ownership.
- Pricing needs clarification: The product is described as free and open source, while the pricing page presents per-user tiers and an Enterprise quote.
- Payroll data may need another route: EMP Payroll is optional, so teams not using it must account for salary data in settlement calculations.
Alternatives
Employee Offboarding Software is the broader category directory for comparing options. Consider 50skills Offboarding if a web and API option with a free plan and free trial better fits your purchasing preference. MangoApps may suit organizations seeking a broader multi-platform offering, with a free trial and paid pricing from $9 a month from 200 employees. Assess.one Employee Offboarding Workflow is worth considering for a web-based freemium option whose free tier includes 100 operations per month and one team member.
FlexiEle Employee Exit & Offboarding is another option for organizations comparing employee-size-based offboarding tiers. Okta Lifecycle Management is an alternative for buyers who want a paid lifecycle-management product with an Essentials plan at $17 per user per month, billed annually. Stitchflow may appeal to teams considering a free first workflow and a paid ongoing plan. Newployee is a web-based freemium alternative centered on onboarding journeys, with a free tier for one active journey per month. OffboardIT offers a free starting workflow and charges when it is running in production.
Verdict
Choose Emp-Exit if your organization already runs EMP Cloud and wants departure processing, settlement, employee participation, and attrition insight together. Its strongest case is the range of workflows spanning departmental clearance through post-exit analysis. Look elsewhere if you need standalone offboarding or want to avoid managing the self-hosted prerequisites and EMP Cloud dependency.
The verdict
Emp-Exit covers employee-facing departure tasks alongside clearance, settlement, and attrition analytics. Its reliance on EMP Cloud and listed deployment prerequisites are important considerations for organizations planning a setup.
Questions people ask
Is EmpCloud Emp-Exit open source?
Yes. The repository states an AGPL-3.0 license, and the pricing note describes it as open source.
Which platforms does Emp-Exit support?
It is listed for API, self-hosted, and web use.
Does it integrate with payroll?
EMP Payroll is an optional source of salary data for full and final settlement calculations.
What authentication does it use?
It uses OAuth2/OIDC authentication through EMP Cloud, which must be running.
What plans are listed?
Essentials/Bronze is $22 a year per user for 1–10 users; Standard/Silver is $44 a year per user for 11–50; Premium/Gold is $66 a year per user for 51–200; Enterprise/Diamond has personalized pricing above 200 users.
What the maker publishes
- Additional features
- The repository describes asset returns, knowledge transfer, PDF exit letters, background verification, an opt-in alumni directory, and a rehire workflow. source
- Analytics
- The product includes flight-risk scoring, attrition analytics, and exit survey NPS tracking. source
- API
- The project documents a Swagger UI at /api/docs with an OpenAPI 3.0 specification. source
- API
- The project documents an OpenAPI 3.0 specification with Swagger UI at /api/docs. source
- Attrition analytics
- It includes 0–100 flight-risk scoring, risk-factor analysis, department heatmaps, attrition trends, and exit analytics. source
- Clearance
- Clearance workflows support sign-off from departments including IT, Finance, HR, Admin, and managers. source
- Clearance
- Its clearance workflow supports sign-off by departments including IT, Finance, HR, Admin, and managers. source
- Deployment
- The quick-start instructions include Docker Compose and list Node.js 20+, pnpm 9+, MySQL 8+, and Redis 7+ as prerequisites. source
- Deployment
- The README provides a Docker Compose setup and lists Node.js 20+, pnpm 9+, MySQL 8+, Redis 7+, and a running EMP Cloud instance as prerequisites. source
- Employee experience
- Employees can use self-service to submit resignations, check exit status and checklist items, complete interviews, and submit an exit NPS survey. source
- Exit workflows
- It supports exit requests for resignations, terminations, retirements, and contract endings, with configurable notice periods. source
- Exit workflows
- It supports configurable exit workflows for resignation, termination, retirement, and contract end. source
- Integration
- The project uses OAuth2/OIDC authentication through EMP Cloud, and its setup requires EMP Cloud to be running. source
- Integrations
- EMP Exit uses OAuth2/OIDC authentication through EMP Cloud, and EMP Payroll is an optional source of salary data for final settlement calculations. source
- Intended users
- The pricing page lists tiers for organizations with 1–10, 11–50, 51–200, and above 200 users. source
- License
- The repository states that the project is licensed under AGPL-3.0. source
- License
- The repository states that the project is licensed under AGPL-3.0. source
- Maker
- The EmpCloud site identifies the company as EmpCloud India Private Limited. source
- Notifications
- Six branded email templates cover exit milestones, with preview, customization, and delivery logging. source
- Other features
- Features include exit interviews, asset return tracking, knowledge transfer, letter generation, background verification, alumni profiles, and rehire workflows. source
- Payroll dependency
- EMP Payroll is listed as optional for salary data in full and final calculations. source
- Purpose
- EMP Exit is EmpCloud’s employee offboarding and exit management module. source
- Purpose
- EMP Exit is EmpCloud’s employee offboarding and exit management module. source
- Settlement
- Full and final settlement calculations cover pending salary, leave encashment, gratuity, deductions, and notice recovery, with manual adjustments and approval. source
Checked against the maker's pages on 4 Oct 2026.