You decide what Vaulty sees

Vaulty does not crawl your systems. Every connection is a list you approve: these tables and views from the ERP, these folders, these mailboxes. The node reads what is on the list and nothing else. A table that is not on the list is not read, not counted, and does not appear anywhere in Vaulty, not even as a name.

How it worked at our first customer

At the food manufacturer Vaulty was built with, the recipes stayed outside by written rule from the first day. From the purchasing side of the ERP, only the tables needed for goods receipts were connected, and nothing else in that system was listed or counted. When a new source was needed, it was added as a change the customer asked for, not something the agent found on its own.

Changing the list

Adding a source is a change you request, and you see what it contains before it is connected. Removing one takes effect immediately: the node stops reading it and the agent stops answering from it. The list is yours to read at any time, in plain words, from inside Vaulty.