Trust, stated plainly.
How Vezra handles data, access and agents, and who is responsible for what. Each customer’s commitments are written into their agreement.
Data, access, agents and support.
The approach for every engagement. The specifics live in each customer’s agreement.
Data
Customer data remains the customer’s. Its use, retention and return are set in the agreement.
Migrated data is trial-loaded, reconciled against its source and signed off before go-live.
Hosting, data location and recovery commitments are agreed per engagement, in writing.
Access
Roles, permissions and approval thresholds are defined with you and tested before go-live.
Significant actions, approvals and changes are recorded with who made them and when.
Vezra’s own access to your environment is limited to what the agreed work requires.
AI agents
Agents act within the permissions and business rules of the role they are assigned.
Where rules require a person’s approval, the agent proposes and a person approves or rejects.
Agent proposals and actions are recorded alongside human actions, in the same history.
AI consumption is identified separately. See implementation economics.
Support
Support scope, hours, response commitments and escalation are documented in each agreement.
Vezra does not run a public status page. Incident communication is agreed per engagement.
Vezra does not currently hold third-party security certifications and does not publish uptime or availability figures. Specific controls, support hours and recovery commitments are documented in each engagement agreement.
Who is responsible for what.
Most responsibilities are shared. Each agreement settles the details in the last column.
| Area | Vezra | Customer | Agreed per engagement |
|---|---|---|---|
| Platform | Operates and maintains the platform and its foundational services. | Uses the platform within the agreed scope. | Hosting arrangement, maintenance windows and recovery commitments. |
| Configuration and custom work | Builds to the approved scope and documents what was configured and what was custom. | Approves the scope and accepts or rejects each checkpoint. | Change process and acceptance criteria. |
| User access | Provides role and permission controls and sets up the initial roles from the design. | Decides who has access and at what level, and removes access when people leave. | Who administers access day to day. |
| Business data | Handles it to deliver the service, and migrates and reconciles it as scoped. | Owns its data and its accuracy, and signs off migrated data. | Retention, location, and return or deletion at the end of the engagement. |
| Agents | Enforces permissions and approval rules on agent actions and records them. | Decides which actions agents may propose and which need a person’s approval. | Which workflows use agents, and any consumption limits. |
| Controls | Implements the controls in the design and tests them before go-live. | Defines control requirements and operates them: reviews, approvals and sign-offs. | Scope of control testing and the evidence provided. |
| Integrations | Builds and maintains the integrations agreed in scope. | Is responsible for its external systems and its relationships with their providers. | Which systems are connected, and who holds the credentials. |
| Support | Provides the support defined in the agreement. | Names its contacts and reports issues through the agreed route. | Hours, response commitments and escalation. |
| Security concerns | Investigates reported concerns and notifies the customer as agreed. | Reports suspected issues, and looks after its own users’ devices and credentials. | Notification contacts and timelines. |