Prefer client-controlled commercial accounts
Where practical, domains, cloud accounts, software subscriptions, hardware, and other third-party services are owned or billed directly by the client rather than being used as a dependency mechanism.
Ownership is defined, not assumed
Care should make the operating model clearer—not make the client dependent on hidden access.
Vantus does not design dependency traps. Ownership, handoff, access, third-party billing, documentation, and transition are handled according to the signed scope and contract. The exact model can differ by system, vendor, security requirement, and client policy.
Operating principles
Record access and responsibility
Administrative access, account ownership, role boundaries, and recovery paths should be documented for the systems covered by the engagement. The exact access model follows the signed scope and security requirements.
Treat documentation as an operating deliverable
Documentation included in the Care scope is maintained so the covered environment can be understood, operated, reviewed, and transitioned. The agreement controls which artifacts are included and how often they are updated.
Plan for an orderly exit
Offboarding follows the contract and any approved transition scope. The goal is a controlled transfer of agreed access, current documentation, known risks, and outstanding work rather than an undocumented vendor exit.
What a clean transition should answer
Which accounts and systems are in scope, and who owns each one?
Which administrative credentials or delegated roles exist?
Where are current architecture, dependency, recovery, and operating notes?
What open work, known risks, renewals, and vendor dependencies remain?
What support, data-retention, and access obligations continue after notice?
Which handoff artifacts are included under the actual contract?