# Build brief — a focused alternative to HiBob

> **Verdict:** Not faithfully · **Buildability:** 20/100 · **Category:** HR
> **Source:** https://www.canitbevibecoded.com/hibob
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from HiBob. Verify current pricing and capabilities before acting.

## Context

**HiBob** — Track basic people records and approvals without compensation or payroll processing. It currently costs Variable pricing.

A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For HiBob, track basic people records and approvals without compensation or payroll processing. The hard boundary is enterprise hr data, workflows, analytics, payroll integrations, compliance, and support, plus compliance, payroll, and regulated integrations.

This brief describes a focused, single-operator replacement for the part of HiBob that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Track basic non-sensitive people records, maintain approvals, and export data without processing compensation, calculating payroll, or making employment decisions.

- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- PostgreSQL.
- Private self-hosted deployment.
- Strict admin access.
- Documented retention policy.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build a closest honest personal substitute for HiBob in an empty repository.
Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Docker Compose; do not offer alternative stacks.
The core loop is: track basic non-sensitive people records, maintain approvals, and export data without processing compensation, calculating payroll, or making employment decisions.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Implement employees, teams, roles, documents, leave requests, equipment, onboarding tasks, and acknowledgements.
Use least-privilege roles and log every read or change to sensitive records.
Add approval workflows, expiry reminders, export, retention, deletion holds, and encrypted backups.
Keep compensation fields optional and never calculate payroll, taxes, benefits, or statutory filings.
Provide a data dictionary and explain which fields should not be stored without legal review.
Ship Docker Compose, health checks, disaster recovery, and an emergency-access procedure.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure.
Deliberately leave out payroll calculation or money movement.
Deliberately leave out automated hiring decisions or applicant scoring.
Deliberately leave out tax, benefits, immigration, identity, and global-employment compliance.
Finish by running the tests and listing the exact commands used.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Enterprise HR data, workflows, analytics, payroll integrations, compliance, and support.
- Payroll rails.
- Tax and labor-law compliance.
- Benefits integrations.
- Compliance, licensing, and legal accountability are core features.
- Connectors, OAuth flows, and vendor API changes require constant upkeep.

## What you still own after launch

- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
- Maintain every third-party integration as APIs and OAuth rules change.

## Risk

**High consequence.** Use this as a prototype or personal aid. Keep a qualified human and an established provider in the loop for consequential decisions.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [Frappe HR](https://github.com/frappe/hrms) — Active open-source human-resources and payroll application built on Frappe

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/hibob