Built on Frappe HR and ERPNext
NV360 People puts attendance, leave, payslips, expenses and approvals in every employee’s pocket. It is built native on Frappe HR and ERPNext, so your HRMS stays the single source of truth.
Runs on
ERPNext Finance and operations core 
Frappe HR HR and payroll 
Frappe The framework underneath Built with
Flutter One codebase, both platforms 
Android Dev, staging and production builds 
Firebase Push delivery over FCM Frappe, ERPNext and Frappe HR are trademarks of Frappe Technologies Pvt. Ltd. Android, Flutter and Firebase are trademarks of Google LLC; the Android robot is reproduced from work shared by Google and used under the Creative Commons 3.0 Attribution Licence. iOS is a trademark of Apple Inc. NV360 is an independent implementer and is not affiliated with, or endorsed by, any of them.
Two ways in
NV360 People and NV360 Notifications install onto the bench you already run. No migration, no second database, no fork of your instance. Your employees are on mobile in weeks, reading the same records your HR team works in today.
See the architectureFrappe HR and ERPNext give you a full HR and finance core with no per-seat licence. NV360 adds the employee app most vendors charge for separately, then configures, migrates and supports the whole thing from Dubai and Chennai.
Talk to usThe gap
Frappe HR runs on a desk. Most of a workforce does not sit at one.
So leave requests arrive on WhatsApp, payslips go out as email attachments, and managers approve from their inbox because opening the Desk is one login too many.
The records are right. The reach is missing.
For employees
Six things an employee actually needs from HR, and nothing they do not.
Offline
Half the reason an employee app fails is that it needs a network the warehouse floor does not have. NV360 People is explicit about what works without one, and about what it refuses to keep on the device.
The check-in is accepted by the device, and says so. It does not claim to be recorded.
The queued action replays. What appears on screen is the server’s answer, not the phone’s optimistic guess.
The cache has a denylist, and it is short on purpose. These never touch the device.
Screens render from encrypted on-device snapshots that show their age and say plainly when they are stale.
Attendance actions are held on the device and replayed when the network returns.
Leave changes, profile changes and manager decisions require connectivity. The app says so rather than pretending otherwise.
For managers
A manager sees their team and no one else. Scope is resolved on the server from the reporting hierarchy, so a manager cannot widen it by asking for somebody else’s record.
Leave and expense decisions in one queue, with the balance, the dates and the attachment already on screen.
Who is in, who is late and who is on leave, for any date range inside the manager’s own hierarchy.
Upcoming and overlapping leave across the team, visible before a decision is made rather than after.
The same home screen every employee gets, with the team’s pending work added above the manager’s own.
Decisions reuse the Frappe HR document lifecycle. NV360 adds scope and audit. It never bypasses HRMS permissions.
Architecture
The reason this is worth reading: most HR apps sit beside your ERP and drift out of sync with it. This one does not sit beside anything.
NV360 does not vendor Frappe, ERPNext or Frappe HR. There is no forked instance to maintain, and your upgrade path stays the one Frappe publishes.
The apps read and write your HRMS and ERPNext records through the Frappe ORM and Frappe permissions. NV360 keeps no separate copy of your HR data.
People, Field Sales and Notifications are independent of each other. Install one or all three. Notifications needs only Frappe; People and Field Sales need ERPNext and Frappe HR.
Deploy on your own infrastructure, or have NV360 host and operate it. The product is the same either way.
Security and governance
Most of what follows is ordinary engineering. It is listed because in an app that carries a whole workforce’s HR records, ordinary engineering is the difference between a product and an incident.
Built for where you operate
Arabic is a real right-to-left layout, not a mirrored afterthought. Every screen is tested in all three languages.
With comfortable and compact density, chosen by the person holding the phone rather than fixed by us.
With screen-reader semantics on every screen. A workforce app gets used by the whole workforce.
Distributed through the public stores or your own internal channel, as separate development, staging and production builds.
Companion module
The same platform, for the team that spends its day outside. Link a salesperson to a territory, plan a dated route of customer stops, and record a GPS check-in and check-out at each one. Managers get a daily visit summary by status, employee and territory.
One visit row and two GPS points per visit. This is not continuous location tracking, and we do not sell it as any.
Ask about Field SalesHow we deliver
NV360 implements ERPNext and Frappe HR as its day job. The app is what we add on top.
We map your current HR processes, policies, shift patterns and org structure. Usually about a week.
Frappe HR is set up around those policies: shifts, leave types, salary structures and approval chains.
People, and optionally Field Sales and Notifications, installed onto your bench.
Employee master data, leave balances and history moved across, then reconciled against your existing records.
App distribution, manager training and employee communications. This is the step most projects underestimate.
An SLA-backed team across Dubai and Chennai, working in your timezone.
Questions
People and Field Sales need both. Notifications needs only Frappe. If you already run ERPNext with Frappe HR installed, you have everything the product depends on.
Yes. Deploy on your own bench and infrastructure, or have NV360 host and operate it for you. The product is identical either way.
It should not. NV360 installs as separate Frappe apps that use documented APIs, the Frappe ORM and Frappe permissions. Nothing is forked and no core file is patched. We still review your customisations during discovery, because that is where surprises live.
No. The backend derives the employee from the authenticated session, so a request cannot name somebody else. A manager sees their reporting hierarchy, and that scope is resolved on the server too.
Reads do, from encrypted on-device snapshots that show their age. Check-ins queue and replay when the network returns. Leave changes, profile changes and approvals need connectivity, and the app tells the person so instead of failing quietly.
No. Frappe, ERPNext and Frappe HR are open source and stay that way underneath your deployment. NV360 People, Field Sales and Notifications are NV360 products, licensed commercially. Source access is a commercial conversation, not a download.
It depends on headcount, which modules you want and whether you host it yourself. Tell us those three things and we will send a written quote.
Book a demo
A working session, not a slideshow. Tell us roughly what you run today and we will set the demo up around it.
We reply within one business day, usually sooner.
Prefer not to use a form? Email info@nv360.ae or call +971 50 701 5309.
NV360 is a software company in Dubai and Chennai. We implement ERPNext and Frappe HR for our customers, and build the products that sit on top of them.
More about NV360
