Meet Kin, your AI teammate running IT support 24/7
Kin answers questions, grants access, and runs joiner-to-leaver work in Slack with your team's approval, so requests resolve in your systems before they reach your queue.
Employees ask. Kin resolves. You approve.
Kin reads role, manager, location and start date from your HRIS, so it grants what the person in front of it should have rather than what a static rule assumed.
Deprovisioning on the day
Kin revokes Okta, Google, GitHub and every connected system on a leaver's last day, wipes the device through your MDM, and writes each step to the ticket.
Requests resolved, not deflected
Kin acts in Okta, Google Workspace, GitHub and your MDM, completing the request in the thread rather than surfacing an article and closing the conversation.
Evidence your auditor will accept
Export a complete record of who requested access, who approved it, when it was provisioned and when it was revoked, ready to hand to an auditor rather than reconstruct.
Access reviews without the spreadsheet
Kin runs periodic reviews against live HRIS data, flags standing access nobody has used, and reclaims the licence once it's revoked.
Spot what needs your attention
Track deflection and resolution rates, team workload, SLA performance, and the gaps in your runbooks that keep generating the same tickets.
Ticketing that fits how you work
Run ticketing natively in Kinfolk, or keep Jira and ServiceNow as the system of record with two-way sync, so nothing forces a migration you didn't ask for.
Auto-triaging and routing
Requests that need a person arrive categorized, prioritized, and tracked against your SLA, and Kin routes each one to the right owner.
One desk, every team
IT, HR, Finance and Legal work from one platform, with role-based access so each team sees the requests it owns and nothing beyond them.
Least privilege, by default
Time-bound access, expires on a schedule you set, so nobody holds admin on a system they touched once six months ago and everything granted has an end date.
Your data stays yours
Kin runs on scoped service credentials rather than standing admin, and employee records are processed to answer the request in front of it, never used to train a model.
Access and permissions
Control what Kin can see and act on across knowledge, workflows and connected systems, down to each field, so it operates inside your access model rather than alongside it.
Keep the human things human
Increase capacity, not headcount
Up to 80% requests handled by AI
Up to 1.5 days a week reclaimed by HR
Average 4.5/5 employee satisfaction score