JantaHR
Open-source HR and payroll for India.
PF, ESI, TDS, professional tax, LWF and the new labour codes, calculated every month. Self-host free, forever.
Try the cloud · Website · Self-host in one command · Cloud on Supabase + Vercel · Legal basis · Contributing
Why JantaHR
Indian HR software is either closed SaaS priced per employee or a generic HRMS where you configure PF, ESI and TDS
yourself. JantaHR is neither:
- The statutory work is done. EPF with the ₹25,000 wage ceiling, ESI coverage, state professional tax (including
half-yearly states), labour welfare fund, TDS under the Income-tax Act 2025 with old and new regimes, labour-code
wages under the 50% rule, bonus, gratuity and full and final settlement. Every rule links to its notification in
docs/legal-2026.md.
- You own it. Self-host the complete product on the Supabase stack (Postgres 17 + OrioleDB) with one command:
every feature, no employee limit, no licence key. Or use the cloud edition hosted in India.
- Filing-ready outputs. EPF ECR, ESI contribution file, PT and LWF registers, bank advice, Form 130 salary
certificates and the quarterly TDS extract, plus a compliance calendar that tracks every due date.
- Privacy law built in. DPDP Act 2023 consent ledger, data export, correction and erasure with the 90-day window,
breach register and retention-aware anonymisation. PAN, Aadhaar and bank numbers are encrypted field by field.
Features
| Area | What you get |
|---|
| People | Employee records (80+ fields), departments, org chart, directory, documents with verification, CSV import |
| Payroll | Formula-driven structures, proration, LOP from attendance, arrears, bonus, loans, payslips, Form 130, run → approve → paid |
| Statutory | PF, ESI, PT, LWF, TDS, ECR and challan files, compliance calendar, labour codes, bonus and gratuity |
| Time | Leave policies with accrual and encashment, shifts and rosters, geo-fenced and selfie check-in, biometric push |
| Lifecycle | Onboarding checklists, resignation, clearances, full and final settlement, relieving letters |
| Growth | Appraisal cycles, calibration, salary revision, careers page, applicant pipeline, one-click hire |
| Self-service | Web and mobile (Expo) apps for leave, attendance, payslips, tax declarations, expenses and helpdesk |
| Security | Supabase Auth with two-factor, role-based access, tenant isolation, audit log, row-level security |
Start in 60 seconds
git clone https://github.com/devag7/jantahr
cd jantahr/deploy/self-hosted
./jantahr.sh setup && ./jantahr.sh up # Supabase (Postgres 17 + OrioleDB) + JantaHR
Open http://localhost:3000, create your company and you are running. Details: self-hosting guide.
Developing on JantaHR? See Quick start (local) and CONTRIBUTING.md.
Stack
| |
|---|
| API | NestJS 10 · TypeScript · Prisma 5 · PostgreSQL 16/17 (OrioleDB) (packages/backend) |
| Web | Next.js 14 (App Router) · React 18 · Tailwind with an Apple-style design system (docs/design-system.md) · TanStack Query · Zustand (packages/frontend) |
| Mobile | Expo SDK 51 / React Native (packages/mobile): sign-in with two-factor, geo and selfie check-in, leave, payslips |
| Platform | Supabase (Auth, Postgres, Storage, Realtime, Edge Functions, pg_cron) · Vercel · Docker · Terraform for AWS ap-south-1 · GitHub Actions |
Editions
| Self-hosted | Cloud |
|---|
| Runs on | Your server: the Supabase self-hosting stack with Postgres 17 + OrioleDB, Storage, Realtime, Auth, Edge Functions, plus the JantaHR API and web containers | Supabase project (Mumbai) + two Vercel projects |
| Features | Everything, no seat limit, no licence key | By plan: Free (up to 20 employees), Standard, Professional, Enterprise; 14-day Professional trial |
| Billing | None | Razorpay subscriptions per seat, GST tax invoices (CGST + SGST or IGST) |
| Scheduled jobs | In-process (JOBS_MODE=inprocess) | pg_cron → Edge Function and Vercel Cron → /internal/jobs/* |
| File uploads | Through the API (multipart) | Browser → Storage with presigned URLs (Vercel's 4.5 MB body cap) |
| Guide | deploy/self-hosted/README.md | docs/deploy-cloud.md |
One codebase and one schema serve both; EDITION (API) and NEXT_PUBLIC_EDITION (web) select the behaviour.
여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗
