OpenHRApp — Open Source HRMS for Growing Teams

OpenHRApp is a free, open-source Human Resource Management System (HRMS) built for small to mid-size organizations (20–500 employees). It delivers biometric attendance tracking, intelligent leave management, performance reviews, and organizational tools — all in a lightweight, privacy-first, self-hostable package.

Why OpenHRApp?

Most open-source HRMS tools are bloated, hard to deploy, or stuck in the past. OpenHRApp is different:

Supabase backend — Managed PostgreSQL with built-in auth, storage, and real-time subscriptions. Free tier is enough to get started.
Self-hostable — Deploy Supabase on your own infrastructure with Docker. Your employee data never leaves your server.
Modern stack — React 19 + TypeScript + Tailwind CSS, not a legacy PHP monolith
Mobile-ready — Installable PWA on iOS, Android, and desktop with offline-aware caching
Multi-tenant — One instance can serve multiple organizations with full data isolation

Key Features

Attendance Tracking (Biometric + GPS)

Selfie-verified clock in/out to prevent buddy punching
GPS geofencing to validate employee location
Office and factory/field duty types
Auto-close forgotten sessions at end of workday

Leave Management

Multi-tier approval workflows (Employee → Manager → HR)
Real-time leave balance tracking (Annual, Sick, Casual, and custom types)
Configurable department-level approval routing
Automated email and in-app notifications at every step

Performance Reviews

Configurable review cycles with competency-based ratings
Self-assessment → Manager review → HR finalization pipeline
Auto-calculated attendance and leave summaries per review period

Employee Directory & Organization Setup

Dynamic departments, designations, and team structures
Role-based access control (Admin, HR, Manager, Team Lead, Employee)
Centralized holiday calendar
Shift management with grace periods and auto-close rules

Announcements & Notifications

Organization-wide announcements with role targeting and expiry
Real-time notification bell + email alerts for leave, attendance, and review events

Reports & Analytics

Attendance summaries and leave reports
Exportable data for payroll integration (CSV, PDF)

Tech Stack

Layer	Technology
Frontend	React 19, TypeScript, Tailwind CSS
Backend	Supabase (PostgreSQL + Auth + Storage + Edge Functions)
Mobile	Installable PWA (iOS Safari, Android Chrome, desktop)
Icons	Lucide React
Deployment	Vercel / Netlify (frontend), Supabase (backend), Docker Compose (self-hosted)

Quick Start

Prerequisites

Node.js 18+ and npm 9+
A Supabase account (free tier is enough) — or Docker for self-hosting
Supabase CLI (install via npm): npm install -g supabase

Option A: Supabase Cloud (Recommended — 5 minutes)

This is the fastest way to get OpenHRApp running. Supabase's free tier includes 500 MB database, 5 GB bandwidth, and 2 Edge Functions — enough for a small team.

1. Clone & Install

git clone https://github.com/mimnets/OpenHRApp.git
cd OpenHRApp
npm install

2. Create a Supabase Project

Go to supabase.com and sign in
Click New Project
Choose an organization, name your project (e.g. my-openhr), set a secure database password, and choose a region close to your users
Wait ~2 minutes for the database to provision

3. Link Your Local Repo to Supabase

supabase login
supabase link --project-ref <your-project-ref>

You can find your project ref in Supabase Dashboard → Settings → General → Reference ID.

4. Apply Database Migrations

supabase db push

This applies all 15 migration files from supabase/migrations/ — creating every table, index, RLS policy, trigger, storage bucket, and helper function OpenHRApp needs.

5. Deploy Edge Functions

supabase functions deploy admin-send-push
supabase functions deploy admin-verify-employee
supabase functions deploy create-employee
supabase functions deploy cron-attendance-reminders
supabase functions deploy cron-auto-absent
supabase functions deploy cron-auto-close-sessions
supabase functions deploy cron-daily-report
supabase functions deploy cron-expire-trials
supabase functions deploy cron-push-checkin-reminder
supabase functions deploy cron-review-transitions
supabase functions deploy notify-admins-email
supabase functions deploy public-ad-config
supabase functions deploy register
supabase functions deploy send-bulk-email
supabase functions deploy superadmin-create-org
supabase functions deploy superadmin-delete-org

6. Set Required Secrets

# Generate a random secret for cron job auth:
# PowerShell: [Convert]::ToBase64String((1..32 | ForEach-Object { Get-Random -Maximum 256 }))
# Bash: openssl rand -base64 32

supabase secrets set CRON_SECRET=<your-random-secret>

7. Set Up Cron Jobs

Open your Supabase Dashboard → SQL Editor and run the contents of scripts/setup-cron-schedules.sql. Before running, replace:

