- Home
- Data and Deployment Options
Data and deployment
Data and deployment options
Our products are installed on your organisation's own server. This page explains in one place, for each product, where data is processed and what leaves it.
Where do our products run?
| Product | Where it runs | What leaves it |
|---|---|---|
| Deckent | Installed on a personal computer, an on premises server or the organisation's own cloud. The ledger, records and work output stay on the organisation's own disk. | Model calls go to the provider the organisation chooses. It can work with a model on your own server (vLLM), so work that must not leave the company can stay on a local model. |
| Kâtip | Installed on the organisation's server, on premises or in its own cloud. Meeting content is encrypted with a separate key for each meeting. After the pilot and the first projects, an option hosted by Verhex will also be offered. | Audio goes to the speech recognition provider and text to the language model provider; the provider accounts and keys belong to the organisation. No audio recording is kept. |
| HR Portal | Runs on the organisation's own server as a single executable, installed as a Windows service or a Linux systemd unit. | Attendance is delivered to the organisation's own ERP. The interface does not connect to an external content network. |
| Xerify | An open source command line tool that runs on the user's own computer. | Only the question the user starts goes to the provider the user chooses. Log files keep metadata only. |
Frequently asked
Where is data processed in custom AI projects?
We decide this with you at the start of the project. For data covered by data protection law we recommend an open model running on your own server. If an external model provider is used, which data goes to which provider is set out in a written data flow at the start of the project.
Who can access what, and how is it monitored?
In HR Portal sign in uses LDAP/Active Directory, OIDC or SAML, two step verification is mandatory and the audit log is hash chained. In Deckent every action of an agent is authorised, isolated and recorded; permission never comes from the model. Kâtip's panel sign in is role based (admin, operator, viewer) and security events are tracked in the panel.
How do you handle data protection (KVKK)?
We handle the requirements of KVKK, Turkey's data protection law, with a written data flow at the start of the project: which data is processed, where it is stored and who can access it. Where data is transferred to an external provider we state it plainly and recommend that it is reviewed with your legal team.
Why does Kâtip use external providers?
Live Turkish speech recognition and the language model run at external providers today. We choose the provider and its region together during installation; the accounts and keys stay with your organisation and stored data stays on your organisation's server.
Have a project? Let's talk.
Tell us briefly and we will get back to you. The first call is not a pitch: we listen to what you need and say plainly whether it can be solved. If you need an NDA, please let us know before the call.