The data isolation is the product — and what it costs to ship one
Most AI products treat the data isolation as a feature. We treat it as the product — and the difference shows up in what we are willing to give up to keep it.
Max Hilton · Founder, minidesk
When we say minidesk is "the path to legacy software, never the replacement," the line that does the work is the data isolation. Two companies on minidesk can share a phone number, an email, an account, a workspace — and the data they see is still completely separate. That sentence is not a slogan. It is a constraint, and the constraint shapes everything we ship.
What "data isolation" means in practice
Every AI answer is filtered by the same row-level security that protects your data when the staff open the system. If a person cannot see a customer in the console, the AI cannot see that customer either. The AI's scope is the asking person's scope, enforced in the database, not asked of the model.
That is different from how most AI products work. The common pattern is: a prompt says "you only have access to customer X's data," the model obeys for a while, and the day a clever prompt or a fine-tune breaks the rule, no one notices until the leak is in the press. We do not do that. The model is never the line of defence — the database is.
What it costs
Three costs worth naming, because they are the costs nobody else pays and that is the competitive moat:
- 1We cannot ship features that need the model to "see everything" to do their job. That rules out the easy version of agent mode, the easy version of cross-company analytics, and the easy version of any of a dozen SaaS AI features. We ship the hard version, or we do not ship at all.
- 2The schema is not negotiable. The cage, the membership model, the row-level security — every plugin that wants to ship on minidesk has to read and write through the same shape. The plugin SDK is the price of admission; it is the contract that lets a thousand developers build without any of them being able to widen the isolation.
- 3The build is slower than it would be if we trusted the model. We have a separate isolation test suite that runs on every release, on every plugin, on every schema change. The cost is in hours and in caution, and we accept it because the cost of a single leak is the company.
Why the cost is the feature
The reason we ship the data isolation as the product is that no other AI assistant at the SME price point does. The enterprise tier — Microsoft, Salesforce, ServiceNow — has it, at enterprise price. The SMB tier — every chatbot and every Copilot knockoff — does not. There is a gap in the market, and the gap is exactly the kind of business a Malaysian SME runs on software that does not talk to each other.
“The wall is not a feature. The wall is the reason a Malaysian bookkeeper can let the AI see her sales ledger without fear that the next prompt will land in her competitor's inbox.”
If you are evaluating us against a cheaper AI assistant that promises the same things, the question is the same one you would ask your bank: when something goes wrong, where is the wall? If the answer is "in the prompt," the wall is not there.