<PROJECT_REF> with your Supabase project ref
<CRON_SECRET> with the secret you set in step 6

This schedules all background jobs: auto-close sessions, auto-absent marking, trial expiration, attendance reminders, daily reports, review cycle transitions, and push notification check-in reminders.

8. Configure Environment Variables

cp .env.example .env

Edit .env and fill in:

Variable	Source
`VITE_SUPABASE_URL`	Supabase Dashboard → Settings → API → Project URL
`VITE_SUPABASE_ANON_KEY`	Supabase Dashboard → Settings → API → `anon` `public` key
`VITE_VAPID_PUBLIC_KEY`	(Optional) Generate with `npx web-push generate-vapid-keys` for browser push notifications

9. Start the Dev Server

npm run dev

Open http://localhost:3000. You'll see the OpenHRApp landing page. Register your organization from the app, or create the first admin user via the Supabase Dashboard → Authentication → Add User.

Option B: Docker Compose (Self-Hosted — 2 minutes)

Deploy the entire OpenHR stack (frontend + Supabase backend) on your own infrastructure with a single docker compose up command. All Supabase services — PostgreSQL, Auth, REST API, Realtime, Storage, Edge Functions, and Studio — are included and pre-configured.

Prerequisites

Docker and Docker Compose v2+
Git (to clone the repo)

1. Clone & Generate Secrets

git clone https://github.com/mimnets/OpenHRApp.git
cd OpenHRApp

# Generate a secure .env file with random secrets:
#   PowerShell: bash scripts/generate-secrets.sh
#   macOS/Linux: bash scripts/generate-secrets.sh
#   (Requires Node.js 18+ and openssl — both standard on dev machines)
#
# Or manually: cp .env.docker .env and fill in your own values
bash scripts/generate-secrets.sh

Edit .env to set your Studio credentials (at minimum):

DASHBOARD_USERNAME=your-username
DASHBOARD_PASSWORD=your-secure-password

2. Start Everything

docker compose up -d

The first startup takes 2–3 minutes while Docker pulls images, PostgreSQL initializes, all 21 database migrations run, 21 edge functions deploy, and cron jobs are configured. Check progress with:

docker compose logs openhr-init -f

3. Access the Stack

Service	URL	Description
OpenHR App	http://localhost:3000	The HRMS frontend
Supabase Studio	http://localhost:3001	Database admin UI
Supabase API	http://localhost:8000	Kong API gateway (REST, Auth, Storage, Realtime)

First time? Click Get Started on the landing page to register your organization.

What's Included

The stack runs 13 containers covering every Supabase service:

Container	Role
`openhr-db`	PostgreSQL 15 with `pg_cron`, `pg_net`, and `pg_trgm` extensions
`openhr-kong`	API gateway routing all Supabase traffic (port 8000)
`openhr-auth`	GoTrue authentication (email/password, JWT)
`openhr-rest`	PostgREST — auto-generated REST API from your schema
`openhr-realtime`	WebSocket subscriptions for live notifications
`openhr-storage`	File storage API backed by MinIO (S3-compatible)
`openhr-minio`	MinIO S3 object store for uploaded files
`openhr-meta`	Database introspection for Studio
`openhr-edge-fn`	Deno Edge Functions runtime (21 functions deployed)
`openhr-studio`	Supabase Studio admin UI (port 3001)
`openhr-imgproxy`	Image resizing proxy for uploaded photos
`openhr-frontend`	React 19 SPA served by Nginx (port 3000)
`openhr-init`	Auto-setup container (runs once — migrations, functions, cron)

Cron jobs for attendance processing, trial expiration, daily reports, check-in reminders, review transitions, and demo resets are automatically scheduled.

Persistence

Your data survives container restarts and docker compose down:

Volume	Contents
`openhr-postgres-data`	All database tables, users, and settings
`openhr-minio-data`	Uploaded files (selfies, avatars, logos)
`openhr-secrets`	Auto-generated JWT keys and credentials

To wipe everything and start fresh: docker compose down -v

Configuration

See .env.docker for a complete reference of all environment variables. Key options:

Variable	Default	Notes
`VITE_SUPABASE_URL`	`http://localhost:8000`	Change if Kong is exposed on a different host/port
`VITE_SUPABASE_ANON_KEY`	(auto-generated)	Must match `ANON_KEY`. Rebuild frontend after changing
`POSTGRES_PASSWORD`	(auto-generated)	Database superuser password
`JWT_SECRET`	(auto-generated)	HMAC-SHA256 key for all auth tokens
`CRON_SECRET`	(auto-generated)	Shared secret for pg_cron → edge function calls
`RESEND_API_KEY`	(empty)	Optional — enables email sending via Resend

