People and work were always connected. Kiptos brings projects, conversations and documents into the same system, so they finally explain each other too.
Built for Indian businesses of 25–100 people. No implementation fee.
Open (2)
Client review deck
Update nav copy
In Progress (2)
Bring design handoff forward
Billing API integration
Closed (1)
Review onboarding copy
HRMS in one tab. Project tool in another. Approvals in an inbox, conversations on WhatsApp, and reports assembled by hand in Sheets at the end of the month from all of them.
When these are seven products, nobody can answer a simple question. When they are one, the answer is already there.
HR software knows the person. Project software knows the work. In most companies those are two logins that never talk to each other. Kiptos is the one system that knows how they connect, and a directory is where that stops being a claim and starts being something you can click on.
Select anyone on the team.
Person
Anaya Rao
Senior Designer · Product
Availability
Checked in · 09:42
Present today
Work
Bring design handoff forward
Due today
Project
Meridian Rebuild
6 people, 14 open tasks
Manager sees
Dev Sharma
No status meeting required
Five stages, and every one of them is a real screen you can open — not a diagram drawn once for a pitch deck. Pick anyone above: the same profile a manager opens, an admin edits, and the employee sees their own version of, governed by one permission matrix, not three.
Anaya Rao
Senior Designer · Product · Reports to Dev Sharma
Open tasks
0
Present
0/20
Leave left
0.0 d
A manager running a team does not need another dashboard. They need to know who is working, who is unavailable, what projects are moving, and where workload is concentrated.
Check in from a phone or a desk. A location snapshot can be taken at check-in and check-out. Breaks, shift timings and regularisation requests all sit on the same record.
Channels, direct messages and threads live inside Kiptos, next to the projects they are about. A decision made in a message becomes a task on a project with an owner and a date.
Dev Sharma · 10:42
Task created from this message
Bring design handoff forward to Wed
Meridian Rebuild · Anaya Rao · Due 11 Sep
Twelve reports read from the same records the rest of the product writes — workload, overdue work, attendance summaries, timesheets, leave availability, project status. Nothing is re-keyed, so nothing disagrees.
Five questions, answered in one screen.
One queue holding leave, attendance regularisation, overtime and timesheets — not four inboxes.
Open work per person, so the imbalance is visible before somebody burns out or misses a date.
Overdue and due-soon work across every project, with the owner attached.
The things that changed while you were not looking, gathered in one place.
Deviations from your team’s own normal, with the evidence attached.
Because the work and the people are in one system, Kiptos can compare what is happening now against what normally happens. No model is asked for an opinion. A deviation is measured, the numbers behind it are shown, and a person decides what it means.
Measured
Hours logged against tasks, by category, from the records the team already creates.
Compared
Against that person’s own history — not against their colleagues, and not against a target.
Surfaced
Only when the difference is large enough and there is enough history to mean anything.
What a manager actually sees
Across their last 6 tasks in Rework & Revisions, this member averaged 4.1 hours each, against 2.4 hours across the previous 14 in the same category — a 71% increase on their own baseline.
Kiptos suggests
Worth a conversation about blockers, scope changes or dependencies on this category of work.
Anaya Rao
InvestigateThis is the real component from the product, not an illustration. Open the evidence — every number names the table it came from.
Kiptos never scores a person, ranks your team, or predicts what someone will do. It reports what changed against their own history and leaves the judgement where it belongs.
Data → Context → Signals → Intelligence
Because your company's data is connected in one place, Kiptos answers everyday questions — who is away, what is overdue, how a project is doing — straight from your own records.
Who has the highest workload right now?
Readingteam_workloadtasks_due_overdue
Comparing against each person's current capacity
Anaya Rao is carrying the most open work right now — 14 tasks, 96% of team capacity. Dev Sharma and Meera Iyer are within a normal range.
Evidence
Most business software is bought by an administrator and endured by everyone else. The employee experience is where these products quietly fail — not just the attendance punch, but the tasks, the messages and the leave request too — and it is the one that decides whether a rollout survives its second month.
About location
A location snapshot can be captured at check-in and check-out — one point each. There is no background tracking, no trail, no geofence, and no selfie or face check. If someone declines the permission, they can still mark attendance.
Good morning, Anaya
Here's your day at a glance.
Location captured at check-in
Bring design handoff forward
Review onboarding copy
People and work are two of them. Projects, conversations, documents and the intelligence layer watching over everything else complete the system, and every layer below is a real part of the product, not a diagram drawn for this page.
People
Directory, attendance and leave. Who's here, and who isn't.
Work & Projects
Tasks, boards and timelines for the work itself.
2
Open
2
In Progress
1
Closed
Communication
Channels and messages, next to the work they're about.
Knowledge
Policies, SOPs and employee documents in the same system.
Management
One queue for every approval, one view of who's overloaded.
Intelligence
Deviations from your team's own normal, evidence attached.
Six layers, and every one of them is a screen behind the same login. Not six subscriptions pretending to talk to each other.
Six mechanisms, all of them real, and none of them scoped to payroll alone — the same database-level isolation protects a task, a message and a salary equally. No badges, because we hold no certifications — and saying so is the part you should trust.
Every record belongs to one organisation, directly or through the record it sits under, and is protected by row-level security in the database itself — not by application code remembering to filter.
Owner, admin, manager, employee and viewer, with a permission matrix an administrator controls. Compensation and payroll are gated separately and are not granted by default.
Sensitive changes run through server-side routines that verify permission first. The browser cannot write its own attendance row or grant itself a role.
An activity log captures who changed what and when, so an organisation can audit its own history.
Once a payroll period is approved and locked, its figures are frozen. Later edits to salary, attendance or overtime do not move a number that has already been agreed.
Employee, attendance, timesheet, task and activity data export to CSV from the Reports section, whenever you want, without asking us.
What we do not have. Kiptos holds no SOC 2, ISO 27001 or GDPR certification, and does not claim one. Our infrastructure runs on Supabase and Vercel, which operate outside India. What we store, why, and who processes it is written out in full in the Privacy Policy.
That is the whole product. No implementation fee, no per-module pricing, no minimum seat count.
per employee / month
People and attendance for a small team.
per employee / month
The whole thing. People, work and communication in one system.
per employee / month
For teams running payroll workflows and deeper reporting.
Creating a workspace is free and no card is required. Billing is invoiced directly, and we will talk to you before your first billing month. Kiptos is not a payroll provider and does not file PF, ESI, TDS or professional tax — see the FAQ below.
Run it on Kiptos.
Free to set up. ₹299 per employee, per month when you are ready.