Data custody
Custody means you hold it
Canvas keeps one copy of your operational truth, and that copy lives inside your perimeter. You hold it. Vailient does not.
Hold, not own
Why we say custody
Your operations data already belongs to your business. What Canvas adds is a resolved, single copy that you keep close, on your own infrastructure, instead of scattered across systems and spreadsheets.
Deployment
Where Canvas runs
Canvas runs on infrastructure you choose. Whichever you pick, you hold the copy.
Windows installer, Docker on Linux, cloud or hybrid.
What stays and what can leave
By deployment shape.
| On-site (Windows or Docker) | Cloud | Hybrid | |
|---|---|---|---|
| Where Canvas runs | On your own machines. | Hosted in the cloud. | On-site sensors and sources, with cloud dashboards. |
| Where the copy lives | Inside your perimeter. | In the cloud environment you agree for your deployment. | Agreed per deployment with your partner. |
| What leaves your perimeter | Nothing by design, apart from what you configure, such as chat notifications. | Not applicable: the deployment is hosted. | [CONFIRM: exactly which data classes cross to the cloud in a hybrid deployment] |
Connected assistants
Assistants that read, not write
Read-only
An assistant such as Claude can read the context you approve and ask data questions. It cannot change anything.
Signed in as a person
Each user signs in with their own Canvas account. Remove the account and the assistant loses access.
Permissions per feature
The assistant connection is a feature a user is given, like any other.
See where your data would live
We will walk through the deployment shape that suits your site.