Changing the Supabase URL: If you expose Kong on a different host or port, update VITE_SUPABASE_URL in .env and rebuild the frontend:

docker compose build --no-cache openhr-frontend
docker compose up -d

PWA service worker: Runtime caching in the PWA service worker is optimized for Supabase Cloud URLs. In self-hosted mode, API requests bypass the service worker cache. This has no functional impact — the app works correctly; it's a performance optimization only.

Environment Variables Reference

Variable	Required	Purpose
`VITE_SUPABASE_URL`	Yes	Your Supabase project URL (cloud: `https://<ref>.supabase.co`, self-hosted: `http://localhost:8000`)
`VITE_SUPABASE_ANON_KEY`	Yes	Supabase anonymous/public API key (safe to expose in client code)
`VITE_VAPID_PUBLIC_KEY`	No	VAPID public key for web push notifications. Generate with `npx web-push generate-vapid-keys`

Architecture

React 19 PWA (TypeScript + Tailwind)
    │
    ▼
Custom Hooks → hrService (facade) → Domain Services → Supabase SDK
    │
    ▼
Supabase
├── PostgreSQL (15 tables, full RLS)
├── Auth (email/password, row-level security)
├── Storage (avatars, selfies, org logos, content images)
├── Edge Functions (16 serverless functions)
└── Realtime (notification bell live updates)
    │
    ▼
pg_cron + pg_net → Edge Functions (scheduled background jobs)

State-based routing — No React Router; currentPath state in App.tsx
Context + Event Bus — No Redux; AuthContext, ThemeContext, SubscriptionContext
Multi-tenant — Every query scoped by organization_id
Row-Level Security — PostgreSQL RLS policies enforce data isolation per user/org
WebP auto-conversion — All uploaded images converted to WebP

Supabase Project Structure

supabase/
├── migrations/              # Database schema (15 migrations)
│   ├── 0001_initial_schema.sql          # Core tables (orgs, profiles, attendance, leaves, etc.)
│   ├── 0002_rls_policies.sql            # Row-level security policies
│   ├── 0003_auth_hooks.sql              # handle_new_user trigger
│   ├── 0004_fix_rls_helpers.sql         # RLS helper function fixes
│   ├── 0005_storage_buckets.sql         # Storage buckets + policies
│   ├── 0006_settings_unique_constraint.sql
│   ├── 0007_attendance_self_update.sql
│   ├── 0008_attendance_self_update_text_cast.sql
│   ├── 0009_cron_setup.sql              # pg_cron + pg_net extension setup
│   ├── 0010_contact_submissions.sql
│   ├── 0011_push_subscriptions.sql
│   ├── 0012_broadcasts.sql
│   ├── 0013_add_email_to_profiles.sql
│   ├── 0014_admin_hr_cross_org_rls.sql
│   └── 0015_notify_super_admins.sql
├── functions/               # Edge Functions (16 deployed)
│   ├── register/            # Organization registration
│   ├── admin-verify-employee/  # Manual employee verification
│   ├── create-employee/     # Create auth user + profile
│   ├── admin-send-push/     # Send push notifications
│   ├── send-bulk-email/     # Super admin bulk email
│   ├── notify-admins-email/ # Admin notification emails
│   ├── public-ad-config/    # Public ad slot configuration
│   ├── superadmin-create-org/  # Create org (service role)
│   ├── superadmin-delete-org/  # Cascade delete org
│   ├── cron-auto-close-sessions/   # Close forgotten check-outs
│   ├── cron-auto-absent/           # Mark absent employees
│   ├── cron-daily-report/          # Daily attendance summary
│   ├── cron-attendance-reminders/  # Checkout reminders
│   ├── cron-expire-trials/         # Trial expiration
│   ├── cron-review-transitions/    # Review cycle open/close
│   └── cron-push-checkin-reminder/ # Missed check-in push alerts
└── .temp/                   # Local Supabase config (git-ignored)

Storage Buckets

Bucket	Access	Purpose
`avatars`	Public read	Employee profile photos
`selfies`	Private, user-scoped	Attendance verification selfies
`org-logos`	Public read	Organization logos
`content-images`	Public read	Blog/tutorial cover images
`donation-screenshots`	Admin read	Upgrade request screenshots
`showcase-logos`	Public read	Featured organization logos

Cron Jobs

Job	Schedule	Edge Function
`auto-close-sessions`	Every 5 min	`cron-auto-close-sessions`
`auto-absent-check`	Every minute	`cron-auto-absent`
`daily-attendance-report`	Daily 23:00 UTC	`cron-daily-report`
`attendance-reminders`	Every 5 min	`cron-attendance-reminders`
`push-checkin-reminder`	Every minute	`cron-push-checkin-reminder`
`review-cycle-transition`	Daily midnight	`cron-review-transitions`
`auto-expire-trials`	Daily midnight	`cron-expire-trials`

