Engagement terms for KOVUX: scope, ownership of code, payment structure, confidentiality, warranty and liability for engineering work.
KOVUX is an independent engineering studio operated by Achraf Mehloul, Founder and Principal Engineer, based in Algeria and working with clients internationally.
These terms describe the default engagement model. A signed proposal or contract for a specific project overrides anything on this page where the two differ.
The content of this website — text, case studies, diagrams and imagery — is published for information. It is not a warranty of results, and reproducing it commercially without written permission is not permitted.
Case study figures describe outcomes measured in those specific systems. They are not a promise of identical outcomes elsewhere.
Every engagement starts from a written scope: the problem, the architecture outline, the deliverables and the milestones. Work outside that scope is quoted separately before it starts.
Scope changes are normal in engineering. They are handled explicitly with a revised estimate rather than absorbed silently.
Projects are typically billed in milestones, with the first milestone payable before implementation begins. Retainers and audits are billed monthly or on completion.
Invoices are due within 14 days. Sustained non-payment pauses work and suspends delivery of remaining artefacts.
On final payment, full ownership of the delivered source code, infrastructure definitions and documentation transfers to the client. There is no lock-in, no hidden runtime licence and no proprietary layer you cannot read.
KOVUX retains the right to reuse generic, non-confidential engineering patterns and internal tooling developed over time.
Client material, credentials, data and business context are treated as confidential by default, whether or not an NDA is signed. A client-provided NDA can be signed on request before any brief is discussed.
Publishing a project as a case study only happens with explicit written approval, and sensitive details are removed or anonymised.
Delivered systems come with a defect-correction window agreed per project — defects in delivered functionality are fixed at no cost during that window.
New features, third-party service changes, and issues caused by modifications made by others fall outside warranty and are handled as new work or under a support retainer.
Engineering is done with security review, testing and monitoring, but no system is risk-free. Liability is limited to the fees paid for the engagement in question and excludes indirect or consequential loss.
The client remains responsible for the legal and regulatory compliance of the business the system serves.
Either side can end an engagement with written notice. Work completed up to that point is invoiced, and all artefacts produced and paid for are handed over.
Anything unclear here can be raised directly at contact@kovux.dev before you commit to anything.
See also the privacy policy.