Zulivio: Workforce operations and CRM

Zulivio is a self-hosted workforce-operations platform: employee records, attendance, work assignments, a live master dashboard and a sales CRM pipeline.

Growing teams track people, attendance and work in spreadsheets plus a per-seat CRM, so the data drifts between tools and the employee list lives in someone else's cloud.

Administrators and managers, employees clocking shifts and breaks, and sales staff working a pipeline.

Employees are created, edited, reset and removed under role-based control. Attendance moves through a shift and break state machine, and work assignments move through a guarded status flow so an assignment cannot jump to an invalid state.

Attendance is a good place to use an explicit state machine. A person cannot end a break they did not start, and the system should refuse that instead of recording nonsense.

Zulivio is a pnpm and Turborepo monorepo. A NestJS backend exposes a REST API; a Next.js frontend communicates through a same-origin server-side proxy, so the browser uses a first-party session cookie and the backend stays behind the web service. PostgreSQL holds the relational records, with Prisma providing typed queries.

Shared TypeScript contracts live in a package imported by both sides. This matters when a field changes: the frontend and backend fail type-checking together instead of silently diverging.

Employees, assignments, attendance sessions, leads and opportunities are related records, not separate spreadsheets. The attendance state machine has explicit states for logged out, working and on break; guarded transitions prevent an impossible work history from being recorded. Assignments have their own status-transition guard.

NestJS guards and decorators express the role hierarchy. API routes cover the employee lifecycle, work assignments, attendance, reports, a knowledge base and a sales pipeline. The repository also documents an MCP tool surface for controlled operations such as reading attendance state and starting or ending a session.

The authenticated workspace is separate from login and setup routes. TanStack Query manages server-owned state and invalidates relevant queries after a mutation, which keeps a dashboard, employee list and assignment view in agreement without maintaining a second handwritten cache.

Passwords use Argon2id. Sessions are opaque server-side tokens rather than irrevocable JWTs, so resetting or removing an employee can revoke their access. The same-origin proxy avoids a third-party cookie dependency, while route guards make role checks on the server, not only in the interface.

One-click installer on the company's own server, with CSV and Google Sheets import and export for moving data in and out.

The install script checks for Docker, generates a database password if needed, starts the stack and waits for the backend's health check. Re-running it after an update rebuilds and restarts the services without touching existing data. Imports and exports provide a way to move records into or out of the system.

Zulivio is an intentionally bounded workforce-operations slice of a larger roadmap. The repository separates what exists today from future multi-department plans. That is useful for a buyer and for development: a roadmap is not a feature list.

Lead developer.

Workflow state is more than a status column. Expressing attendance and assignment transitions as rules makes invalid actions fail at the boundary, and gives tests something precise to assert.