Commercial information

Customer service agreements

A codebase purchase and ongoing operational work have different scopes. Agree them separately and clearly.

01

Define the work

If implementation, maintenance or customer-only hosting is separately agreed, the service document should identify the deployment, deliverables, responsibilities, fees, support scope and duration. This page does not offer a public hosted subscription.

02

Define who operates what

Identify who controls provider accounts, domains, credentials, backups and the relationship with end clients. Confirm upgrade procedures, incident contacts and data processing requirements for the actual service.

03

Plan handover and termination

Agree the process for configuration and data handover, retained copies, outstanding provider charges and the end of operational access. A hosted service agreement should not leave those responsibilities implicit.

04

Your applicable service agreement

Request the proposed agreement through hello@avrosh.com. This overview is not a signed master services agreement.

Existing purchases and signed agreements remain governed by their applicable terms. This page does not replace an agreement you already have.