About
Built for the person who runs the place.
Why it exists
Four jobs nobody trained you for.
Running a takeaway means running four jobs on top of the cooking: the rota and the hours people actually worked, the day's food-safety checks, what everyone is owed, and what the deliveries really cost. Often they live on paper, in a group chat and in someone's memory — and they get done after service, when everyone else has gone home.
Invisiko puts all four on one phone. Staff check in by scanning a code at the door. Fridge temperatures and checklists are recorded as they happen, each with a name and a time. Hours turn into fortnightly pay. Delivery notes turn into stock and spend, once someone has checked what was read.
It is built for one independent restaurant, done properly — rather than a cut-down version of software made for chains. The result is a record you can stand behind: who was here, what was checked, what it cost, and when.
What we believe
Plain-spoken software for a hard-working kitchen.
Four ideas behind every screen in the app.
Records made as the work happens
A check written up at the end of the week is a memory. A check recorded at the fridge, with a name and a time, is a record. Invisiko is built around the second.
Say what it doesn't do
It isn't a till, it needs a connection, and it runs one restaurant per account. We would rather you knew that before you start than found out in week two.
A person stays in charge
The app reads delivery notes and works out hours, but nothing reaches your stock or your pay without someone checking it first.
One phone, not a new system
No web dashboard to learn and no hardware to buy: a printed code at the door, and the app on each person's iPhone.
How we build
Handled with care, because it's other people's records.
You'd be trusting Invisiko with your staff's hours and pay and your compliance paperwork. Here is how that is looked after.
Files are private
Invoice photos, certificates and other uploads are kept in private storage and opened only through links that expire after an hour.
Uploads can't be silently lost
The production service refuses to start without its file storage configured, so an upload can never land somewhere the next deploy would wipe.
Roles are enforced on the server
What staff can and can't see is decided on the server, not just hidden in the app. A staff account asking for a manager's data is refused.
Location is read once
A phone's position is read at check-in or check-out, and never tracked continuously.
Your restaurant controls its data
Invisiko provides the app and the infrastructure it runs on. Personal data is not sold and not used for advertising.
This website is separate
This site has no access to the app or its data. It holds no credentials and calls none of the app's services.
Questions about how it works?
Ask us anything before you decide. A person reads every message.