Case studies of Kol.ski's own products and of delivered work: what the problem was, what we built and what works today.
Kol.ski's own product
Photos of skin changes, measurements and test results scattered across phones and portals became one history pinned to each person's body model. It all runs on the family's hardware, with no vendor cloud.
Case study: Naetha Human →Kol.ski's own product
A door, an extinguisher or a hydrant carries a different number in every document. OOPIS gives each of them one durable code with a QR and NFC label that says, without a database, where the element is in the building.
Case study: OOPIS →A project developed at Kol.ski
The community wanted to see the places residents asked about and to bring order to a tight garage. A contractor implemented the monitoring to our camera placement, the parking stayed at the design stage.
Case study: housing estate →Kol.ski's own framework
A panel, a form or an audit needs a live interface and processes on different machines. Instead of an API server, a broker and websockets, one realtime database with three branches is enough: tasks, state and actors.
Case study: Realtime Framework →Tell us what you want to solve. First we will check whether what we have already built can be used for it.
The first conversation is free: 30 minutes online, no preparation and no commitment.