We ran the shifts before we wrote the software.

Tsutome started inside a multi-branch operation, not in a product meeting. The first version existed because we needed to know who was actually at which branch — and every tool we tried either wanted hardware on the wall or a spreadsheet at the end of the month.

Why we build it this way

Records, not dashboards

An attendance log is evidence. It settles a wage dispute and it answers an inspector. We design for the day it is questioned, not the day it looks nice.

Consent has to be real

Biometric consent is explicit, versioned, recorded in the language it was shown in, and always has a one-time email code alternative — because consent cannot be a condition of employment.

We say what we don't do

We don't compute statutory overtime and we don't claim a certified liveness standard. A tool that overstates itself fails on the day it matters.

Where it runs

Built for multi-branch F&B, retail and construction teams in the UAE. Staff clock in from their own phone or a shared device at the counter — the face and the GPS do the checking, so there is nothing to install. Data sits in a managed Postgres database in the EU region with row-level isolation per company.

0terminals to buy
2languages on every screen
3 yrrecords retained

Talk to the people who built it

There is no sales team in between. Onboarding is done with you — branch setup, face enrolment on site, admin training — rather than by sending a manual.