Software you own, not a dependency you're locked into.

Clients should invest in software, not dependency. The objective is to build systems that a business can own, understand and evolve over time. Whenever practical, unnecessary vendor lock-in is avoided and projects are designed so that future maintenance can be performed by MURTWEB or another qualified team.

Unless agreed otherwise in the contract, the source code developed specifically for a project is intended to be transferred to the client after contractual obligations are fulfilled. Any exclusions — such as pre-existing internal libraries, open-source components or licensed third-party software — are clearly identified before development begins.

Where possible, the source repository is created under the client's GitHub, GitLab or other organisation. If development starts in a MURTWEB-managed repository, ownership can be transferred during handover together with the full commit history.

Production infrastructure should be provisioned in accounts owned by the client whenever feasible. This includes cloud providers, domains, DNS, email services and deployment platforms. Temporary MURTWEB-managed environments may be used during delivery when agreed.

Technologies are recommended based on project requirements rather than commercial partnerships. Subscription services, APIs and SaaS products remain subject to their own licensing terms. Recurring costs are explained before implementation whenever they are known.

Each project includes documentation appropriate to its scope. Depending on the engagement, this may include architecture diagrams, deployment instructions, environment configuration, API documentation and operational guidance.

Client-specific business logic, workflows, interfaces and deliverables are treated as confidential project assets. MURTWEB retains ownership only of reusable internal know-how, generic utilities and pre-existing frameworks unless otherwise agreed in writing.

A typical handover includes source code, repository access, deployment documentation, an environment-variables inventory (without exposing secrets insecurely), database migration history where applicable, and a knowledge-transfer session if included in the agreement.

The goal is to make future decisions easier — not harder. Widely adopted technologies, clear architecture and documented systems are favoured over proprietary dependencies whenever they do not provide a compelling business advantage.

Many clients continue working with MURTWEB after launch for maintenance and ongoing development. Long-term relationships are valued, but they should be based on trust and delivery quality — not on technical dependence.