Enterprise: Kartoteq on your servers
The product core deployed inside your infrastructure, under your domain and your name, with the terms written into one contract.
Kateryna is head of knowledge at a law firm with sixty lawyers. She liked the notebook, then read the firm’s policy: client files may not leave the firm’s own servers. Her security team sent a questionnaire with forty questions, and the first one was “where is the data stored”.
For some organisations the question is not whether the product is good, but whether it can live inside their walls. That means their domain, their sign-in, their backups, and a clear answer about where AI requests go.
The core inside the firm’s walls
Kateryna’s firm will get the product core deployed in its own infrastructure, under its domain and name. Sign-in through the firm’s directory, integrations, support hours and the choice of AI models are agreed in one contract, and the price is individual. The lawyers will see the same notebooks; the servers will be the firm’s.
This is ahead, after the AI notebook and collaboration, because deploying an unstable core to a client helps nobody. One thing we will put in writing before any rollout: the core on your servers does not by itself mean the AI models run there, and the contract has to say where they do.
Planned · Integrations
What is in scope
This is ahead and depends on the first two directions: there is little point in deploying the core to a client before the AI notebook and the access rules are stable. Deployment, sign-in, integrations, where AI requests are processed and who answers the phone when something breaks are agreed per client, and there is no public price. One thing to put in writing before any rollout: the core running on your servers does not by itself mean the AI models run there too, and the agreement has to say where they do.
Where it stands
This direction is in the plan but not in development yet. We will write here when work starts and when there is something to try. Until then there is no date, and we would rather say so than guess.
If this direction matters to you, tell us about the task behind it. A concrete situation changes what we build more than a vote for a feature does.
Tell us about your task