Your infrastructure. Your data. Your IP.

• Agents run in your environment, or in a sandbox you approve. Once live, nothing runs on our servers or depends on us to keep working.
• Each agent holds scoped, short-lived credentials. No shared keys, no standing admin rights.
• Access is limited to the systems the workflow needs, and it is approved before the build.

During a pilot we may run the work on our own infrastructure so we can move quickly, on data and under a boundary you have approved in advance. At production it moves to yours.

• Your data stays inside your boundary. We name the provider, the region and the retention term before anything moves.
• Enterprise API terms exclude your data from model training.
• Retention is 30 days by default. Where your data class requires zero retention, we arrange it with the provider before the build starts.
• We design to local data-transfer limits from the start, rather than discovering them at review.

Two organisations, and we would rather you heard it here than found it later.

• iAlpha. The founders. We specify the work, review it with your team, build the pilot and sign it off.
• Delivery Devs. Our engineering partner, who take the pilot into your systems and engineer it for production. Production is where agents fail, and it deserves engineers who do nothing else.

They work under the same access rules we do: scoped credentials, only the systems the workflow needs, approved before the build. They are named in your engagement letter as a subprocessor and bound by the same terms we are.

Nobody else. We do not staff your operations, and we do not bring in contractors you have not been told about.

• Code, prompts, configurations, evaluation sets and documentation are assigned to you at handover.
• We assign ownership expressly and do not rely on work-made-for-hire.
• We keep only our pre-existing components, licensed to you perpetually and royalty-free.
• The system runs under your certifications, not ours. Your audit requirements are scoped with you at Triage, before anything is built to them.

• Access and credentials are revoked when the engagement ends.
• Any copies of your data on our systems, or our partner's, are deleted within 30 days, and we confirm the deletion in writing.
• You keep the code, the runbook and the documentation. Nothing you need to run the system depends on us still being there.

If we are still required in year two, the transfer failed.