Change the core. Never stop the business.

You do. Source written for you, infrastructure code, tests, documentation and the deployment pipeline are assigned to you on payment and live in repositories you control from the first week. Altuon retains its pre-existing methods, tooling and libraries and grants you a perpetual licence to whatever of them is embedded in your system. Third-party components are listed in a licence inventory with their terms, so nothing in your system carries an obligation you have not seen.

We prefer well-maintained open-source components with permissive licences and a track record of security releases, and we say so in each decision record. Copyleft licences are used only where your legal function has agreed to the obligations they carry. Every dependency is inventoried, pinned and scanned, and we contribute fixes upstream rather than forking privately, because a private fork is a component only we understand.

Documentation is part of the definition of done, not a phase at the end. Each significant decision has an architecture decision record. Each service has a readme that lets an engineer run it locally. Each operational procedure has a runbook. The data model has a dictionary. Before handover, an engineer from your team who was not on the project uses the documentation to onboard, and anything they cannot do from it is a defect we fix.

By never taking a step that cannot be reversed. The compatibility layer means consumers move individually, on their own schedule, and the legacy system keeps running until the last one has moved. Every step has a rollback procedure that has been run in a production-like environment and timed. Dual-running with daily reconciliation catches divergence before anyone downstream sees it. Cut-overs happen in the business's quietest window, with the operators present and a named person holding the decision to roll back.

Defects in work we delivered are fixed at our cost for the warranty period written into the agreement. During and after the Operate phase, support is available under a retainer with response and resolution targets set by severity, written into the contract, and reported against so you can see they were met. We do not offer service levels for infrastructure you operate, but we design and document the system so your own targets are achievable, and we say in writing where they are not.

The system keeps running without us, because that was a gate. On exit you already hold the source, the pipeline, the documentation and the operational record. We provide a transition period at the agreed rate, a walkthrough for any successor you appoint, and the return or deletion of any data we held, with confirmation in writing. Key people on the engagement are named in advance and paired, so no knowledge leaves with a single person.

Every change is reviewed by a second engineer and passes static analysis, dependency scanning and secret scanning before it can merge. Build artefacts are signed and deployed from the pipeline, never from a laptop. Access follows least privilege, with audit logs kept. Findings are tracked to closure with evidence your auditors can read, and the controls are mapped to the frameworks that apply to you: the revised Swiss FADP, the GDPR, Jordan's Personal Data Protection Law, HIPAA, FINMA's expectations on outsourcing and operational resilience, and DORA where you are an EU financial entity.