Requests, tasks, clients, invoicing, leave, people, attendance and payroll — purpose-built screens over one secure database. No more spreadsheets. No more WhatsApp approvals. No more "which version is final?"
Each module is a purpose-built screen for one job — and they talk to each other, so nothing is typed twice.
Raise → route → approve → track. High-value amounts escalate to the owner automatically. Every decision carries a reason and a permanent timeline.
Assign, start, block (with a stated reason), finish. Overdue items surface themselves. Tasks link back to the request or project that created them.
One client, one record — duplicates are impossible. Projects carry budgets, dates and a manager who can run their engagement without extra permissions.
Draft → sent → paid, computed to the paisa. Payments can never exceed the outstanding amount; corrections are voids with reasons, never deletions. Print or email in one click.
Balance-tracked per financial year. Weekends and company holidays never burn balance. Cancelling approved future leave restores it automatically.
The employee master: permanent codes, reporting lines, an org view, statutory & bank details visible only to the person and HR, documents in a private vault.
One-tap check-in and check-out, office or WFH. A live team board, honest monthly registers, and HR corrections that always carry a reason.
Salary structures with statutory deductions (PF, ESI, PT, TDS), attendance-aware proration, and payroll runs that become immutable the moment they're finalized.
Identity is the foundation: invite-only logins, three tiers, per-module permission grants, company settings — currency, financial year, timezone, approval thresholds.
A real lifecycle, end to end — every step recorded, every handoff automatic.
A team member raises a purchase request; it lands in the approver's queue instantly.
High-value? It escalates to the owner on its own. The decision and reason go on the record.
The approved request becomes a task — assigned, due-dated, tracked to done.
Work rolls up under the client's project, with its manager and budget in view.
An invoice is drafted from the project, sent, and emailed to the client.
Payments are recorded against outstanding; the home page shows what's overdue — until nothing is.
Three honest layers. Security lives in the middle one — where no browser can reach around it.
Nine fast, mobile-first pages — no frameworks, no build steps, nothing to go stale. Screens decide what to draw; they are never trusted to decide what you may see.
Row-Level Security on every table plus ~70 checked database functions. Writes are atomic: the change, its timeline entry and its audit record succeed together or not at all. Sensitive data (salaries, statutory IDs) accepts no direct reads whatsoever.
PostgreSQL — module-organised schemas, referential integrity, financial-year document numbering from a single atomic counter. The same customer exists exactly once, forever.
Staff see their own world; managers see their queue; owners see everything. Enforced by the database engine on every query — verified with zero-leak tests on every module.
Every approval, rejection, void, correction and salary change is logged with who, when and why. Closed records freeze; money and payroll are never hard-deleted.
Nobody signs up unless they were added first — the database itself rejects uninvited emails. The founder's account carries a lock no other admin can touch.
Totals, taxes, proration and statutory deductions are computed server-side and verified to the rupee by automated tests — overpayment is impossible by construction.
Purpose-built for how this company actually works — and it keeps growing, one module at a time.
Sign in to MyNexus →