AI that runs inside your network, not somebody else's.
Most AI works by sending your information to another company's computer. Your invoices, your rates, your customer list, your supplier terms, processed in a data centre you do not control. Orchyn works the other way round. The model is installed in your estate and your data stays where it already is.
Four things a hosted service cannot offer.
The system runs on your infrastructure
The model sits on your servers, inside your network. So does everything that tells it how your business works. Your information is read where it already lives and the answer is produced in the same place. There is no external service in the path, so there is no connection to sever, no provider whose terms can change and no dependency on anyone staying in business.
Nothing is sent anywhere
In a standard Orchyn build, nothing goes to us, to a model provider or to a data centre in another country. This is the difference between a promise and an architecture. Most suppliers protect your data in transit to somewhere else. The safest data is the data that never travels at all.
Your model is yours and so are its instructions
You get your own model, tuned to your operation, not a shared service with your name on it. How it works is written in plain readable files that sit alongside it: your terminology, your rules, your exceptions. It learns nothing from anyone else's business and nobody else's system learns from yours.
You can read how it reached a conclusion
The rules the system follows are written in English in files you can open, not buried inside a model. Every output records the input it came from, the rule applied and the calculation performed, so any figure can be reconstructed and put in front of an auditor or a board.
Why this matters more than a data processing clause
Every AI supplier will tell you your data is safe. Most of them mean it. The difference is what happens when a contract changes, a provider is acquired, a region goes down or a regulator asks where the processing physically took place.
A promise depends on a company continuing to behave well. An architecture does not. If the information never leaves your network, there is no transfer to disclose, no processor to audit and no connection anyone can change the terms of. That is a structural answer to a question that is usually answered with paperwork.
It matters most if you hold client confidential information, operate across more than one jurisdiction, or sell to buyers whose procurement teams ask where data is processed before they will sign.
Common questions
01What does on premise AI actually mean?
The model and the instructions that tell it how your business works are installed inside your own network, on hardware you control. Your data is read where it already lives and the answer is produced in the same place. This is different from a cloud AI service, where your information is sent to a provider's data centre to be processed and you are trusting a contract rather than an architecture.
02Does any of our data leave the network?
In a standard Orchyn build, no. If a particular build genuinely needs an external service, for example a public data source you have asked us to check against, we name it in the design, explain exactly what would be sent, then you decide before it is built. We will not add an external dependency quietly.
03Is our data used to train AI models?
No. Nothing about your operation is pooled, resold or used to train anything, whether ours or a third party's. Because the system is not connected to an external model service, there is no route by which it could be.
04Did you build the model yourselves?
We build and maintain the Orchyn model: the tuning, the instruction layer and the surrounding system are ours and that is where the work and the value sit. The underlying foundation is an open weight model rather than something we trained from nothing and we would rather say so than let you assume otherwise. That choice is deliberate and it is what makes the rest of this possible. A closed hosted model cannot be run inside your network. An open weight one can. If you want the specific base model named in your documentation, we will name it.
05Who owns the system when the work is finished?
You do, outright. The system, the code and the data are yours. It is an asset you own, not a licence that stops working the day you stop paying us. Ownership here is a fact of how it is built, not a clause in a contract.
The full architecture and governance position, written to be forwarded to your risk and IT teams, is on the assurance page. To see the shape of a delivered build, read the case studies, or look at what an engagement costs. It matters most in law firms and accountancy practices, where the records are somebody else's.