Get your code and accounts under company control.
Make an inventory of the accounts the business depends on, identify the actual account owner and verify company access. Technical control, contract rights and ownership of project work are separate checks. Recover them through the authorized account and contractual processes.
01 / Start with the account, not the password.
| Account | Evidence to request |
|---|---|
| Repository | Company administrator role, code history and an export or clone. |
| Cloud | Organization ownership, billing contact, admin permissions and recovery routes. |
| Domain | Registrar account, registrant details, renewal and DNS control. |
| Database and backups | Authorized access, export and tested restoration instructions. |
| Third-party tools | Named account owner, subscription rights, integrations and transfer restrictions. |
A password shared in a document may belong to a personal account and may stop working as soon as its owner changes it. A company login with verified administrator and recovery rights is a stronger control.
02 / Send an inventory-based handover request.
- List each asset and the company account that should receive control.
- Ask for the current owner, transfer process and any contractual restriction.
- Record a responsible person and target date for every missing item.
- Agree a period of overlapping access so current operations continue.
- Verify the result before retiring old credentials.
Keep the request factual. If ownership or access is disputed, use the provider’s recovery process and appropriate legal advice. Do not attempt to bypass authentication or assume that a copy of a credential grants authority.
03 / Record the gaps you cannot close yet.
A missing license, inaccessible vendor account or unknown data export can change the takeover plan. Record the business consequence and the temporary operating arrangement. A rebuild may still depend on the same data, domain or third-party contract, so it does not automatically resolve an access problem.
04 / Prevent the same dependency next time.
Your company controls the repositories, cloud, domains, data and credentials from day one. You own project-specific code, configuration, documentation, prompts, evaluations and deployment definitions as each milestone is paid. We retain our background tools and methods, with a perpetual, transferable license to anything embedded in your system.
Use the technology ownership checklist in the next agreement. Then follow the full handover sequence. Foundation can establish the inventory and control as part of the first engagement.
Editorial review: Ego Eimi · Updated September 6, 2026 · About the team
Your technology
Start with the business
Your business depends on it.
Tell us which system matters, what has changed and who controls it. We will define a reviewable next step. Read Foundation and the commitments and evidence.