Behind the agency
Work routes through the agency. Client communication follows the partner model agreed for that estate.
Hosting, Infrastructure Management and incident coverage for agencies responsible for multiple client environments.
Use one ZenoCloud relationship while keeping each client environment, account and responsibility boundary separate.
Separate client VMs with published CPU, memory and storage configurations.
Complete nodes for client workloads that need a defined hardware boundary.
Operate supported client-owned AWS accounts without transferring billing or account ownership.
A recurring operating scope for portfolios that need shared standards and separate client records.
The model can differ by client. It is written down before onboarding starts.
Work routes through the agency. Client communication follows the partner model agreed for that estate.
Agency, customer and ZenoCloud owners share one escalation path with named responsibilities.
The client keeps its cloud account and billing. ZenoCloud receives only the access required for the agreed scope.
We will separate the infrastructure quote from the operating scope and identify what needs discovery first.
Only under the agreed partner and escalation model. The agency keeps ownership of its client relationship.
Potentially, where the platform, access, monitoring and support boundaries are supported and documented.
Yes. Supported AWS environments can remain in the client account. Access and operating responsibilities are agreed before work begins.
Infrastructure is priced by its published unit. Infrastructure Management is scoped around the environments, responsibility and coverage required across the portfolio.