Your data stays in your building
A Vaulty node runs inside your network, next to your ERP. Your database is never copied to us; only the answer travels, encrypted, over one port you control.
Vaulty does not pull your database into a cloud and query it there. It installs a small node inside your network, on a machine your IT team controls. The node reads your sources where they already are: the ERP, the accounting system, the exports your BI tool already produces, the shared folders, the mailboxes you connect. The working copy it builds from them lives on that same machine. Nothing in that copy is sent to us.
What leaves the building
The node opens one outbound connection to Vaulty, on port 443, encrypted. No port is opened into your network. What travels over that connection is the answer to a question: the rows a query returned, the summary the agent wrote, the action it proposed. The question itself and those rows are sent to the AI model so it can explain them. That is the whole traffic. The database, the files and the mailboxes stay where they are.
What stays with us
Three things sit on our side, so you know exactly what they are. The screen your people use runs on our servers in Frankfurt. The conversations and the facts the agent has learned about your company are stored for you in Ireland. The AI model runs in Microsoft Azure's EU data zone. All of it is inside the European Union, under contracts that name every provider. Your ERP, your accounting and your files are not among those three things.
If you need the AI itself inside your walls
The first version of Vaulty ran its AI model on a machine inside the customer's building, with no model in any cloud. The architecture still allows it: the model is a replaceable part. If your rules say that not even a question may leave the building, we can run Vaulty that way, with a local model, and we will tell you plainly what that model can and cannot do compared with the one in Azure.
Last updated: 2026-11-01