Four contracts. One firm.

The client. Deliverables — code, models trained on the client's data, documents, designs, identity systems — are assigned to the client on payment or acceptance, depending on the model. Altuon retains ownership of its pre-existing methods, frameworks and internal tooling, and licenses them to the client, perpetually and without further fee, to the extent they are embedded in the deliverables. Third-party components remain under their own licences, which are listed in the handover.

For embedded teams, work is created inside the client's organisation and belongs to the client from the moment it is created.

Every agreement fixes its notice period, its handover obligations and the condition in which systems are left, at signature. Handover means: documentation current, credentials rotated to the client, runbooks in place, knowledge transferred to named people, and a defect warranty for project work. There is no exit fee. Leaving well is part of the service, because a client who can leave freely is a client who stays for the right reasons.

Service levels are agreed per system and written into a schedule of the agreement: availability targets, incident severity definitions, acknowledgement and resolution times by severity, and the escalation path with named people. Where Altuon operates a system on the client's behalf, the schedule includes reporting against those levels at every steering meeting. The specific figures are set in the schedule of each agreement rather than published here, because they depend on the system and the hosting choice.

Yes, and this is decided before any design work. For each system the data plane — Switzerland, the European Union, the United States, the client's own premises or a national or sovereign cloud — is recorded in an architecture register. Models can be deployed inside that plane; policy, identity and observability run in a control plane that never holds client data. On-premises and sovereign deployments carry additional cost for infrastructure the client provides and operates, which is made explicit in the proposal.

The current sub-processor list — hosting, email, telephony, model providers, observability — is provided with every proposal and on request, with each processor's purpose and location. Changes are notified in writing before they take effect, with the right to object. Where a client requires it, model providers can be excluded entirely in favour of models deployed inside the client's own plane.

Proposals name the engagement lead and the practice principals, with their roles. Every engagement has a deputy for the lead and documentation standards that mean no system depends on one person's memory. If a named person leaves Altuon during an engagement, the client is informed in writing, a replacement of equivalent seniority is proposed for approval, and the transition is overlapped at Altuon's cost.

Professional indemnity and cyber cover levels are stated in every proposal, with certificates available on request. Liability terms follow the client's jurisdiction — Swiss, Jordanian or US law as appropriate — with caps and carve-outs negotiated in the agreement rather than imposed by standard terms.

Yes. Most relationships begin with an executive briefing or a scoped project. A retainer or an embedded team is proposed only when the work has the shape that calls for it — and we will say so if it does not.