Database Tables

Table	Purpose
`organizations`	Multi-tenant org records with subscription status
`profiles`	Employee profiles (extends `auth.users`, 1-to-1)
`attendance`	Daily attendance with GPS, selfie, and duty type
`leaves`	Leave requests with multi-tier approval status
`shifts`	Shift definitions with grace periods
`teams`	Team records with leader assignments
`settings`	Key-value organization configuration
`announcements`	Organization announcements with role targeting
`notifications`	User notification records
`review_cycles`	Performance review cycle definitions
`performance_reviews`	Individual review records
`blog_posts`	Blog articles
`tutorials`	Tutorial/how-to content
`showcase_organizations`	Featured organizations
`social_links`	Social media links
`upgrade_requests`	Donation and upgrade requests
`reports_queue`	Email automation queue
`contact_submissions`	Contact form submissions
`push_subscriptions`	Web push notification subscriptions
`broadcasts`	Super admin broadcast audit log

Role-Based Access

Role	Access Level
Super Admin	Cross-organization platform management
Admin	Full organization visibility and configuration
HR	Full employee data, leave approvals, review finalization
Manager	Team members' attendance, leave, and reviews
Team Lead	Direct reports only
Employee	Own data only

Deployment

Frontend (Vercel / Netlify / Any Static Host)

npm run build      # outputs to dist/

Set the same VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY environment variables in your hosting dashboard. Deploy the dist/ folder.

Backend (Supabase)

The backend is your Supabase project. No additional deployment needed for the database and auth. For self-hosted, run the Supabase Docker stack behind a reverse proxy (nginx, Caddy) with TLS.

Contributing

We welcome contributions! Bug fixes, new features, and documentation improvements are all appreciated.

Fork the repository
Create a feature branch (git checkout -b feature/my-feature)
Make your changes
Submit a pull request

Please read Others/CLAUDE.md for architecture details, coding standards, and development guidelines.

License

OpenHRApp is open-source software licensed under the MIT License.

Keywords

open source HRMS · free HR software · human resource management system · open source attendance tracking · leave management system · employee management software · self-hosted HR tool · Supabase HRMS · React HR application · open source people management · free attendance system · performance review software · open source employee directory

Name		Name	Last commit message	Last commit date
Latest commit History 982 Commits
.agents/skills		.agents/skills
.claude		.claude
.vite/deps		.vite/deps
Others		Others
public		public
scripts		scripts
src		src
supabase		supabase
volumes		volumes
.dockerignore		.dockerignore
.env.docker		.env.docker
.env.example		.env.example
.gitattributes		.gitattributes
.gitignore		.gitignore
.npmrc		.npmrc
.nvmrc		.nvmrc
CLAUDE.md		CLAUDE.md
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
Dockerfile		Dockerfile
LICENSE		LICENSE
README.md		README.md
SECURITY.md		SECURITY.md
docker-compose.yml		docker-compose.yml
index.html		index.html
metadata.json		metadata.json
middleware.ts		middleware.ts
nginx.conf		nginx.conf
package-lock.json		package-lock.json
package.json		package.json
skills-lock.json		skills-lock.json
tsconfig.json		tsconfig.json
vercel.json		vercel.json
vite.config.ts		vite.config.ts
vitest.config.ts		vitest.config.ts

Folders and files

Latest commit

History

Repository files navigation

OpenHRApp — Open Source HRMS for Growing Teams

Why OpenHRApp?

Key Features

Attendance Tracking (Biometric + GPS)

Leave Management

Performance Reviews

Employee Directory & Organization Setup

Announcements & Notifications

Reports & Analytics

Tech Stack

Quick Start

Prerequisites

Option A: Supabase Cloud (Recommended — 5 minutes)

1. Clone & Install

2. Create a Supabase Project

3. Link Your Local Repo to Supabase

4. Apply Database Migrations

5. Deploy Edge Functions

6. Set Required Secrets

7. Set Up Cron Jobs

8. Configure Environment Variables

9. Start the Dev Server

Option B: Docker Compose (Self-Hosted — 2 minutes)

Prerequisites

1. Clone & Generate Secrets

2. Start Everything

3. Access the Stack

What's Included

Persistence

Configuration

Environment Variables Reference

Architecture

Supabase Project Structure

Storage Buckets

Cron Jobs

Database Tables

Role-Based Access

Deployment

Frontend (Vercel / Netlify / Any Static Host)

Backend (Supabase)

Contributing

License

Keywords

About

Topics

Resources

Code of conduct

Security policy

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages