The full answer
Documentation is written during the project, not rushed at the end. Architecture decisions, data models and integration details are recorded as they are made, so the handover reflects how the system really works.
A typical handover pack includes a system overview with diagrams, a README for each repository, instructions for running the product locally, deployment and rollback procedures, API reference documentation, environment configuration notes and a list of third-party services with their purpose.
Access is transferred in an orderly way. Code repositories, cloud accounts, app store accounts, domains and third-party services should be owned by your organisation, and Creuto confirms that every credential and permission is in your hands.
Knowledge transfer sessions walk your engineers through the codebase, infrastructure and release process. Where you are building an in-house team, Creuto can pair with them for a period so they take ownership gradually.
Many clients continue with Creuto for support and iteration after launch, but the handover is always prepared as if you will take over, so you are never dependent on Creuto to keep the product running.