Invisibility is an operational requirement, not a promise to stay off client calls. It means your client never encounters us in a commit author, a staging domain, a deployment account, an automated alert or a file’s metadata — and each of those is a separate thing somebody has to own before access is created.
How much of it we control depends on whose infrastructure the project runs on, which is why it’s worth settling on day one rather than assuming. When the code sits in our repository, the commit authors, the email addresses on them and the repository name are all ours to configure, and none of it reaches your client. When we work in yours, we commit under whatever identity you specify. We register and run staging domains unless you’d rather provide your own, and where hosting falls inside the scope we hold the deployment accounts as well. Monitoring and alerting come to us during development and move across to you or your client at deployment. Documentation we produce is written to be handed over as yours.
Your project manager owns that list for the length of the engagement. The useful thing to do at kickoff is agree which side owns each surface, because the slips happen where both parties quietly assumed the other one had it.
We keep almost all work inside our own team. Where a piece of work needs a skill we don’t hold, or capacity we can’t free in time, we occasionally bring in a trusted specialist. When that happens the contract doesn’t change: Ablion remains the single point of accountability, and everyone who touches your project signs the same confidentiality terms, including the ones protecting your client’s identity.